
When a cash-on-delivery order exists in WooCommerce but its ChatGPT Ads event is missing, trace one order through the integration before changing the campaign. Establish what action the store intends to measure, whether that action triggered an event, whether the request was accepted and whether the platform received it. Attribution comes after these checks.
Do not treat the order’s status label as proof that cash was collected. WooCommerce’s Cash on Delivery documentation says COD orders enter Processing before payment collection, with completion following confirmation of collection. This distinction matters when an integration waits for payment rather than order placement.
1. Write down the counting rule
Ask the store owner to finish this sentence: “We want to measure an order when…” Possible business milestones include a checkout order being placed or payment being confirmed. These describe different moments. Neither should be silently substituted for the other in a report.
Then inspect the integration’s documented trigger and current configuration. A setting labelled Purchase does not by itself explain whether it waits for a payment callback, an order-status change or another signal. Ask the developer to identify the actual trigger if the documentation is unclear. Record the plugin or custom-integration version alongside the answer.
For a COD store choosing order placement, cash collection and fulfilled revenue still need separate business records. For a store choosing payment confirmation, an order existing before collection may correctly remain outside that event. Align the chosen milestone with the campaign’s measurement definition before diagnosing a technical failure.
2. Build a record for one order
Choose an order that you are authorized to inspect. In a controlled test, use the site’s supported test process and avoid unnecessary charges or real customer information. Record identifiers and diagnostic states privately; do not publish API keys, customer details or unredacted logs in a support thread.
| Field | Evidence to collect | Why it matters |
|---|---|---|
| Store order | Internal ID, placement time, payment method and status | Establishes the local action being investigated |
| Counting rule | Intended milestone and actual configured trigger | Separates an expected wait from a missing trigger |
| Consent | Applicable consent state and integration behavior | Identifies a deliberate collection restriction |
| Event identity | Event name, Pixel ID and event identifier | Connects browser, server and platform records |
| Delivery | Queue state, attempt time and sanitized response | Shows whether a request left the integration |
| Platform receipt | Corresponding received-event evidence | Separates local success from platform receipt |
Keep the original event time separate from the attempt time. If a background task retries later, those two timestamps answer different questions. Also record which clock and timezone each screen uses, so a difference in display is not mistaken for a different order.
3. Find the first missing piece of evidence
Start with the local order and move forward. If the configured trigger never occurred, investigate that trigger before rotating credentials. If an event was generated but is still queued, inspect the integration’s queue and scheduled-task mechanism. If an attempt was rejected, preserve its response and correct the specific problem it identifies.
An integration may use its own queue, WordPress cron or another delivery mechanism. Confirm which one applies. Ask the developer or host to inspect the relevant mechanism directly, using the affected event and its attempt time as the starting point.
Browser and server paths need separate observations. A browser event can depend on a page and script running. A server request has its own trigger, consent requirements, credentials and delivery state. Seeing a pixel load does not prove that the server sent an order event, and a completed server request does not prove that the browser path ran.
| First failing checkpoint | Focus the investigation on | Success evidence |
|---|---|---|
| No local event generated | Milestone, integration trigger and consent | The expected authorized action creates an event record |
| Event remains queued | Worker or scheduling mechanism and its logs | A recorded attempt processes that specific event |
| Request rejected | The returned validation or authorization error | Corrected request is accepted under the documented rules |
| Local send reported, no matching receipt found | Pixel/account selection, time range and event identity | The corresponding received event can be identified |
| Event received, no attributed conversion | Campaign measurement and attribution checks | Receipt and attribution are assessed as separate states |
4. Check identity and time before retrying
OpenAI’s Conversions API documentation requires a stable event ID and an integer Unix timestamp in milliseconds. It currently permits events from the previous seven days and no more than ten minutes into the future. Use the time of the actual action being measured, rather than changing an old event’s timestamp to make it appear recent.
When the same conversion is sent from browser and server, the documentation requires matching Pixel ID and event identity; the API ID corresponds to the pixel event_id. Retry the same event with its original identifier. A new identifier on every retry can make one business action look like several events.
For the full cross-channel procedure, use our Pixel and Conversions API deduplication guide. This order-level investigation does not require resending every historical order. Restrict a recovery attempt to the authorized event and applicable retention and consent rules.
5. Use a small, explicit decision example
Illustrative example: a shop measures orders placed at checkout. A COD order is created at 09:15, but the integration’s documentation says its server event waits for a payment-confirmation callback. There is no local event record yet. The evidence points to a mismatch between the intended milestone and the integration’s trigger, not a failed API request.
The next action is to have the owner and developer align that definition and implement the supported trigger. It is not to mark an unpaid order paid simply to make tracking fire. After the correction, a permitted test should show the expected local event, delivery evidence and platform receipt.
A different order may already have an event and a rejected response. That is a delivery investigation. Keep these cases separate so a repair for one does not obscure the cause of the other. These examples are reasoning exercises, not claims about a particular plugin or a test we performed.
6. Close the investigation with evidence
Write down what changed, who approved it, the retest order and the remaining limitation. Confirm the event’s amount and currency against the intended business action without confusing order value with collected cash or fulfilled profit. Keep the same milestone in the reporting worksheet after the technical repair.
Once a received event is visible, use our received events versus attributed conversions guide. For the later review, the first-week reporting worksheet keeps settings, observations and decisions together. Neither a local “sent” label nor platform receipt alone establishes attributed revenue.
Common questions
Should I change a COD order to Completed to force a conversion?
No. Keep the order record truthful. Investigate and correct the measurement trigger instead of altering the business status to satisfy it.
Should I install a second tracking plugin as a quick test?
First inventory the existing browser and server integrations. Adding another sender can complicate identity and duplicate-event diagnosis. Prefer a controlled test of the current path with a clear owner and a rollback plan.
Can I call the issue fixed after one accepted request?
Confirm the expected local action, request outcome and matching platform receipt, then check the next permitted order. Record attribution separately. A successful diagnostic request is useful evidence, but it does not establish that every checkout path is covered.
Pingback: ChatGPT Advertising: How ChatGPT Ads Work & How to Launch