This is the implementation checklist — the technical companion to the measurement guide. Work through it in order and your OpenAI Ads tracking will be clean, deduplicated, and trustworthy before a single dollar of spend depends on it.
Concepts: pixel, Conversions API, and event dedupe
1 — Data layer events
Standardize a data layer so every conversion event has a consistent shape before anything fires. Define the events you care about, attach a unique event_id at the moment the action happens, and keep the payload small and predictable. A clean data layer is what lets the pixel and the server send the same event without drift.
- ›Define the conversion events you'll track (e.g. lead_created, audit_booked).
- ›Generate a unique event_id when the action occurs, not on page load.
- ›Keep a consistent payload shape across pixel and server.
- ›Avoid leaking PII into the data layer beyond what tracking actually needs.
2 — HubSpot form conversion
Tie the conversion to the real outcome: a HubSpot form submission, not a page view. Hook the form's submit/callback so the conversion fires only when the lead is actually captured, and pass enough context to match the event to its HubSpot contact record downstream. This is what lets you grade lead quality later instead of optimizing for clicks.
3 — Server event endpoint (Conversions API)
Stand up a server-side endpoint that sends the same conversion to the Conversions API. The browser event and the server event carry the same event_id so the platform deduplicates them into one conversion. Critically, the Conversions API key lives only on the server — never in client code.
4 — Event naming
Pick one naming convention and enforce it everywhere — pixel, server, and CRM. Consistent, lowercase, descriptive event names (lead_created, audit_booked, quote_requested) make reporting legible and prevent the silent drift where the pixel and server disagree about what an event is called.
5 — Privacy and consent
Honor consent before tags fire, collect only what you need, and document what you send and why. Browser-side measurement is increasingly partial under modern privacy controls — which is the whole reason server-side reporting matters — but server-side does not exempt you from consent. Build the consent gate into both paths.
6 — QA checklist before you trust it
- 01Trigger a real conversion and confirm the pixel event fires with an event_id.
- 02Confirm the server sends the same event with the same event_id.
- 03Confirm the platform deduplicates to a single conversion.
- 04Confirm the lead lands in HubSpot and can be matched to the event.
- 05Confirm consent gating blocks tags when consent is withheld.
- 06Confirm no secret key is exposed anywhere a browser can reach it.