There\u2019s no way for you to know exactly what is it, so you do what every media buyer does in this moment: you open four tabs, ping the network, stare at Events Manager, and guess.<\/p>\n\n\n\n
The challenge: Your performance monitoring dashboard can\u2019t tell you what\u2019s actually wrong<\/h2>\n\n\n\n
All your dashboard does, it shows you that conversions dropped. <\/p>\n\n\n\n
Details are kept in deeper investigation, usually the one that follows after such event, because a single dashboard can\u2019t tell whether the conversions actually stopped happening, or whether they stopped being recorded.<\/p>\n\n\n\n
There are multiple problems with this challenge.<\/p>\n\n\n\n
1. Dashboards report outcomes, not diagnoses<\/h3>\n\n\n\n
Every reporting tool you use including Meta Ads Manager, Google Ads, Google Analytics 4, your store backend, your affiliate network, you name it, shows you the conversion count for a period, and when the count drops you see a smaller number than last week. That right there is outcome.<\/em><\/p>\n\n\n\n They don\u2019t show the reason for outcome. Just that it happened.<\/p>\n\n\n\n There\u2019s no announcement to broken tracking component. There\u2019s no console error warning for the broken pixel. There\u2019s no returned 404 for the postback URL that you\u2019ll notice. Conversion PAI keeps connecting, but it\u2019s just sending events with degraded match quality that Meta quietly fails to attribute.<\/p>\n\n\n\n The result happens silently because there\u2019s nothing to trigger an alarm, as every system is still working:<\/p>\n\n\n\n All. Happens. In the background. And over time.<\/p>\n\n\n\n So when you catch it \u2013 you gotta troubleshoot it by yourself.<\/p>\n\n\n\n Check the pixel in Events Manager.<\/p>\n\n\n\n Compare numbers between Meta and Shopify. <\/p>\n\n\n\n Open the offer page. <\/p>\n\n\n\n Pint the network and ask if the postback fired. <\/p>\n\n\n\n Re-run the test conversion. <\/p>\n\n\n\n Export a CSV and compare.<\/p>\n\n\n\n Several hours of work to answer one binary question: is the problem tracking or campaign.\u00a0<\/em><\/strong><\/p>\n\n\n\n Every hour you can\u2019t answer the tracking-vs-campaign question immediately costs money, and you make a wrong decision, and those decisions compound.<\/p>\n\n\n\n The most common wrong decision is you pause the campaign to stop the bleeding, and it\u2019s justified \u2013 conversions dropped, and you don\u2019t know why. Seems logical to pause the campaign.<\/p>\n\n\n\n But the campaign was fine. Your Conversion API was sending events without fbp or fbc parameters for three days, so Meta couldn\u2019t match them to users. Conversions were happening, you just couldn\u2019t see them. You paused a profitable campaign for nothing and lost a week of compounding ad delivery training.<\/p>\n\n\n\n On the opposite side, the mistake is just as costly \u2013 your Conversion API match rate drops to 30% silently. Meta\u2019s algorithm loses signal and starts delivering ads to an audience that\u2019s far from perfect fit.<\/p>\n\n\n\n Campaign still looks fine on Monday because your dashboard averages tracked conversion across the comparison window.<\/p>\n\n\n\n You scale a campaign that has effectively gone blind, and the audience degradation accelerates.<\/p>\n\n\n\n Another problem on top of these two: burned hours on something that should have been automated.<\/strong><\/p>\n\n\n\n If you run paid media for a living, you already know how many hours per week go to troubleshooting broken stuff.<\/p>\n\n\n\n If you don\u2019t, we\u2019ll tell you:<\/p>\n\n\n\n On average, in normal week, 3 hours go to troubleshooting problems that occur in active campaigns, while a bad week can take up to 12 hours of troubleshooting.<\/strong><\/p>\n\n\n\n Cost of those hours from just one occurrence is a price of the solution to take care of that problem.<\/p>\n\n\n\n Speaking of solution\u2026<\/p>\n\n\n\n If you could have a solution that knows how to troubleshoot manually you would never spend all those hours trying to understand where and why the problem occurred\u2026<\/em><\/p>\n\n\n\n Let\u2019s break it down how the solution to this \u201cIs it campaign or tracking\u201d problem actually<\/strong> looks like:<\/p>\n\n\n\n There should be a conditional check: did spend stay stable while output dropped?<\/em><\/p>\n\n\n\n If yes, it\u2019s a tracking problem.<\/strong><\/p>\n\n\n\n If both dropped proportionally, it\u2019s the campaign or the market.<\/strong><\/p>\n\n\n\n There should a system that performs this check automatically, 24\/7, without you asking.<\/p>\n\n\n\n And we\u2019ve built it.<\/p>\n\n\n\n It\u2019s the system that watches the upstream health signals so you catch problems before they compound into a quarter of lost optimisation.<\/p>\n\n\n\n It\u2019s also important to mention that what counts as normal for your account is not what counts as normal for someone else\u2019s \u2013 if you\u2019re an affiliate running native traffic, you might have 25% unattributed conversions as a healthy baseline, but if you\u2019re an eCommerce brand running Meta, you might have 5%. A drop from baseline only matters if the baseline is calibrated to your own history, not to absolute thresholds someone else chose.<\/strong><\/p>\n\n\n\n So what is the system we\u2019ve built?<\/em><\/p>\n\n\n\n RedTrack Pulse is an automated tracking health monitor inside your RedTrack account with one sole mission \u2013 to answer the question can you trust your data right now, and if not, where is it broken?<\/strong><\/p>\n\n\n\n It’s part of ad tracking software<\/a>, and here’s how it looks like in real life appliance.<\/p>\n\n\n\n It compares the current 7 days against the previous 7 days across four signals, performs the spend-stability conditional check on each and labels every signal (Normal, Warning, Critical, or N\/A with simple explanation).<\/p>\n\n\n\n Event Integrity and Spend vs Revenue signals from the RedTrack Pulse do the conditional check you would do manually. <\/p>\n\n\n\n Event Integrity watches for conversions dropping more than 50% week-over-week while spend stays within a 15% corridor (the classic broken pixel, postback or Conversion API fingerprint). <\/p>\n\n\n\n Spend vs Revenue catches the related pattern \u2013 money flowing out and revenue not coming back, or revenue down more than 60% with spend table (usually a postback not transmitting the revenue parameter, a missing payout or an affiliate network model change). If any of them go Critical, the issue is on the data side. If they both stay Normal, the drop is real performance.<\/p>\n\n\n\n On the other spectrum, RedTrack Pulse\u2019s Attribution Integrity and CAPI\/Pixel Health signals exist for failures with delayed effect. <\/p>\n\n\n\n Attribution Integrity tracks the share of unattributed conversions against your account’s own 7-day rolling baseline, and flags when it jumps more than 10% (Warning) or 20% (Critical). The cause of these might lay in the fingerprint of broken UTM tags, a misconfigured attribution window, or a new traffic source running without proper tagging.<\/p>\n\n\n\n CAPI\/Pixel Health watches Meta’s Event Match Quality score or to be more precise how well Meta can match your CAPI events to real users. Below 75% is a Warning; below 60%, or a week-over-week drop of more than 25 points, is Critical. <\/p>\n\n\n\n This is extremely useful because match quality degrades silently, meaning, conversions still arrive in RedTrack, revenue looks fine, but Meta’s algorithm is increasingly delivering ads to the wrong audience. That\u2019s exactly where Pulse catches the degradation upstream, before two weeks of optimisation are lost.<\/p>\n\n\n\n Pulse activates the moment your RedTrack account is collecting data. What that means is that every baseline is calculated from your account\u2019s own 7-day rolling history.<\/p>\n\n\n\n That also means, no configuration, no threshold tuning, no rules to write.<\/p>\n\n\n\n In order to access and read RedTrack pulse, follow these steps:<\/p>\n\n\n\n RedTrack Pulse gives you a diagnosis, and even though diagnosis tells you exactly where to look first, acting on that diagnosis is still your decision.<\/p>\n\n\n\n If your Event Integrity or Spend vs Revenue went Critical, that means you need to fix the data pipe first.<\/strong><\/p>\n\n\n\n Status Critical on Event Integrity means conversions are not flowing into RedTrack the way they were last week, so before changing anything in your campaigns, check the conversion pipe.<\/p>\n\n\n\n For ecommerce:<\/strong> confirm your store-side script and webhook are still firing and Conversion API events are arriving with quality parameters.<\/p>\n\n\n\n For affiliate:<\/strong> ping the network and verify postbacks are being sent with the click ID and revenue parameter intact. <\/p>\n\n\n\n DO NOT pause your campaign if your Event Integrity or Spend vs Revenue is critical, as that is the most expensive mistake you can make!<\/em><\/strong><\/p>\n\n\n\n If your Conversion API or Pixel Health went Critical, that means Meta is increasingly unable to match your Conversion APi events to real users, even though events are arriving so you should audit your event quality before scaling anything.<\/strong><\/p>\n\n\n\n Two common causes for this:<\/p>\n\n\n\n That being said, audit your event payload first.<\/p>\n\n\n\n DO NOT scale spend on any Meta campaign showing Critical CAPI until match rate is back above 75% because every additional dollar is being delivered to a degrading audience.<\/em><\/strong><\/p>\n\n\n\n In case all your signals are status normal, you can rest assured that your data is fine, and the problem lies on the other various reasons, among most common ones are creative fatigue, audience saturation, market shift, seasonal pattern, or a competitor change.<\/p>\n\n\n\n Act on data with confidence \u2013 pause, scale, refresh creative or hold steady, as your data is just fine.<\/p>\n\n\n\n Want to see how RedTrack Pulse work in real life?<\/p>\n\n\n\n Book a demo<\/a> and we\u2019ll show every step of it, or try it for your self and sign up for a 14 day free trial<\/a>!<\/em><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" It\u2019s Monday morning and you just checked in. You opened the dashboard and you see conversions are down 40% from…<\/p>\n","protected":false},"author":17,"featured_media":13156,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_ap_featured_post":false,"footnotes":""},"categories":[220],"tags":[],"class_list":["post-13152","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-use-cases"],"acf":[],"yoast_head":"\n2. Tracking failures happen silently<\/h3>\n\n\n\n
\n
3. Manual diagnostics<\/h3>\n\n\n\n
4. You\u2019re paying for the guesswork<\/h3>\n\n\n\n
Solution: RedTrack Pulse as a diagnostic tool for answering \u201cIs it campaign or tracking\u201d problem<\/h2>\n\n\n\n
![\"redtrack](\"https:\/\/www.redtrack.io\/wp-content\/uploads\/2026\/06\/redtrack-pulse-feature.png\")
<\/figure>\n\n\n\nEvent Integrity and Spend vs Revenue signals<\/h3>\n\n\n\n
Attribution Integrity and Conversion API\/Pixel Health signals<\/h3>\n\n\n\n
How to access and read RedTrack Pulse<\/h3>\n\n\n\n
\n
![\"redtrack](\"https:\/\/www.redtrack.io\/wp-content\/uploads\/2026\/06\/redtrack-pulse-location-in-dashboard.png\")
<\/figure>\n\n\n\n\n
Scenarios and how to act on each Pulse Status<\/h2>\n\n\n\n
My Event Integrity or Spend vs Revenue went status Critical<\/h3>\n\n\n\n
My Conversion API or Pixel Health went status Critical<\/h3>\n\n\n\n
\n
All my signals are status Normal, but metric still dropped<\/h3>\n\n\n\n