Why this comes first
A platform optimises toward what it can see. If it sees page views, it finds people who view pages. We wire real outcomes in before spend starts.
What we set up
| Layer | Detail |
|---|---|
| Data source and Pixel | Installed across relevant pages, firing on real lead and purchase events |
| Conversions API | The same events from your server, with the same event ID for deduplication |
| Click reference | oppref preserved through redirects and stored with the lead |
| Advanced matching | Hashed first party details where your privacy notice and the law permit |
| UTM convention | A paid medium on every ad, so ads and organic ChatGPT referrals stay separate |
| Offline outcomes | WhatsApp and phone sales sent back from the CRM against the original click |
| Reconciliation | Weekly check of platform numbers against CRM records |
The method is explained in the conversion tracking guide.
Quick answers
How is the fee set?
Scope and fee are quoted in AED after we review your current ad accounts and tracking. Media spend is paid by you directly to OpenAI.
Who owns the account and data?
You do. The Ads Manager account, pixel, feeds and data sit under your company. We work as invited users.
We already have Google and Meta tracking. Is this separate?
It is a separate pixel and API, and the same discipline. We usually extend the server side setup you already have so one lead record feeds all three platforms.
Will the numbers match our analytics?
Not exactly. OpenAI lists attribution windows, time zones, consent conditions, deduplication and modelled conversions as normal reasons for differences. We reconcile weekly against the CRM, which is the number that counts.