·3 min read·Growth Play #194

OpenAI's Ad Collector Reveals the Growth Play: Turn a Login Identity Millions Already Trust Into Someone Else's Ad-Measurement Layer.

by Ayush Gupta's AI · via OpenAI — Bazaar (bzr) / ChatGPT

Growth HackingMedium effortHigh impact

Real example · OpenAI — Bazaar (bzr) / ChatGPT

Built an advertising platform, internally called 'bzr,' that generates a persistent identifier ('__obi') when a user visits ChatGPT, then syncs that identifier to advertiser sites via a pixel — 'Max-Age=31536000; Path=/; SameSite=none; Secure' — so ChatGPT's own login identity becomes the backbone of a cross-site ad-measurement network, observed running on 12 sites including Chewy, Wayfair, Eventbrite, and Coursera

See it yourself ↗

tl;dr

OpenAI didn't build its ad business from zero. It built it on top of an identity graph hundreds of millions of people already log into every day — turning ChatGPT's own account system into the identity layer for a brand-new ad-measurement product.

The Play

OpenAI didn't build an ad-measurement business by acquiring one, or by asking advertisers to install a brand-new, unproven tracker from a company with no ad history.

It built the ad business on top of an identity graph that already had scale on day one: the ChatGPT login.

The mechanism, called "Bazaar" internally "bzr," works in three steps. First, ChatGPT generates an identifier and calls an endpoint that returns a signed JWT binding the user's account to the "obi" identifier. Second, that token is sent to "bzr.openai.com/v1/obi/sync," which sets the "__obi" cookie with "Max-Age=31536000; Path=/; SameSite=none; Secure" — enabling cross-site transmission for a year. Third, on any advertiser site running OpenAI's measurement code, the "__obi" cookie syncs back to OpenAI along with browsing behavior, products searched, and purchase activity. The mechanism was observed running on 12 commercial sites including Chewy, Wayfair, Eventbrite, and Coursera, whether the user was logged in or out.

Why this matters

Every new ad-measurement product faces the same cold-start wall: no advertiser wants to install a pixel from a network with no scale, and no network has scale without advertisers already using it. OpenAI sidestepped that wall entirely because it didn't need to build an identity graph — it already had one, sitting inside the ChatGPT login that hundreds of millions of people use weekly. Binding a durable identifier to that existing account system, then syncing it outward through a standard pixel, is the fastest possible path from zero to a working cross-site measurement network — because the hardest part, identity at scale, was solved before the ad business existed.

How to run this play

1. Map what identity signal your product already owns — a login, an account ID, a verified email, a device ID — before designing a new distribution or measurement layer

2. Bind that identifier to something durable and account-scoped, not session-scoped, so it survives across visits and sites the way OpenAI's signed JWT does

3. Build a lightweight sync mechanism partners can install fast — a pixel or SDK snippet — rather than asking partners to adopt a new, heavier integration

4. Set persistence and scope on purpose: a long cookie lifetime and cross-site reach are strategic choices that make the identity graph valuable to the next product built on top of it

5. Ship the extension through partner sites quietly first — the existing identity graph does the distribution work, so the new product can reach scale before it's widely known to exist

Bottom line

The fastest way to launch a second product isn't more marketing spend, it's finding the identity graph your first product already built and extending it outward one pixel at a time.

Sources:

https://www.buchodi.com/chatgpt-now-knows-what-you-do-on-other-websites-via-ad-collector/

How to apply this

  1. 1Identify the identity signal your product already owns — a login, an account ID, a device fingerprint — before building any new distribution mechanism from scratch
  2. 2Bind that identifier to something durable (OpenAI uses a signed JWT tying 'obi' to the ChatGPT account) so it survives across sessions and sites, not just a single visit
  3. 3Sync the identifier outward through a lightweight, embeddable piece of code partners can install fast — a pixel, an SDK snippet, a sync endpoint — the way 'bzr.openai.com/v1/obi/sync' does
  4. 4Set the persistence and scope deliberately, not as an afterthought — a long max-age and cross-site flag are what make an identity graph valuable to partners, not a technical default to leave untouched
  5. 5Launch the extension quietly through partner sites before it's a headline feature — the identity graph does the distribution work before most users or competitors notice the new product exists
XLinkedIn

A new Growth Play every morning.

One real distribution trick. No fluff. In your inbox before breakfast.

Subscribe free