The oppref parameter in ChatGPT Ads is OpenAI’s opaque click reference, added to your landing page URL after an ad click so a later conversion can be attributed to it. With measurement consent, the OpenAI pixel saves it in a first-party __oppref cookie for 30 days. For server-side tracking, you must preserve the original value and send it back in the conversion event’s oppref field.

This is the reference page for the parameter: what arrives, how long it lasts, how to move it to a server event, and where it gets lost. The wider setup is in the ChatGPT Ads conversion tracking guide.

What arrives on the landing URL

OpenAI’s own example is ?oppref=gAAAAAb123. Third-party captures of real ad clicks, such as the ones Rankly and buchodi published in spring 2026, show a long token with that gAAAA prefix and a second parameter beside it:

https://example.com/pricing?oppref=gAAAA...&olref=gAAAA...

The gAAAA prefix matches the Fernet token format, which is how those authors read it. OpenAI’s docs call the value opaque and say nothing about its internals, so treat it as a string: do not parse, shorten, re-encode or regenerate it.

olref appears next to oppref in those captures. It is not in OpenAI’s documentation and the pixel does not store it. Ignore it.

The same captures show the click going straight to the advertiser’s URL, with no OpenAI redirect domain in between. That is observed behaviour, not a documented promise, but it means nothing upstream rebuilds the parameter if your own site drops it.

In the published captures OpenAI adds no UTM parameters of its own to paid clicks; the UTMs on those URLs are the advertiser’s. Organic citations from ChatGPT search arrive with utm_source=chatgpt.com. Tag paid traffic with a different source, such as openai (OpenAI’s own template example) or chatgpt, so paid and organic do not merge in your analytics.

The pixel’s cookies and how long they last

When measurement consent is granted, the pixel writes two first-party cookies (Measurement Pixel, cookie expiry, checked 2026-10-17):

Cookie Holds Expiry
__oppref the oppref from the landing URL 30 days after the pixel writes it
__obref a random browser reference for your site 365 days after creation

Each time the pixel captures a non-empty oppref from a URL, even the same value again, it resets __oppref to 30 days. Reading the stored cookie on a visit without the parameter does not extend it. __obref is reused while valid and never extended. Browsers can shorten both, and oaiq("consent", false) deletes both.

The two are not interchangeable. oppref goes on the server event as an event-level field. obref goes inside user, unchanged.

Cookie expiry is a storage limit, separate from the attribution window. OpenAI’s default click window is 30 days.

Flow diagram: a click ID arrives on the landing URL, is stored in a first-party cookie, and is read back at conversion time to attach to a server-side event.
The click ID arrives once, at the start. Everything after that depends on having stored it.

Putting oppref in your own parameter

Campaigns, ad groups and ads accept a query_string_template, and {oppref} is one of its macros alongside {campaign_id} and {ad_id} (Campaign Management, tracking parameters). OpenAI’s example:

{
  "landing_page_configuration": {
    "query_string_template": "utm_source=openai&utm_campaign={campaign_id}&utm_content={ad_id}&click_id={oppref}"
  }
}

That is the cleanest way to get the value into a form field, a CRM or a hosted checkout under a name your system already reads. The alias is for your plumbing only. When you send the conversion, the value still goes in the event-level oppref field. Parameters set at several levels combine, and the more specific level wins for the same key: account, then campaign, then ad group, then ad.

The four ways it goes missing

A redirect drops the query string. A canonical-domain redirect that rebuilds the URL, a locale router that sends visitors to a clean path, or app code that replaces the URL before the pixel loads: each removes oppref before anything reads it. Point ads at final URLs, and carry the full query through any hop you cannot remove.

Consent is denied before init. If your consent platform calls oaiq("consent", false) before init, or the pixel finds a stored denial, it sends nothing and writes no cookie. The symptom looks like a lost redirect. Check the consent state before you blame the URL. Events blocked during denial are not replayed after a later grant.

The visit outlives the page. Someone clicks, leaves, returns two days later from a bookmark and buys. The purchase URL has no oppref; only the cookie or your own store still has it. A conversion tag that reads only the URL loses that sale.

The server event has no browser. A payment webhook arrives from Stripe or your checkout provider, with no cookie and no URL. The click reference has to be written somewhere durable before checkout and looked up when the webhook lands. The Conversions API will not do this for you.

How we carry it to a Stripe webhook

On the Advanced Tracking Academy checkout, built on 6 August 2026, the round trip reuses the path that already carried Meta’s _fbc and _fbp:

  1. At lead and checkout time, the server container reads oppref from the URL and __oppref and __obref from the cookies.
  2. The two Stape Store writers that already save each visitor’s index document add three fields: oppref, oppref_url (the raw URL value) and obref. Empty values are skipped, so the writers do nothing until the pixel has set the cookies.
  3. When a customer ID exists, a re-key writer copies those fields onto the customer’s document.
  4. When Stripe’s webhook arrives, the conversions tag looks up oppref and obref in that document and sends them on the event, oppref at event level and obref inside user.

The server-side GTM build notes cover the tags around this. For checkouts on another domain, the hosted checkout attribution index shows how to keep the lookup key separate from the order ID.

Key the stored value to the checkout or subscription it belongs to, not only to a customer. One customer can click two ads months apart and buy twice; a customer-keyed slot overwrites the first click or credits the second purchase to it. Keep the capture time beside the value, because a click older than the 30-day window will not attribute anyway.

Your own copy also outlives the pixel’s consent switch. When a visitor revokes measurement consent, the pixel deletes its cookies, but a row in your Store or database stays until you remove it. Gate capture, storage, lookup and forwarding on the same consent decision, and test a revocation end to end. OpenAI’s instruction for obref is direct: if the user revokes consent, stop sending it.

The no-JavaScript image tag does not capture or store oppref either. If you use it, pass the value URL-encoded in the oppref parameter, or leave the parameter out (Image Tag).

What you lose without it

Without oppref, OpenAI loses the direct click reference. Customer information can still help match the conversion to an ad: the pixel’s automatic advanced matching exists for cases “when a click identifier is unavailable”, and a server event can carry hashed customer fields (pixel docs, checked 2026-10-17). Nothing guarantees that match. The conversion can also appear as a view-through conversion within one day of an eligible impression, which is why OpenAI recommends sending every conversion, with or without the parameter. OpenAI’s pixel docs say bidding, billing, CPA and conversion optimization stay click-through based, so a build that drops oppref gives the bidder less to learn from.

When a conversion is missing, the troubleshooting checklist separates receipt, this click-reference path and the campaign link.