ChatGPT Ads attribution, from the paid click to the closed deal

Two kinds of ChatGPT traffic, two pages. The ChatGPT integration is earned traffic: a reader clicks a link ChatGPT cites in its answer, and LeadJourney recognises the referral with no setup. This page is paid traffic: a reader clicks an ad OpenAI places beneath an answer. Paid clicks are credited to their ChatGPT campaign, earned visits stay on the organic ChatGPT source, and when one buyer did both, each gets its share of the deal.

OpenAI began testing ads in ChatGPT in the United States in February 2026, for adults on the Free and Go plans; Plus, Pro, Business, Enterprise and Edu accounts have no ads. An ad appears beneath an answer, labelled as sponsored and set apart from it. In May 2026 OpenAI opened its Ads Manager at ads.openai.com to US businesses as a self-serve beta, with CPC bidding, a pixel and a Conversions API.

No, and neither can LeadJourney. OpenAI says advertisers do not get chats, chat history, memories or personal details, only aggregated performance such as views and clicks. What LeadJourney records starts at your site: the paid click with its oppref, the landing page, every later visit, the lead and the deal. That is enough to tell which campaign and which ad group produced revenue.

OpenAI's click identifier for ChatGPT ads, which it calls an opaque attribution identifier. The OpenAI pixel reads it from the landing page URL and keeps it in a first-party cookie, __oppref, for 30 days. The Conversions API does not capture it for you: your own system has to store it and pass it on unchanged. LeadJourney captures it server-side with the click and keeps it on the journey, so it is there when the deal closes. OpenAI's tracking template can also add UTM parameters with macros such as {campaign_id} and {ad_id}.

It can run alongside it or instead of it. OpenAI describes the pixel and the Conversions API as complementary, and when the same event arrives both ways with the same event ID under the same Pixel ID, it keeps the first one and ignores the other. LeadJourney's tracking is server-side, so it does not depend on the pixel, and each event it sends through the Conversions API carries an event ID, so a conversion the pixel also reports is counted once.

Because it counts differently, not wrongly. Ads Manager credits a conversion inside a 7, 14 or 30 day click window, reports view-through conversions within a day of an impression as their own metric, dates results on the ad interaction by default, and asks you to allow at least a day for conversions to appear. Your CRM only knows the people who became leads and deals. LeadJourney shows both: Ads Manager's conversions where you buy, and the revenue ChatGPT ad clicks actually produced, measured once across every channel.

Yes, that is the point of tracking server-side. The click, the oppref and the visit are recorded on your own domain before an ad blocker, Safari or a declined banner can remove them, at 95%+ accuracy. The OpenAI pixel sends nothing while measurement consent is off, and does not send those events later; LeadJourney shows you the measured numbers.

In LeadJourney, yes. The ChatGPT click is stored on the visitor's LeadJourney Click ID, so when the same person comes back through Google brand search, an organic ChatGPT answer or a typed URL and converts, the ChatGPT campaign is still part of that journey. Multi-touch models then share the revenue between the ad and the channel that closed, instead of handing all of it to the search.

Any CRM stage or paid order you map, sent through the Conversions API as one of OpenAI's standard events: a qualified lead as lead_created, a won deal or an order as order_created, with the value and its currency. OpenAI's list also has appointment_scheduled, subscription_created and trial_started, plus custom events. A conversion-optimised campaign bids for one standard event, and custom events cannot be optimisation goals, so map the stage you want bidding to learn from to a standard one.

In LeadJourney, yes: the journey has no window, so the deal is credited to the campaign that started it regardless of the cycle length. Ads Manager credits conversions inside a click window of 30 days at most, so for a long cycle map an early stage that predicts revenue, such as the qualified lead, as the event a conversion-optimised campaign learns from. The report that matches the late revenue to the ad lives in LeadJourney.

An event carries the oppref, the event type, an event ID and, when there is one, the value and currency, and nothing for a stage you have not mapped. OpenAI requires any customer field sent as a match key, such as an email or a phone number, to be SHA-256 hashed. LeadJourney itself processes and stores data in the EU, signs a data processing agreement, and tracks first-party and server-side, so consent decisions are respected rather than worked around.

Not natively. HubSpot's ads tool connects Meta, Google, LinkedIn, Microsoft and TikTok ad accounts, and ChatGPT Ads is not on that list. LeadJourney records the ChatGPT ad click itself, follows each lead into HubSpot to the deal next to every other channel, and sends the qualified leads and won deals back through OpenAI's Conversions API.

An active ad account in OpenAI's Ads Manager, and the CRM or shop where your revenue is recorded. Add the LeadJourney script, connect both and map stages to conversion events; most accounts are live in about 21 minutes, and our team will do the setup with you on a call if you prefer.

The ChatGPT Ads integration is part of the platform rather than a paid add on. Plans are priced by ad spend instead of seats, so your whole team and your agency can share one workspace, and every plan starts with a 14 day free trial without a credit card.