Google Tag Manager

Tracking Plan Template for Paid Media: Plan It Before You Touch GTM

The tracking plan to write before anyone opens Google Tag Manager: the columns, the GA4, Meta, TikTok, Snap and Google Ads names for each event, owners, tests and the questions to settle first.

Cover: Plan the events before GTM. a spreadsheet whose rows (purchase, lead, sign-up) fan out into GA4, Meta, TikTok, Snap and Google Ads columns, with a GTM container icon waiting at the end.

Most tracking plan templates you will find were written for product teams instrumenting an app. They track feature usage and have no column for what Meta calls the event, whether TikTok should get it, or who signs off that the purchase value is right. A paid-media plan has a different job: make sure each ad platform receives the conversions it optimizes on, once, with the right value.

Definition Tracking plan
A tracking plan is the agreed list of events a website sends, with each event’s trigger moment, parameters, destinations, owner and test. For paid media it also records the event name each ad platform expects and which conversions campaigns optimize toward.

The tracking plan template: columns and what to write

Build it as a sheet with one row per business action. These are the columns I use on every new site, in this order. The first four are the business view; the rest are the build and QA view.

Template

Tracking plan columns

 What to writeExample
IDA short code so tickets and QA notes can refer to the rowE06
Business actionWhat the person did, in plain wordsPaid order confirmed
When it firesThe exact moment, after the system confirms itOrder confirmation, after payment succeeds
dataLayer eventThe name the developer pushes, GA4 stylepurchase
ParametersKeys, types and where the value comes fromtransaction_id, value (number), currency, items, event_id
DestinationsEach platform and its event nameGA4 purchase, Meta Purchase, TikTok Purchase, Snap PURCHASE, Google Ads Purchase
RoleOptimize, report only, or audience onlyOptimize on Meta and Google Ads
ConsentWhich consent category gates itMarketing
OwnerWho builds and who approvesDev pushes, marketer tags, agency QA
TestHow you prove it works and who signed offTest order in Preview, then Events Manager and DebugView

Keep the sheet in one place everyone can comment on. Add a tab for open questions and another for dev tasks, so the event rows stay clean.

Map each event to every platform’s name

Name events in the dataLayer once, using GA4’s recommended names, then map. The table below is a starting point for an ecommerce or lead-gen site. Check each platform’s current list before you build, because names change: TikTok’s standard event list now names the purchase event Purchase, while older setups still use CompletePayment.

Starting point

Event mapping for a typical paid-media site

 dataLayer / GA4MetaTikTokSnapGoogle Ads
Product viewedview_itemViewContentViewContentVIEW_CONTENTUsually none
Added to cartadd_to_cartAddToCartAddToCartADD_CARTSecondary, if any
Checkout startedbegin_checkoutInitiateCheckoutInitiateCheckoutSTART_CHECKOUTSecondary, if any
Payment info addedadd_payment_infoAddPaymentInfoAddPaymentInfoADD_BILLINGUsually none
Paid orderpurchasePurchasePurchasePURCHASEPrimary purchase action
Lead form successgenerate_leadLeadSubmitFormSIGN_UP or a custom eventPrimary lead action
Account createdsign_upCompleteRegistrationCompleteRegistrationSIGN_UPSecondary, if any
Call or WhatsApp clickA custom name, e.g. contact_clickContactContactA custom eventSecondary, if any

Snap has no lead event in its pixel template, so teams pick SIGN_UP or a custom event. That is a decision, so write it in the plan and keep it the same on the server side. The details per platform are in Meta Pixel and Conversions API in GTM and TikTok and Snap pixels in GTM.

Build the plan in this order

How to

Write a paid-media tracking plan before the GTM build

The order an agency team works in, from what is live today to a signed-off plan.

  1. 01

    Inventory what is live

    Open the site with Tag Assistant and list every GTM container, hard-coded pixel and plugin that sends data. Note pixels set up outside GTM, such as codeless events created in Meta Events Manager.

  2. 02

    Choose what each platform optimizes on

    One primary conversion per platform and campaign type. Everything else is report-only or for audiences.

  3. 03

    Write business actions as events

    Use GA4 recommended names in the dataLayer: generate_lead, sign_up, purchase. Invent a name only when none fits.

  4. 04

    Map destinations

    Fill the platform columns and mark where a platform gets nothing on purpose.

  5. 05

    Set parameter rules

    value is a number, currency is a code, transaction_id is the order ID, and every conversion carries one event_id shared by browser and server.

  6. 06

    Assign consent and owners

    Which consent category gates each row, who pushes it, who tags it, who approves the publish.

  7. 07

    Write the test for each row

    The page, the action, and what must appear in Preview, DebugView and each platform’s events tool.

The dataLayer contract is the part developers need most. Hand them the event names and parameter keys, not GTM screenshots. For ecommerce rows the full parameter set is in GTM ecommerce tracking; for lead rows, see GTM form submission tracking.

Settle these questions before the build

Open questions

Ask these on day one

  • Which GTM container is the real one? Sites often load two, or an old one nobody owns.
  • Do new pixels replace the old ones or run alongside them, and who decides when the old ones go?
  • Which conversion does each live campaign optimize on today? Changing it resets learning.
  • Where does payment happen, and does the buyer return to a page you can tag?
  • Which consent banner runs, and which categories gate marketing tags?
  • Who has Publish rights in GTM and who approves a publish?
  • Has the client issued fresh pixel base codes, or are you being handed snippets copied from another project?

Where this goes wrong

  • Stale base code. Pixel snippets travel between projects in old documents. Leave the base-code cells empty until the platform owner issues them fresh from Events Manager.
  • Planning by page instead of by action. "Fire on /thank-you" counts reloads, bookmarks and direct visits. Plan the moment the system confirms the action, then decide how to detect it.
  • Purchase only tracked for one payment method. If card or instalment payments redirect to an external gateway and never come back to a tracked page, only cash-on-delivery orders reach the platforms. Ask for a confirmation page that checks payment status first.
  • Item IDs that change through the funnel. A SKU on the product page and an internal number in the cart break catalog matching and dynamic ads. Pick one ID in the plan.
  • Leads with no value. Platforms can then only optimize for lead count. Agree a value per lead type, even a rough one, and label it as an estimate.
  • Two pipes, one rule. If a server-side tracker also sends leads, gating the browser tag does not gate the server copy. Plan both legs in the same row.

Once the plan is built and tagged, test it with the paid media tracking QA checklist.

Do it faster with Whathead

Whathead connects Claude or ChatGPT to Google Tag Manager and GA4 through its Google Tag Manager MCP. For a tracking plan, the useful part is the read: the assistant can list every tag, trigger and variable in a container and compare it with your sheet, so the "what is live" column fills itself. A read-only audit also flags tags with no firing trigger, references to missing triggers or variables, paused tags and duplicate names. Whathead is our product.

  • “Look up container GTM-XXXXXXX and list every tag with its type, firing trigger and the event it sends. Then compare it with the events in this tracking plan and list what is missing or extra.”
  • “Run the read-only audit on the Default Workspace and explain each finding in plain language. Don’t change anything.”

Nothing changes from those prompts. If you want an inspection-only setup, connect the read-only endpoint, https://www.whathead.com/mcp/read, which refuses GTM writes. The GA4 MCP can then list the property’s key events next to the plan.

Tracking plan template: common questions

What is a tracking plan?

A tracking plan is the agreed list of events a site sends, with each event’s trigger moment, parameters, destinations, owner and test. It is written before implementation and used for QA afterwards.

What is the difference between a tracking plan and a measurement plan?

A measurement plan starts from business goals and KPIs. A tracking plan is the implementation layer under it: the exact events, parameters and platform names that make those KPIs measurable.

Who should own the tracking plan for paid media?

The person accountable for conversion data, usually the performance lead or analyst. Developers own the dataLayer pushes and the agency or marketer owns the GTM build, but one person approves changes.

Which event names should a tracking plan use?

Use GA4 recommended names such as purchase, generate_lead and sign_up in the dataLayer, then map them to each platform’s standard event names in separate columns.

How often should the plan be updated?

Every time a form, checkout step or campaign objective changes. Version the sheet and note the GTM version that implemented each change.

Sources

Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.