Every Lead and Sale From ChatGPT Ads Counted Once, Matched Correctly and Ready to Optimise
ChatGPT Ads can report clicks, but it cannot report revenue until you send conversions back. As a conversion tracking and server-side tracking specialist, I install the OpenAI Pixel, the OpenAI Conversions API and server-side Google Tag Manager on Stape, so every lead, trial and purchase reaches OpenAI once, with the right value, and shows up in GA4 and Looker Studio.
ChatGPT AdsPixel + CAPIOpenAI Pixeloaiq in the head
Conversions APIServer-side events
Server GTMYour own subdomain
order_createdShopify, Stripe, PayPal
lead_createdCRM won deals
Looker StudioChatGPT Ads ROAS
GA4ChatGPT traffic
AutomationRetries & alertsChatGPT AdsConversion Tracking
OfficialStape PartnerOne clean conversion record per lead or sale, sent from both browser and server and deduplicated on a shared event ID. Click through the views to see how I report it: Overview, Click ID and Match, Deduplication, Server GTM, E-commerce, Lead Gen and CRM, Revenue and SaaS.
ⓘ Demo dashboard with sample data for a ChatGPT Ads advertiser. Yours is built on your own OpenAI, GA4 and CRM data.Want to know how many ChatGPT Ads conversions you are missing?
Get a Free Tracking AuditBy MD Niamul · Conversion tracking specialist · Updated October 2026
ChatGPT Ads conversion tracking sends your leads, sign-ups and purchases back to OpenAI. ChatGPT Ads can report clicks on its own, but it cannot report revenue or optimise toward sales until it receives conversion events. The OpenAI Pixel sends them from the browser, the OpenAI Conversions API sends them from your server, and a shared event_id makes sure each conversion is counted only once.
Sending your leads, trials and sales back to ChatGPT Ads with the OpenAI Pixel and the Conversions API, so OpenAI can report and optimise on real results.
E-commerce, SaaS and lead generation businesses running ChatGPT Ads, and the agencies that manage them.
The oaiq pixel loaded high in the head through Google Tag Manager, capturing the oppref click reference in a first-party cookie.
A server GTM container on your own subdomain, hosted on Stape, sends the same events through the Conversions API.
Browser and server events share one event_id, so each conversion is counted once.
Shopify, Stripe and PayPal orders, plus HubSpot, Salesforce, Zoho, Pipedrive and GoHighLevel won deals.
Pixel consent tied to your banner, hashed customer data and the API key kept on the server, never in the browser.
A free audit of your pixel load order, event names, values, deduplication and consent.
When someone clicks your ad in ChatGPT, the landing URL carries an oppref value. The OpenAI Pixel (oaiq) stores it in a first-party cookie and fires events such as lead_created or order_created from your data layer through Google Tag Manager.
At the same time, your server GTM container on Stape sends the same event through the Conversions API with hashed customer data and the same event_id. OpenAI keeps the first copy and ignores the duplicate, so ad blockers and Safari limits no longer delete your conversions.
OpenAIGoogle Tag ManagerStapeGoogle Analytics 4Looker Studio
BigQueryStripe
PayPalHubSpot
Zoho
GoHighLevel
n8nZapier
Make
Google Ads
MetaIt depends on your checkout, your CRM and your privacy needs. Most brands need the hybrid: browser pixel for speed, server-side for survival, deduplicated. Click a setup to see what is included.
Most brands need both layers: the browser pixel for speed and the Conversions API for survival. I build both and deduplicate them on a shared event_id, so OpenAI keeps one clean copy of every conversion.
OpenAIGoogle Tag ManagerStapeGoogle Analytics 4The fast layer, not the full one. The oaiq snippet must load high in the page, capture the oppref value into a first-party cookie and load before your event tags. I sequence it correctly in Google Tag Manager.
Google Tag ManagerOpenAI
JavaScriptGoogle Analytics 4The pixel only fires when the browser allows it. A server GTM container on your own subdomain, hosted on Stape, keeps sending conversions when ad blockers and Safari limits shut the browser down, with the API key kept on the server.
StapeGoogle Tag ManagerOpenAIMetaitems_added, checkout_started and order_created mapped with the correct currency and amount, then purchases mirrored server-side from your Shopify, Stripe or PayPal checkout, refunds included.
StripePayPalWooCommercelead_created fires on a real submission, not a button click. Bookings send appointment_scheduled, and every lead keeps its oppref value for later matching.
HubSpotGoHighLevelGoogle Tag ManagerOpenAIregistration_completed, trial_started and subscription_created with plan IDs and values, so trial-to-paid revenue, not just sign-ups, guides your bidding.
OpenAIStripeGoogle Analytics 4BigQueryWhen HubSpot, Salesforce, Zoho, Pipedrive or GoHighLevel marks a deal won, I send that event with hashed identifiers through the Conversions API, so real revenue trains bidding.
HubSpotSalesforceZohoPipedriveTracking that breaks silently is worse than none, because you still trust it. n8n, Zapier or Make watch your CRM and checkout, retry failed events and alert you when volume drops.
n8nZapierMake
SlackForms & CRMLeads and won dealsData layerEvents + opprefPixel + CAPIGTM · server · event_idhash → consent → dedupeChatGPT AdsPixel + Conversions APIGA4ChatGPT traffic segmentedLooker StudioChatGPT Ads ROASOpenAI now offers conversion-optimised campaigns in ChatGPT Ads, and they work only for accounts that send conversion events through the OpenAI Pixel or the Conversions API. Without events, you bid on clicks while a competitor bids on purchases. And the browser pixel alone loses conversions to ad blockers, Safari cookie limits, declined consent and script errors. Server-side events survive all of that.
Six building blocks. Most advertisers need the first three, and the rest depend on your CRM, automation and reporting needs.
Server-side events
Events sent from your server with hashed customer data and the same event_id as the pixel, so OpenAI receives conversions the browser misses.
Fast browser layer
The oaiq pixel loaded high in the page through GTM, with consent set first and events fired from your data layer.
Survives ad blockers
A server container on your own subdomain, hosted on Stape, keeps conversions flowing when the browser blocks the pixel.
Tracking that does not break silently
n8n, Zapier or Make watch your CRM and checkout, retry failed events and alert you when volume drops.
CRM revenue to OpenAI
Won deals from HubSpot, Salesforce, Zoho, Pipedrive or GoHighLevel sent with hashed identifiers through the Conversions API.
Reporting you can trust
ChatGPT Ads traffic segmented in GA4, and a Looker Studio view of conversions, revenue and ROAS your team can read.
Click any feature to see how it works and what it changes for your ChatGPT Ads results.
The oaiq snippet loads high in the page, before your event tags, so the oppref value is captured on the landing page every time.
Your actions mapped to OpenAI standard events such as contents_viewed, items_added, checkout_started, order_created, lead_created and subscription_created.
Pixel and Conversions API events share the same Pixel ID and event_id, so OpenAI keeps the first copy and ignores the duplicate.
Order amounts sent as whole numbers with the right currency code, checked against OpenAI’s examples, so revenue in Ads Manager matches your store.
Email and phone normalised and SHA-256 hashed on the server before they are sent, to help OpenAI match conversions.
Pixel consent set from your cookie banner before init, and server events that follow the same choice, for GDPR and US privacy laws.
Qualified leads and closed deals from your CRM sent through the Conversions API with real values.
ChatGPT Ads traffic tagged with UTMs and segmented in GA4, next to organic ChatGPT referrals, with a Looker Studio view.
Automations that retry failed events and alert you when conversion volume drops.
Check your own setup first. These free tools run in your browser, need no sign-up, and are the same checks I use in a tracking audit.
Most advertisers install only the browser pixel. Here is what changes with a full setup.
| What you get | Set up by MD Niamul | Basic pixel only |
|---|---|---|
| What OpenAI can optimise toward | Real orders, leads and trials | Clicks only |
| Conversions lost to ad blockers | Recovered server-side | Lost |
| Duplicate conversions | Removed with event_id | Common |
| Order values | Correct amount and currency | Often wrong or missing |
| oppref click reference | Captured and stored | Often lost |
| Customer data | Normalised and hashed | Missing |
| CRM won deals | Sent with real values | Not sent |
| Consent | Set before the pixel loads | Often ignored |
| Reporting | GA4 and Looker Studio | Ads Manager only |
Five clear steps, from the first audit to a documented handover.
I check your pixel load order, event names, values, deduplication keys and consent.
Which events to send, with values, for your business model.
oaiq pixel through Google Tag Manager, firing from your data layer.
Server GTM on Stape, Conversions API, hashing and deduplication.
Events checked in Ads Manager, documentation and a walkthrough.
Any business that sells something measurable. The event you optimise toward changes by model: a purchase, a qualified lead or a trial start.
Shopify, WooCommerce and custom stores running ChatGPT Ads.
E-commerce server-side →Won deals from HubSpot, Salesforce or Zoho sent back to OpenAI.
Offline conversion tracking →Looking for a dedicated OpenAI Conversions API specialist?
ChatGPT Ads specialist →Use the same server for other platforms:
Server-sideShopifyAttributionGoogle AdsMeta CAPII work remotely in your time zone, with consent and privacy settings matched to your market.
Calls in EST, CST, MST or PST.
All 50 states, from New York and Texas to California and Florida.
Calls in GMT or BST.
Across the UK, including London, Manchester, Birmingham and Glasgow.
Calls in ET, CT, MT or PT.
Across Canada, including Toronto, Vancouver, Calgary and Montreal.
Calls in AEST, ACST or AWST.
Across Australia, including Sydney, Melbourne, Brisbane and Perth.
Hear from our clients. Loved by 600+ businesses worldwide.
“I had an excellent experience working with MD on my Google Ads account. Everything was set up perfectly and worked smoothly without any issues or troubleshooting needed. His expertise and attention to detail made the whole process effortless.”
“I worked with Niamul on multiple Google Analytics projects and was impressed by his expertise and precision. He has a strong grasp of tracking, reporting, and optimization, always ensuring accurate insights. He is proactive, reliable, and easy to collaborate with.”
“MD Niamul is extremely skilled. He fixed my Shopify, Google Analytics, and Google Ads conversion tracking perfectly. Everything works exactly as it should now, and he even added an extra data layer, which was very helpful. Outstanding service, fast delivery, and highly recommended.”
“Reliable, knowledgeable, and truly trustworthy. I’ve been working with Niamul for over a year, and he consistently delivers exceptional results across all analytics tasks. His expertise, communication, and commitment make him my go-to specialist for tracking, measurement, and data accuracy.”
“MD N delivered flawless Meta Pixel, CAPI, and server-side tracking. He understood our goals quickly, explained everything clearly, and ensured full transparency. Communication was smooth, updates were consistent, and the results improved our data accuracy and ad performance.”
Five-star reviews from businesses and agencies in the USA, Canada, UK and Australia.
Read All ReviewsIt sends your leads, sign-ups and purchases back to ChatGPT Ads, using the OpenAI Pixel in the browser and the OpenAI Conversions API from your server. Without it, ChatGPT Ads can report clicks but not revenue.
Most businesses should use both. The pixel is quick to deploy, and the Conversions API keeps sending events when the browser blocks the pixel. Both are deduplicated on a shared event_id.
OpenAI matches events by Pixel ID, event name and event_id. It keeps the first event it receives and ignores later duplicates, so the pixel and server must send the same event_id.
Standard events include page_viewed, contents_viewed, items_added, checkout_started, order_created, lead_created, registration_completed, appointment_scheduled, subscription_created and trial_started. Custom events are also supported.
oppref is the reference value added to the landing page URL when someone clicks a ChatGPT ad. The pixel stores it in a first-party cookie so later conversions can be linked to the click.
Yes. I deploy the pixel through Google Tag Manager, fire events from your data layer, and send server events from a server GTM container, keeping the API key on the server.
Yes. Purchases are tracked on the site and mirrored server-side from your Shopify, WooCommerce, Stripe or PayPal checkout, with the correct amount and currency.
Yes. When HubSpot, Salesforce, Zoho, Pipedrive or GoHighLevel marks a deal won, I send the event with hashed identifiers and the real value through the Conversions API.
It can be when set up correctly. The pixel supports a consent setting, so I connect it to your cookie banner, hash personal data and keep the API key off the browser.
A pixel and Conversions API setup usually takes a few days. CRM or custom checkout connections can take longer. Data then builds up as your ads run.
Yes. One server GTM container on Stape can send events to OpenAI, Meta, Google Ads, TikTok and GA4 at the same time.
Yes. You can use the free server-side tracking checker, tracking audit tool, hashing code generator and 96 free ad calculators, including the tracking loss calculator.
Send me your website and ad account. I will check your pixel load order, event names, values, deduplication and consent, then tell you exactly what is broken and what to fix first. No charge.
