Monitoring · always on # Every hit, every hour, every event — watched. Trackingplan watches every event and property across web, mobile, and server-side, learns your hour-of-day and day-of-week baselines, and tells you the moment something drifts — in the channel that owns it. How it works 1. 01 Learns your baselineFrom real traffic during the first days, per hour of day and day of week. 2. 02 Compares every hour against itPer event, per property, per platform. 3. 03 Posts only the deltas that matterWith an explanation and links to the affected hits, in the channel that owns it. Anomalies A traffic drop isn’t always a problem. A spike isn’t always a success. Trackingplan looks at your historical patterns and uses statistical signals — including z-scores and absolute changes — to distinguish meaningful shifts from normal variation. Implementation issues Missing properties, dead tags, duplicate fires, broken triggers, naming inconsistencies, orphan events — caught in the wild, on real traffic. Consent breaches Vendors firing before opt-in and Consent Mode misfires, tracked per market and per hit. Noise control It knows what not to flag: sparse hours, partial buckets, holidays, and the campaign you launched on purpose. > “What we needed was a solution that could look at real user sessions and provide live or near-live alerts when something wasn’t working as expected.” **Persida Roata** · Digital & Analytics Project Manager, MicroAnalytics Ask it [What broke in my tracking this week?Send](/#ask=What%20broke%20in%20my%20tracking%20this%20week%3F) [Pinterest conversions fell off a cliff — is the campaign dying?Send](/#ask=Pinterest%20conversions%20fell%20off%20a%20cliff%20%E2%80%94%20is%20the%20campaign%20dying%3F) [Start monitoring your data →](https://app.trackingplan.com/signup) [Book a demo](/demo) ## Monitoring that doesn’t need babysitting. Your analytics stack changes every day. New releases. New campaigns. New tags. New vendors. New consent rules. Trackingplan keeps watching in the background, so your team doesn’t have to spend its time checking whether everything is still working. - Implementation monitoring ### Know when a release breaks your tracking. Before it breaks your reporting. Trackingplan watches your implementation in real traffic and catches the changes you weren’t told about — broken tags, missing data, duplicate events, and more — before they make it into your reporting. Posted to #tracking · 4 minutes ago Slack·Email Real-time alert · 4 minutes ago **TikTok – Purchase is firing on two different triggers** since the GTM publish at 11:02. Every order has been reaching TikTok twice since then. **Trackingplan** · monitor Since 11:02, each purchase goes out to TikTok twice from the same tag: once on the *Purchase Confirmation* pageview and once on the *purchase* DataLayer event. TikTok’s bidding has been optimizing on a doubled signal since 11:02. GA4 and the other pixels are unaffected. **Cause:** the 11:02 publish added the *purchase* DataLayer trigger to *TikTok – Purchase* without removing *Purchase Confirmation*, so both match on every order. One trigger to remove in GTM. Purchase hits to TikTok, per minuteSince the publish - Marketing & campaign monitoring ### Your marketing data, connected to reality. Track the signals your campaigns depend on — from UTMs and conversion events to pixels and attribution — and catch issues before they distort performance. Posted to #paid-media · 2 hours ago Slack·Email Real-time alert · 2 hours ago **utm\_campaign is empty on 97% of paid landings** since yesterday. Google Ads and Meta traffic is being attributed as direct. **Trackingplan** · monitor Since yesterday morning, sessions landing from Google Ads and Meta arrive with *utm\_source* and *utm\_medium* but no *utm\_campaign*: 11,400 sessions so far, across the 14 landing pages of the *Back to School* campaigns. GA4 is reporting them as *direct / (none)*. Organic and email traffic are unaffected. **Cause:** the new ad sets went live yesterday with a tracking template that never fills *utm\_campaign*. The old ad sets still do. One template to fix in the ad accounts. Paid sessions with utm\_campaign, %Since yesterday - Consent monitoring ### Know what’s happening with consent, everywhere. Monitor consent signals and vendor behaviour across markets, devices, and user journeys. Catch tracking that fires when it shouldn’t, before it becomes a privacy or compliance problem. Posted to #privacy · 25 minutes ago Slack·Email Real-time alert · 25 minutes ago **Google Ads is firing before consent in DE** since the CMP update at 14:20. 38% of German sessions sent an ad hit before answering the banner. **Trackingplan** · monitor Since 14:20, the Google Ads conversion tag fires on page load for visitors in Germany, before the banner is answered, with *ad\_storage* set to *granted*: 1,236 hits so far. France, Spain and the UK still wait for the answer. GA4 respects the default and is unaffected. **Cause:** the 14:20 CMP update changed the default consent state for the *de* region to *granted*. One default to set back in the CMP, or in the Consent Mode initialization. DE sessions with a hit before consent, %Since the CMP update - Ad-hoc monitoring ### Your team’s operational knowledge, running on its own. Turn the weird, specific checks your team has learned to care about into always-on monitoring. The company’s runbook, living in someone’s head and checked by hand — now checked every hour. Posted to #ecommerce · 12 minutes ago Slack·Email Ad-hoc check · 12 minutes ago **Heads up: 22% of purchase events are missing *currency*** since this morning’s release. Meta’s bidding has been learning from 78% of your orders since then. Your check: “purchase events must always carry a currency property.” **Trackingplan** · monitor Since the 09:15 release, purchases from the new express checkout leave without *currency*: 312 orders so far, 22% of the total. Meta and Google Ads discard those conversions, GA4 reports them with no revenue. Purchases from the regular checkout still carry it. **Cause:** the express checkout builds its own *purchase* payload and never sets *currency*. One property to add in the express checkout’s dataLayer push. Purchase events without currency, %Since the release Trackingplan lives where the work already happens: your team chat, the AI tool you already use, or another agent calling it on its own. - Slack - Teams - Email - MCP - Webhooks - API FAQ ## About the monitoring. ?How long does it take for Trackingplan to work? tp Trackingplan starts monitoring your data in real time immediately after installation — no lengthy setup, no code changes to your existing tracking. Depending on your traffic volume, your dashboard can be ready in as little as one hour. For lower-traffic sites, it may take up to a week. You will receive an email notification as soon as enough data has been collected and your dashboard is ready. ?Will Trackingplan affect my site's visitor experience or performance? tp Not at all. Trackingplan is designed to have a minimal impact on your site. Our lightweight tag, only 10kb in size, has no significant effect on page load times. Additionally, our SDKs are optimized to ensure that your app's performance remains unaffected.The Trackingplan tag loads asynchronously with the page content, responding in less than 500ms. This means that it won't slow down your site's loading speed. Furthermore, once the configuration is stored in the browser cache, it won't be reloaded during subsequent page views for a period of 24 hours.With Trackingplan, you can gather the data you need without compromising the visitor experience or your site's performance. ?What are the problems Trackingplan will notify me about? tp Trackingplan automatically detects and alerts you about missing or dropped events, unexpected traffic drops or spikes, property type mismatches (e.g. a string where a number is expected), naming convention violations in events and UTMs, broken pixels (Meta, TikTok, Google Ads), consent and PII leaks, schema changes introduced by third-party tools, and regressions between releases. All monitoring runs continuously 24/7 in the background, with no manual checks required. Moreover, [Trackingplan's Digests](/docs/settings#digests-notifications) will notify your team with all you need to know about the state of your data at the beginning of your work day so that you can work on what you do best instead of having to find those errors by yourself. ?How does Trackingplan's AI Debugger identify the root cause of analytics errors? tp When Trackingplan detects an anomaly, its AI debugging engine analyzes the affected events, properties, and context to automatically pinpoint the root cause. Instead of a generic alert, you get a structured diagnosis: a plain-language summary of the issue, the most likely root cause hypothesis, recommended actions to fix it, and the conditions under which it occurs - with sample hits to reproduce the problem. What makes this especially powerful is the Potential Impact analysis. Rather than framing issues as purely technical, Trackingplan estimates the business consequences of leaving them unresolved - such as the effect on ROAS, conversion tracking, campaign attribution, or data reliability. This makes it significantly easier to prioritize fixes and communicate their value to stakeholders, clients, or leadership. ?How do I know if Trackingplan is for me? tp Trackingplan is built for digital analysts, developers, and marketing teams who deal with data quality issues. If your team spends time manually auditing tracking implementations, debugging broken events, or discovering data errors after they have already affected reports or ad spend, Trackingplan automates that entire process. It detects errors in real time, so you can focus on insights, not data firefighting. You can get started for free with no credit card required. ?Is there any free trial? tp Yes. Starter and Growth start with a 9-day free trial: Trackingplan learns your specs from your real traffic for 2 days, then you get 7 days free and 25 credits to put your agent to work. For Enterprise, a free Proof of Concept (PoC) period is also available so you can evaluate the solution against your specific business needs before committing. ?How do I get started? tp Getting started with Trackingplan takes three simple steps: 1\. Create a free account to generate your Trackingplan snippet. Install it via Google Tag Manager, by adding a lightweight code snippet to your site's head section, or via iOS and Android SDKs for apps — no code changes to your existing tracking required. 2\. Trackingplan automatically starts discovering and documenting all analytics traffic sent to your integrations. No manual configuration needed. 3\. Once your dashboard is ready, explore all events, pixels, UTMs, and campaigns automatically discovered. Invite your team, customize your alerts, and start resolving the issues Trackingplan has already spotted. ## Know when your tracking breaks. Before the numbers do. Start monitoring your analytics and marketing tracking across web, mobile, and server-side — continuously, on real user traffic. [Start monitoring your data →](https://app.trackingplan.com/signup) [Book a demo](/demo) **Chats** × Send Sample workspace. Answers are scripted — the real one reads your traffic.