Install · 30 seconds

# One tag. Your entire data layer monitored.

One tag in GTM or your `<head>`, an SDK in your iOS & Android apps, or a server-side connection — working from day one. No schema to define, no rules to write: Trackingplan automatically discovers every event as real users navigate your websites & apps.

How it works

1.  14:00
    
    Tag addedGTM, your `<head>`, the iOS or Android SDK, or a server-side hook.`<script async src="https://cdn.trackingplan.com/tp.js" data-tp-id="TP1234567"></script>`
    
2.  14:03
    
    First hits arriveEvery request to every platform, inspected at the source.
    
3.  14:48
    
    Schema inferred142 events, 1,037 properties, six main funnels — all inferred automatically from real traffic.
    
4.  15:10
    
    First question answered“What broke in my tracking this week?” — with the hits behind the answer.
    

Web

A GTM template or one script tag. Every request your pages send to every provider, captured at the source.

iOS & Android

Lightweight SDKs that watch your analytics and ad SDKs, without changing how you track.

Server-side

CAPI, Measurement Protocol, or your own backend. The same visibility into the hits that never reach a browser.

Nothing to configure

Events, properties, platforms and baselines — all discovered automatically. Your tracking plan builds itself as real-user data flows in.

> “We came across exactly the solution we were looking for — and this is rare; it’s not every day you find something so perfectly suited to your problem.”

**David Rascón** · Data & MarTech Consultant, CSA (Havas Media Network)

Ask it

[Just pushed a new implementation to preview — can you check it’s OK before we publish?Send](/#ask=Just%20pushed%20a%20new%20implementation%20to%20preview%20%E2%80%94%20can%20you%20check%20it%E2%80%99s%20OK%20before%20we%20publish%3F) [When was the ‘add\_to\_cart’ event first implemented, and by which release?Send](/#ask=When%20was%20the%20%E2%80%98add_to_cart%E2%80%99%20event%20first%20implemented%2C%20and%20by%20which%20release%3F)

[Install Trackingplan →](https://app.trackingplan.com/signup) [Get help getting started](/demo)

After you install

## Everything your team can do once Trackingplan is in.

Real traffic does the setup. From the first hits, Trackingplan monitors every event around the clock, answers any question about your data with the evidence behind it, and writes the reports your team reads.

-   Fix
    
    ### Always on, from the first hit.
    
    Anomalies, missing properties, broken triggers and consent breaches — caught the moment they appear and posted to the channel that owns them.
    
    Monitors your websites, apps and servers 24/7
    
    Email·Webhook
    
    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
    
    Suggested actions
    
    Show me the triggers Tell me how to fix them in GTM Audit all GTM triggers
    
    Show me the affected hitsSend
    
-   Ask
    
    ### Answers for anyone, without the bottleneck.
    
    Trackingplan takes care of repetitive questions, reports, and data checks, giving analysts their time back — and everyone else an answer.
    
    Answers for anyone
    
    Claude·ChatGPT·MCP
    
    **Emily** · 2 minutes ago
    
    Are we sending every purchase to Meta?
    
    **Trackingplan** · answered in 6.4s
    
    **No. Meta is missing 1,642 of this week’s 13,172 purchases** — 12.5%, all since March 12.
    
    **Look at the rest:** Google Ads, TikTok and GA4 sit on the dataLayer line all week. Meta drops on the 12th, when the new consent banner moved the Meta pixel into the marketing category: visitors who decline no longer reach it.
    
    The purchases exist, and every other platform received them. Meta’s bidding has been learning from **87% of your orders** for three days.
    
    platformpurchasesvs dataLayer
    
    dataLayer*13,172*~~—~~
    
    Google Ads*13,110*~~−0.5%~~
    
    TikTok*13,047*~~−0.9%~~
    
    Meta*11,530*~~−12.5%~~
    
    Found while auditing
    
    **22% of this week’s purchases arrive without `currency`**: the ones paid with PayPal. The ad platforms count them with no value. Different bug, different owner: the checkout, not the banner.
    
    Suggested actions
    
    Open the Root Cause Analysis for this gap Investigate the missing currency on purchase Write the impact story for the paid media team
    
    Show me the missing purchasesSend
    
-   Automate
    
    ### Reports you can edit and share.
    
    A weekly leads report, a Monday conversion-gap email: the numbers, the chart and what changed, written for the people who read it.
    
    Reports you can edit and share
    
    Teams·Slack
    
    Scheduled · every Monday · posted to #analytics
    
    Leads by platform, last 7 days
    
    meta 497 · google ads 514 · organic 305
    
    MetaGoogle AdsOrganic
    
    **Trackingplan** · report
    
    **Meta leads fell 40% from Wednesday**, when three prospecting campaigns were paused on that platform. It’s a change in the incoming traffic, not in tracking: Google Ads and organic held their level, and every lead form still reaches all three platforms.
    
    Analyst note · Daniel
    
    **The optimizations on the remaining campaigns cut the cost per lead by 20%:** fewer leads, but at 14€ instead of 17.5€, with the same qualification rate downstream. Worth keeping the paused budget off until Q4.
    
    Suggested actions
    
    Add the organic campaign to this report Send the full breakdown to #analytics
    
    Break the CPL down by campaignSend
    

FAQ

## Before you install.

?Where should I install Trackingplan?

tp

Wherever your tracking runs. There are three options, and most teams use more than one:

1\. **Web:** a Google Tag Manager template or one asynchronous script tag in your `<head>`. It captures every request your pages send to every provider.

2\. **iOS & Android:** lightweight SDKs that watch your analytics and ad SDKs without changing how you track.

3\. **Server-side:** CAPI, Measurement Protocol or your own backend, for the hits that never reach a browser.

?Do I need to change my existing tracking?

tp

No. Trackingplan works alongside your existing analytics and marketing implementation. You install the tag or SDK and it observes the traffic your existing stack already generates.

?What does Trackingplan actually see?

tp

Trackingplan observes the tracking requests generated by real users across your website, apps and server-side stack — including events, properties, pixels, UTMs, consent signals and provider traffic.

?What happens after I install it?

tp

Real traffic does the setup. As users navigate your sites and apps, Trackingplan discovers every event, property and provider, builds your tracking plan and schema, and learns your hour-of-day and day-of-week baselines. There is no schema to define and no rules to write.

From then on, monitoring runs 24/7 and alerts land in the channel that owns them, you can ask the agent anything about your data and get an answer with the hits behind it, and reports can be scheduled to the people who read them.

?How long does it take for Trackingplan to work?

tp

Monitoring starts the moment the first hits arrive. Your tracking plan and schema build themselves from real traffic, so how fast they are complete depends on your volume: high-traffic sites are ready within hours, lower-traffic ones may take a few days to learn stable baselines. You get an email as soon as enough data has been collected and your workspace is ready.

?Will Trackingplan affect my site's visitor experience or performance?

tp

Trackingplan's web tag loads asynchronously and is under 10 KB. It runs independently of your existing tracking and is designed to have minimal impact on page performance. The mobile SDKs are optimized the same way.

?Is it safe?

tp

Yes. Trackingplan never introduces new tracking mechanisms, never stores personal data and never builds user profiles. It acts as a passive observer of the data you are already sending to your vendors, with strict safeguards against access to personally identifiable information. See the [privacy policy](/privacy-policy) for the details.

?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. Enterprise teams can also run a free proof of concept against their own stack before committing.

Install

## Ready to see what your tracking actually looks like?

Install Trackingplan and let real traffic do the setup.

[Start free →](https://app.trackingplan.com/signup) [Get help getting started](/demo)

**Chats**

×

Send

Sample workspace. Answers are scripted — the real one reads your traffic.