Event quality is a diagnostic of whether the information received from a Pixel or data source is useful for measurement. It is not a campaign-performance score and does not guarantee that a conversion will be attributed to an ad. OpenAI refreshes the assessment daily using seven complete calendar days, so a corrected setup may take time to show in the result.
Start with real events and consent
Use genuine customer actions and identifiers your business is permitted to send. Do not create extra events, invent customer IDs, reuse another person’s click reference or change an event time to improve a warning. Check your consent flow and current OpenAI data requirements before adding customer fields.
Warning-to-check guide
| Warning | First checks |
|---|---|
| Limited email or customer ID | Confirm the event sends an eligible, stable identifier where permitted; review supported formatting and hashing. Never use a shared placeholder ID. |
| Ad click information missing or unconnected | Preserve the actual oppref through redirects, language changes, checkout and browser-to-server handoff; pass it on CAPI events when available. |
| CAPI events delayed | Check queues, retries, scheduled uploads and failed requests. Send promptly after the real action and preserve its original timestamp. |
| Conversion matches need review | Check duplicate tags, repeated callbacks, retries, timestamps and consistent event IDs for browser/server copies. |
| Many conversions linked to one interaction | Check refreshes and repeated triggers, but keep legitimate repeat orders or separate actions. Distinct actions need distinct event IDs. |
| Limited additional matching information | Review which supported phone, name/location, IP or user-agent fields your integration actually has and is permitted to send. |
| Limited event types | Map the real customer journey and capture applicable browsing, intermediate and completed actions. Not every business uses every stage. |
| Limited Pixel/CAPI activity | Confirm requests are accepted by the intended data source; an installed tag or attempted request alone is not proof of receipt. |
| Limited activity for a configured goal | Compare the goal’s event name and configuration with the event that actually fires. A genuinely rare action may simply have low volume. |
Fix the measurement path in order
First confirm one real action sends an accepted event to the correct data source. Then check the event name and configured goal, click information, timing and deduplication. Add permitted matching fields only when your integration supports them and your privacy/consent controls allow them. If the business closes leads in a CRM after a call or WhatsApp conversation, a browser Pixel cannot see that later sale; use a supported server-side process to report the true outcome.
For a Pakistan online store, trace the actual journey through any payment or checkout redirect and reconcile the event with the store’s real order record. For cash-on-delivery, distinguish an order placed from any later confirmed or fulfilled status your business chooses to measure; use an event only when the corresponding action has happened. These are measurement design examples, not special OpenAI event rules.
After a correction, verify that new events arrive and allow the seven-day assessment window to incorporate them. Do not treat an unchanged score the next day as proof that the fix failed. A score can also be unavailable when there is too little activity or attribution evidence to assess.
Quick answers
Does a low score mean my campaigns are failing?
No. Event quality assesses measurement information and does not predict campaign performance or guarantee attribution.
How often does it refresh?
Daily, using seven complete calendar days with additional time for recent events to arrive. Changes can appear gradually.
Should I send extra events to clear a warning?
No. Send only real business actions and permitted information. Do not invent events, identifiers, timestamps or click references.
Why is one goal flagged while another looks healthy?
A configured-goal warning can reflect low received activity for that event even when other events on the same source are arriving.
Will the Pixel track a sale closed later in WhatsApp?
No. It can record website activity, but a later off-site sale needs to be recorded through an appropriate supported server or CRM integration.