Conversion Tracking Plan

What This Page Answers

A conversion tracking plan defines which user actions count as meaningful outcomes, where those actions are measured, and how they are sent to ad platforms and analytics systems. Without a tracking plan, campaign optimization becomes guesswork.

What A Tracking Plan Should Include

A practical conversion tracking plan should document:

FieldExample
Event namepurchase, lead, qualified_lead, schedule_demo
Business meaningA completed order or qualified sales handoff
Platform mappingMeta Purchase, Google purchase, TikTok Complete Payment
Trigger locationWebsite, app, CRM, server, offline import
Primary or secondaryPrimary optimization event or diagnostic event
ValueStatic value, revenue, predicted value, or none
Deduplication keyevent_id, order_id, lead_id
Attribution useOptimization, reporting, audience building, or all
OwnerMarketing, engineering, data, sales ops

Primary vs Secondary Events

Not every event should optimize campaigns. Primary events are used for bidding and optimization. They should be meaningful, reliable, and frequent enough for learning. Secondary events are useful for diagnosis, audience creation, or funnel analysis. They may include page views, add to cart, scroll depth, video views, or micro-conversions. A common mistake is optimizing for a shallow event because it has more volume. Volume helps learning only if the event is directionally aligned with business value.

Event Quality

A conversion event should be:

  • Meaningful: it reflects real progress toward revenue or qualified demand.

  • Accurate: it fires once when the action happens.

  • Deduplicated: browser and server events do not double-count.

  • Timely: it reaches platforms quickly enough for optimization.

  • Matched: it includes privacy-safe identifiers where allowed.

  • Stable: it does not change definition every week.

Platform Tracking Stack

A modern paid media stack often uses both browser-side and server-side tracking.

PlatformBrowser-sideServer-side
MetaMeta PixelConversions API
GoogleGoogle TagEnhanced Conversions / offline imports
TikTokTikTok PixelEvents API
ChatGPT AdsOpenAI Ad PixelOpenAI Conversions API

Server-side tracking does not replace good event design. It improves resilience and matching, but bad events remain bad events.

Conversion Value

If a platform supports value optimization, send accurate value when possible. Value can be:

  • Order revenue.

  • Gross margin-adjusted value.

  • Predicted lead value.

  • Subscription trial value.

  • Offline sales value.

  • Qualified pipeline value.

Value optimization is powerful only if value data reflects actual business economics.

Implementation Checklist

  1. List every conversion event and business definition.

  2. Choose primary optimization events by objective.

  3. Map events to Meta, Google, TikTok, ChatGPT Ads, and analytics.

  4. Add deduplication IDs for browser and server events.

  5. Confirm event values and currency.

  6. Validate event firing in staging and production.

  7. Compare platform counts against analytics and backend truth.

  8. Document attribution windows and reporting assumptions.

  9. Review tracking after every site, checkout, form, or CRM change.

Common Failure Modes

  • Purchase fires on page refresh.

  • Lead fires before form validation.

  • Browser and server events double count.

  • Test events reach production campaigns.

  • CRM-qualified leads are never sent back to ad platforms.

  • Offline sales are missing.

  • Consent mode or cookie settings silently reduce signal.

  • Event names differ across platforms and reports.