ChatGPT ads conversion tracking: from a site action to a campaign goal
Set up and verify the path between a completed business action, your event source and the conversion goal selected in ChatGPT Ads Manager.
A button click is not necessarily a lead, and a thank-you page visit is not necessarily a paid order. Choose the business action you need to measure before installing anything.
The tracking path has several parts: the site action, the event sent, the data source receiving it, and the goal the campaign uses. If a link in that path fails, the report may stay empty.
Write an event definition someone else can test
For a lead form, define the event as a successfully accepted inquiry. For an order, use a completed order record with a stable ID. If a form submission fails or a payment is declined, that action should not become a successful conversion.
Document the event owner, the success condition and whether the action can happen more than once for the same customer.
Connect the source and the campaign goal
OpenAI’s conversion tracking guide describes the measurement source and event configuration. Sending an event and attaching a conversion goal to a campaign are separate steps.
The source’s pixel identifier and its data-source identifier serve different configuration purposes. Copy the value required for the specific step rather than reusing whichever ID you first found.
If both browser and server send the same event, use the documented deduplication scheme. A completed order should not appear twice just because you added another transport.
Test the entire successful path
- Complete a controlled test action on the intended destination.
- Confirm the event is sent only after success, with the expected event name and identifier.
- Check the correct source receives it.
- Verify the campaign is connected to the intended conversion goal.
- Repeat a failure path and a refresh to check for accidental extra events.
Use the platform’s documented test or validation facilities where supported. Do not send invented purchases into live reporting just to make the dashboard look active.
Separate received events from attributed conversions
Conversion measurement requires an eligible matching ad interaction within the reporting conditions. A successfully received event can be a genuine website event without receiving credit for the ad campaign.
Compare the event stream with order or CRM records first. Then investigate attribution differences using the window, timezone, event definition and date basis. The reporting guide explains the settings that affect the displayed totals.
If the source receives events but the campaign shows none, do not reinstall everything immediately. Check the campaign connection and whether there was a qualifying interaction. If no events arrive at all, investigate the sending path.
Keep personal data and credentials under control
Collect and send only the fields your supported setup needs, with the appropriate consent and privacy disclosures. A server API credential belongs on the server, never in page source or a public tag-manager variable.
Use the pixel versus Conversions API guide when choosing an implementation. Aim for a completed-action count you can reconcile with your business records.
Sources and review date
Official documentation checked on 2026-10-12. Availability and features can change; confirm them before launch.