TrueTrackedTrueTracked
Destination
ChatGPT Ads+TrueTracked

Conversion tracking and attribution for ChatGPT Ads

See which ChatGPT ads bring in sales, and send those conversions back to OpenAI through the Conversions API, deduplicated against the ChatGPT pixel.

Get StartedRead the setup guide

What you get

Spend and attribution down to the ad

Connect your ad account and ChatGPT Ads spend, clicks and impressions sit beside the orders TrueTracked attributes to them, from campaign to ad group to ad.

Server-side Conversions API

Purchases and funnel events are sent to OpenAI from our servers, so they can still arrive when a browser blocks the pixel.

Browser pixel and server, counted once

TrueTracked also loads the ChatGPT pixel and gives both copies of an event the same ID. Purchases use the order ID, so a sale is not counted twice.

OpenAI's numbers next to yours

The conversions and sales ChatGPT Ads reports for itself are imported too, so you can compare them with TrueTracked's attribution on the same screen.

Events sent to ChatGPT Ads

Five events map to OpenAI's standard conversion events. TrueSignal shows the same list in your dashboard, so you can create the matching events in Ads Manager.

Purchase campaigns usually use order_created as their goal.

See the setup guide →
TrueTracked eventChatGPT event
page_viewedpage_viewed
product_viewedcontents_viewed
product_added_to_cartitems_added
checkout_startedcheckout_started
checkout_completedorder_created

What is sent with every event

OpenAI matches conversions to ad clicks using the customer details that travel with each event. The more of them your checkout collects, the more conversions it can match.

Hashed with SHA-256

5 fields
  • Email
  • Phone
  • First name
  • Last name
  • External ID

Sent unhashed

8 fields
  • City
  • Region
  • Postal code
  • Country
  • Client IP
  • User agent
  • oppref click ID
  • __obref cookie

OpenAI's Conversions API takes location, IP and its own click identifiers in the clear.

Hashing follows OpenAI's own rules, which differ slightly from Meta's for phone numbers and names.

Why the first copy wins

OpenAI deduplicates on pixel, event name and event ID, and TrueTracked sends the same ID from the browser pixel and the server. OpenAI keeps the first copy it receives and does not merge in details from the second.

That matters in Shopify's checkout, where a browser pixel cannot see the ad click that brought the customer in. So on Shopify, checkout_started and order_created are sent from the server only, with the click ID attached, and the copy OpenAI keeps is the complete one.

Browser pixel
Server
ChatGPT Ads
ChatGPT Ads

ChatGPT sends you two kinds of visitors: people who clicked an ad, and people who followed a link in an ordinary answer. TrueTracked keeps them in separate rows, so ad spend is judged against paid clicks rather than free referrals.

Paid

utm_source=chatgpt + tt_source=chatgpt

Attributed down to the campaign, ad group and ad, and compared with spend.

Organic

utm_source=chatgpt.com

Reported in its own row, with no spend attached.

The ad-level view needs the TrueTracked URL parameters on your ads. See the ChatGPT Ads template.

Set up ChatGPT Ads in four steps

  1. 1

    Connect your ad account

    Create an API key in ChatGPT Ads Manager under Settings, API Keys, and paste it into TrueTracked under Settings, Integrations. Spend, clicks and impressions start flowing into your attribution reports.

  2. 2

    Add the tracking parameters

    Paste the TrueTracked URL parameters into each ad group or ad in Ads Manager, so every paid click can be tied to the ad that drove it.

  3. 3

    Turn on the Conversions API

    Copy your Pixel ID and a Conversions API key from Ads Manager under Conversions, and add them in Settings, TrueSignal. The pair is checked with OpenAI when you save.

  4. 4

    Create your conversion events

    Create the matching events in Ads Manager using the list TrueSignal shows you, and set order_created as the goal for purchase campaigns.

Full walkthrough: ChatGPT Ads setup guide →

ChatGPT Ads integration FAQ

How the ChatGPT Ads integration behaves once it is live. Still unsure? Reach out and we will give you a straight answer.

They do different jobs. The Advertiser API key, from Settings, API Keys in ChatGPT Ads Manager, lets TrueTracked read your spend and reporting. The Conversions API key, from the Conversions section, can only send events to your pixel. The Conversions API key goes into TrueSignal together with your Pixel ID, and the two are not interchangeable.

Yes. TrueTracked loads the ChatGPT pixel on your site and pairs every browser event with a server event that shares its event ID. A second copy of the pixel sends its own events with different IDs, which OpenAI cannot deduplicate against ours.

OpenAI deduplicates on pixel, event name and event ID, and both the browser pixel and the server send the same ID. Purchases use the order ID, so the same sale cannot be counted twice.

OpenAI keeps the first copy of a duplicate event rather than merging the two. Inside Shopify's checkout, a browser pixel cannot see the ad click that brought the customer in, so its copy would arrive first without it and the richer server copy would be ignored. TrueTracked sends checkout_started and order_created from the server only on Shopify, with the click ID attached.

No. OpenAI does not offer a test event code the way Meta and TikTok do. Instead, TrueTracked checks your Pixel ID and Conversions API key with OpenAI when you save them, so a typo shows up straight away rather than as missing events later.

Email, phone, first name, last name and an external ID, all SHA-256 hashed. City, region, postal code, country, client IP, user agent, the oppref click ID and the __obref cookie are sent unhashed, as OpenAI's Conversions API expects.

No. Paid clicks carry utm_source=chatgpt plus the TrueTracked parameters. Visitors who follow a link in an ordinary ChatGPT answer arrive as chatgpt.com and stay in their own row in your attribution report.

Only recent ones. OpenAI accepts events from the last 7 days, so older events are skipped rather than rejected at OpenAI's end.

One per workspace on every plan. OpenAI's browser pixel runs a single pixel per page.

Related integrations

Other destinations

MetaMetaGoogle AdsTikTokTikTokMicrosoft AdsMicrosoft Ads

Sources that feed ChatGPT Ads

ShopifyShopifyWooCommerceWooCommerceWixWixStripeStripe
Get started

Track smarter. Grow faster.

Get clear insights into what drives your sales with TrueTracked.

Get StartedBook a Demo

14-day free trial · No credit card required