Your OpenAI Ads Identifier Coverage Is at 0%? Here's What to Do

You opened OpenAI Ads Manager, found identifier coverage at a flat 0%, and understandably worried something is broken. The good news: this is one of the most common and most fixable setup issues in ChatGPT ads. It almost always means your events are firing, but arriving with nothing OpenAI can match them on. Here is how to confirm that and fix it.

What 0% coverage means, and what it does not

First, separate two different problems that look similar:

• 0% identifier coverage means conversion events are reaching OpenAI, but none carry a usable identifier, so none can be matched to an ad. The pipe works; the events are just blank.
• 0 conversions is a different thing entirely, often no events firing or simply an early channel with low volume. That case is covered in why your ChatGPT ads show 0 conversions.

If your coverage is zero specifically, keep reading. This is a signal problem, not a volume problem.

Why your coverage is stuck at zero

Run down these causes, most common first:

1. No user object on your events. The single most common cause. Your events send the conversion but omit the optional user object, so there is nothing for OpenAI to match. This alone produces a flat 0%.
2. Browser pixel only, no server events. A pixel-only setup often cannot attach reliable identifiers, and much of it is lost to ad blockers and tracking protection before it arrives.
3. Consent blocking every signal. An over-aggressive consent setup can strip out every identifier, including non-PII device and network signals that are safe to send.
4. Identifiers sent wrong and rejected. Raw values where hashes are required, or malformed hashes, get dropped, leaving coverage at zero.

The fix, step by step

1. Confirm you are sending server-side. Events should flow through OpenAI's Conversions API, not just a browser pixel. Server-side delivery is what lets you reliably attach identifiers in the first place.
2. Attach a user object to every event. This is the actual fix for a flat zero. Every conversion event should carry the optional user object.
3. Lead with device and network signals. Add IP address and user-agent first. They need no protected customer data and move most merchants off zero immediately.
4. Add a hashed email where consent allows. For a higher-quality match, include a SHA-256 hashed email, but only where the shopper has consented and protected-customer-data rules permit. Never send it raw.
5. Recheck after events flow. Give it a day or two of real traffic, then confirm coverage has climbed in Ads Manager.

If you use Reach, it is already handled

This is exactly what Reach's identifier feature does for you. It attaches a user object to every server-side event automatically, device and network signals first, hashed email where consent allows, so you do not have to configure any of it. For most stores, installing and sending live events is enough to move coverage off zero on its own.

The honest privacy note

A coverage of zero does not mean you must start exposing customer PII. The opposite: most merchants clear zero using only device and network signals, with no protected data at all. Keep it minimal, keep emails hashed, keep it consent-gated. You can read the full picture in identifier coverage in OpenAI Ads, explained.

Move your coverage off zero. Install Reach on the Shopify App Store to send server-side ChatGPT Ads events with a privacy-first user object attached automatically, so OpenAI finally has something to match your conversions on.