DocsFor Performance & Paid Media
Use Cases

For Performance & Paid Media

How performance and paid media teams use Trackingplan to explain gaps between ad platforms and analytics, check conversion values and review live campaigns.

For performance and paid media teams who need to trust the conversions their bidding runs on. Ask the agent in a thread: it compares what each ad platform receives with what your analytics records. Connect your ad platforms and it also compares spend and platform-reported conversions.

Explain why an ad platform and analytics disagree

Why is Meta showing more purchases than GA4 this week?

The agent compares both counts for the same period and finds the cause, for example purchases sent twice from the server after a change in the server-side container. It ends with the fix to ask for.

The agent explains a gap between Meta and GA4
The agent explains a gap between Meta and GA4

Check that every platform gets the same conversion value

Are we sending the same purchase value to every ad platform?

The answer shows, platform by platform, how many purchases carry a valid value: where it is missing, where it arrives malformed (for example as text instead of a number) and where duplicates inflate revenue. A follow-up tells you what each gap means for ROAS.

Review the campaigns that are live

Review the paid campaigns currently live — where is data being lost and how could we improve ROAS?

With your ad platforms connected, the agent reads spend and platform-reported conversions per platform, and lists the conversion feeds that send skewed data, ordered by spend and likely ROAS impact.

Know whether a campaign is failing or the tracking is

Pinterest conversions fell off a cliff — is the campaign dying?

The agent compares platform conversions with spend, clicks, sessions and purchases seen on your site, and tells you whether demand really changed or the measurement broke, such as a missing value on part of the checkout hits.

Find conversions counted twice

Is any other tag double-firing?

The agent checks every destination for conversions counted more than once. It tells you which ones repeat, how it happens (a browser tag firing twice, a server-side retry, a page restored by the browser) and whether the platform deduplicates them.

Keep checking it

The UTM naming conventions audit in the Library checks that campaign parameters follow one convention. See Audits.

Was this useful? Write to support@trackingplan.com