
Choose a ChatGPT Ads conversion event by the real customer action, then document the trigger, data shape and value before configuring a campaign goal. Use a standard event when it fits. A page view, a started checkout and a completed purchase are different actions; giving them the same business meaning makes the report harder to trust.
Begin with one important journey and an event worksheet. This guide helps a business owner and implementer agree what should be measured. It does not install the Pixel or replace a review of account access. Use the launch-readiness guide for that earlier decision.
1. Write the success condition in ordinary language
Describe the result before choosing its technical name. For a service business, the useful action might be an enquiry successfully accepted by the form system. Clicking the Send button is an attempt; an accepted submission is a different outcome. For an online shop, adding an item to a cart does not establish that a purchase completed.
Name the business record that supports the event: a saved enquiry, confirmed booking or completed purchase. Assign someone who can inspect that record. If the developer and marketing owner disagree about the success condition, resolve the disagreement before adding another tag. A precise definition is easier to test than a vague instruction to track conversions.
2. Match the action to a supported event
OpenAI’s supported-events reference defines the standard names and their data shapes. The following working shortlist covers common website journeys. Choose only the actions relevant to your service; this is not a requirement to install every row.
| Customer action | Standard event | Data type |
|---|---|---|
| Important page load | page_viewed | contents |
| Specific product or content view | contents_viewed | contents |
| Item added to cart | items_added | contents |
| Checkout begins | checkout_started | contents |
| Purchase completes | order_created | contents |
| Lead form successfully submitted | lead_created | customer_action |
| Meeting or consultation booked | appointment_scheduled | customer_action |
| Free trial begins | trial_started | plan_enrollment |
| Paid subscription begins | subscription_created | plan_enrollment |
For page loads use page_viewed; for a specific content item, including an interaction after loading, consider contents_viewed. The event name describes what happened, not how valuable you hope the visitor will become. App installs and opens have separate Conversions API-only requirements; do not assume a website Pixel supports every event in the full reference.
3. Define a trigger that excludes failed attempts
Choose the point where the application confirms success. A validation error, abandoned checkout or rejected form should not satisfy that condition. Test both a successful path and an unsuccessful one. Save the expected outcome before testing so the reviewer does not reinterpret an accidental event as a pass.
For cash-on-delivery businesses, write down how the site distinguishes an order record, payment and eventual delivery. An order submission does not prove cash was collected or goods were delivered. Do not rename a pending commercial outcome as paid revenue. Review your integration’s actual trigger against the documented event meaning and keep later fulfilment reconciliation separate.
Illustrative case: a repair company wants to measure consultation requests. Its first implementation fires on every click of the form button, including incomplete forms. The revised acceptance rule waits for a successfully stored enquiry, uses lead_created, and records a test reference. This example describes a proposed implementation decision, not a measured campaign result.
4. Check data types and currency units
Every event data object needs the matching type. If an amount is included, a currency is required. OpenAI uses integer amounts in the currency’s standard minor unit. Do not send a displayed decimal price without converting it correctly, or apply one currency’s number of decimal places to every currency.
| Illustrative value check | Correct interpretation | Error to catch |
|---|---|---|
| USD 49.95 event value | amount: 4995, currency: "USD" | Sending 49.95 instead of integer minor units |
| JPY 4,995 event value | amount: 4995, currency: "JPY" | Multiplying every currency by 100 |
| Two items at USD 20 each | Item amount 2000, quantity 2; event total 4000 if no other adjustments | Treating a line total as a per-unit price |
Define which adjustments are represented in the event total and reconcile them with the actual transaction. Item amounts describe one unit; quantity is supplied separately. A correct payload format cannot tell you whether the underlying commercial value was chosen sensibly. Keep your value rule in the worksheet and avoid changing it silently between reports.
5. Separate sending an event from selecting a campaign goal
OpenAI’s conversion-tracking guide distinguishes the receiving data source, conversion event setting and campaign. Sending an event does not automatically select it as a campaign goal. A setting chooses an event from a source; it does not make the website trigger run.
For an authorised account, have the campaign owner confirm that the setting uses the intended source and action, and that the intended campaign is attached. Follow the current documented workflow for that account rather than assuming all interfaces expose identical controls. Keep server credentials out of website source and screenshots used for handoff.
Use a custom event only when no suitable standard event describes the action. Follow OpenAI’s name and data-shape rules instead of inventing a second spelling of a standard purchase or lead. A custom label can be useful for a distinct business step, but its existence does not establish campaign optimisation support or advertising attribution.
6. Sign off a small event worksheet
| Worksheet field | Illustrative lead example | Acceptance evidence |
|---|---|---|
| Business action | Enquiry accepted and stored | Safe test reference in form records |
| Event and shape | lead_created; customer_action | Observed payload matches definition |
| Failure exclusion | Invalid form does not qualify | Controlled unsuccessful submission |
| Source and campaign | Named intended source and setting | Owner confirms correct mapping |
| Value policy | No invented revenue value | Written rule approved by business owner |
| Review owner | Named maintainer | Change log and repeatable test |
Perform one controlled action, note its time and inspect the intended source for reception. A tag manager saying “fired” is not the same evidence as an event arriving. Keep reception separate from attributed conversions: an event can arrive without receiving advertising credit. Use the official troubleshooting reference for the specific failed step.
If browser and server implementations describe the same action, agree their shared identity before enabling both; do not solve duplicates by changing the business meaning. Detailed deduplication needs its own implementation review. For broader measurement planning, use the conversion-goal worksheet as a planning example while keeping each advertising platform’s technical fields distinct.
Frequently asked questions
Should a checkout start count as a completed purchase?
No. Keep checkout_started and order_created tied to their different documented actions. Check the real application state, not only the page URL.
Do I need every supported event?
No. Start with the events that answer a real business question and can be tested accurately. Add others when they have a clear owner and purpose.
Can I invent a revenue value for every lead?
Do not present an assumed lead value as collected revenue. If a business uses a planning value, document its basis and keep the reporting label clear.
Does an event arriving prove an attributed conversion?
No. Event reception, goal configuration and advertising attribution are separate checks. Inspect the relevant evidence for each.
Pingback: ChatGPT Advertising: How ChatGPT Ads Work & How to Launch