Count one milestone you can prove in HubSpot, a started quote, and send it two ways: the OpenAI pixel on the page and the Conversions API from the server, deduplicated. Connect the ChatGPT Ads account in HubSpot with Auto tracking on, create one lifecycle or form conversion event, and read click-through and view-through separately.
A campaign that cannot see its conversions cannot learn. And a quote that arrives the next day on a laptop is invisible to a pixel alone.
Wire it wrong, and you spend 14 days teaching the system nothing. Wire it right, and OpenAI’s own data says you capture 69% more of the conversions you already earned. This chapter mirrors the Google Ads chapter of our HubSpot guide: one milestone, one route, separate checks. The ChatGPT pieces are new. The discipline is the same.
Which milestone should ChatGPT learn from?
One you can prove from a record in HubSpot.
For most insurers that is a started quote: a form submission naming the person, the line and the state. A bound policy is a better business milestone and a worse optimisation signal, because it arrives days later from the policy admin system, in small numbers. Send the quote as the primary event. Observe the bind.
| Milestone | What proves it | Send it? |
|---|---|---|
| Quote started | A form submission with line and state | Yes, as the conversion the campaign optimises to |
| Quote completed | The rating result returned | Yes if your quote tool can fire it; otherwise observe |
| Policy bound | Policy ID and status from policy admin | Record it in HubSpot and read it; too sparse to bid on in a 14-day test |
| Agent application | A form naming licence, lines and state | Yes, for a recruiting test |
Write the event as a sentence a sales manager could check. Settle the value before you create it. Count it once per person.
The pixel plus the Conversions API
OpenAI gives you three ways to report a conversion: a JavaScript pixel on the page, an image tag, and a Conversions API that posts events from your server. Its first best practice is to run the pixel and the API together.
Its own data: advertisers that added the API saw a median 69% increase in conversions captured and a 22% lower median cost per conversion. Read the footnote. It is observational, taken from accounts that switched between April 29 and August 7, 2026, and it does not prove cause. It is still the best measurement data the platform has published.
The mechanics. The pixel code goes high in the page head. The API needs its own key, separate from the account key, and events posted to OpenAI with a shared event ID so a conversion the pixel already sent is not counted twice. Ten standard events exist. For insurance the useful ones are lead_created, registration_completed and appointment_scheduled. The event stream in Ads Manager shows events arriving. The Event Quality Score (1 to 10) flags missing identifiers, delayed events and duplicates. Check it daily.
Attribution: click windows of 7, 14 or 30 days, view windows of 0 or 1 day, click wins over view. The default is 30 and 1. Leave them.
Connect ChatGPT Ads to HubSpot
HubSpot was the first CRM in OpenAI’s ads partner programme (September 16, 2026), and the connection works on every HubSpot plan. You need the Ads publishing permission, an active ChatGPT Ads account with an API key from the OpenAI Ads dashboard, and an ad blocker switched off in the browser. During the beta only a ChatGPT tenant admin can approve HubSpot’s access.
- In HubSpot, click the settings icon, then Marketing > Ads.
- On the Accounts tab, click Connect account.
- In the Select a network dialog, select ChatGPT Ads.
- Log in to ChatGPT with the email on the ads account and click Allow.
- Tick the ChatGPT Ads accounts to connect. (No account yet? Create ad account is here too.)
- Turn Auto tracking on for each account, so HubSpot appends its tracking parameters to your ad URLs and contacts attribute to the ad that brought them.
- Click Connect.
HubSpot’s article was last updated October 15, 2026. The labels above are its labels. The currency set when a ChatGPT Ads account is created cannot be changed later, and a ChatGPT user can be connected once per ad account.
Create the conversion event in HubSpot
With the account connected, HubSpot can send a HubSpot milestone back to ChatGPT Ads as a conversion. First confirm that each contact whose data you plan to share has given permission for it. HubSpot asks for a consent property in the setup.
- Marketing > Ads, then Create > Conversion event.
- Choose the trigger: Sync lifecycle stage change or Sync form submissions. For a started quote, the form.
- Select your ChatGPT Ad account and Pixel, then Next: Conversion event details.
- Set the HubSpot form (or lifecycle stage), the ChatGPT Ads conversion event it maps to, the Value and the Event Name.
- Next: Match contacts. Set the Consent property, the Contact data to share (the click ID always goes; email, name, phone, IP, city, state, ZIP and country are optional, and more fields match more people) and the Contacts to share.
- Create conversion event. Synced events appear on the Conversion Events tab.
Limits: 5 ad conversion events on Marketing Hub Starter, 50 on Professional, 100 on Enterprise.
And the line that catches people: only updates made after the event is created count. A lifecycle repair run the next day looks like a flood of new quotes to OpenAI. Finish the cleanup first.
What you will see, and how to read it
In Ads Manager: impressions, clicks, spend, click rate, cost per click, conversions and cost per conversion, split into click-through and view-through, by ad, ad group, device and country. In HubSpot: the ChatGPT campaigns beside Google and Meta on the Analyze tab, and contacts and deals attributed to the ad that brought them.
Read click-through and view-through apart. A click-through quote is a person who tapped the card. A view-through quote is a person who saw the card, did not tap, and started a quote within a day; your server event matched their email to the earlier impression. OpenAI says 52% of eligible one-day view-throughs land within an hour. That is the phone-to-laptop hop.
Both are real. Only the first proves the ad was read.
What not to send
Only data you collected with permission for this use. Policyholder data a broker handed you and prospect data from your own quote form are different collection paths. Confirm each before you switch it on. Health information, and anything that implies a medical condition, stays out of the match fields entirely. OpenAI shows no ads in health conversations. Send it no health data.
One more. The Brookings audit found ad delivery skewed toward lower-income ZIP codes. That is OpenAI’s delivery, not your targeting. It is still one more reason to keep ZIP out of your targeting and your match fields for an insurance product, and to let your compliance owner read this chapter before the event goes live.
FAQs
Do I need HubSpot Marketing Hub Professional?
Connecting the account works on every plan. The conversion event needs Marketing Hub Starter at least (5 events), Professional for 50, Enterprise for 100. Our HubSpot for insurance guide covers the rest of the build.
Can I use GTM instead of the pixel?
There is no official GTM template. Put the pixel in the page head directly, and send the server event from wherever your form posts. Our rule: ad conversions live in HubSpot and the ad platform, GTM only for what is left, and nothing fires twice.
Can we do this for you?
Yes. It is the same connection we build for Google Ads, with the ChatGPT pieces added. See HubSpot for insurance and insurtech.
Sources, checked October 26, 2026:
- Connect your ChatGPT Ads account to HubSpot, HubSpot Knowledge Base (updated October 15, 2026)
- Create and sync ad conversion events with ChatGPT, HubSpot Knowledge Base (updated October 15, 2026)
- Set up your ChatGPT Ads for success, OpenAI webinar (pixel plus API data, Event Quality Score, view-through timing)
- OpenAI ads developer documentation (Conversions API, standard events, attribution windows)
- OpenAI ads blog (HubSpot as first CRM partner)
- Brookings, the audit