ChatGPT Ads in HubSpot: the Two Admin Gates, and What Actually Lands in the CRM

Published September 19, 2026Updated September 19, 2026By ABD Legacy LLC
Paid media / ChatGPT Ads

OpenAI's post says a business managing its customers in HubSpot can connect a ChatGPT Ads account. HubSpot's own documentation describes something narrower: a beta a Super Admin must opt the account into, and a connection only a ChatGPT tenant admin can approve. For an agency whose client already runs HubSpot, that inverts the order of work — the first deliverables are an admin request and a tenant-ownership question, not a media plan.

This page covers where the buying desk sits, the two permission gates, the only two mechanisms HubSpot documents, and how to brief a client before anyone connects an account.

Where the ChatGPT Ads buying desk sits now

Three doors lead into a ChatGPT Ads account, and they are not three routes to the same thing: OpenAI's own Ads Manager, the HubSpot integration, and the Shopify app — the merchant-side door and the only one shipped through an app store listing.

OpenAI introduced the partnerships on 16 September 2026: “That's why we're integrating ChatGPT Ads into HubSpot and Shopify as our first CRM and ecommerce partners”.

HubSpot's framing of the same integration, on the newsroom page it updated on 16 September 2026, is “Today, we are launching the first CRM integration with ChatGPT Ads for customers to build, manage, and measure campaigns directly in HubSpot.” That sentence is HubSpot describing HubSpot's own product, not a statement about how widely ChatGPT Ads is available, and the ad format remains a select-advertiser test in the United States.

The two admin gates the sources name

HubSpot's Knowledge Base is the only documentation that describes the permission chain, and it names two separate switches.

Gate one is on the HubSpot side. Under a “Please note” alert, the connect document says: “if you're a Super Admin, you can opt your account into the ChatGPT Ads in HubSpot beta”. Nothing below Super Admin opens the beta, so an agency inside a client's portal cannot flip it without Super Admin rights on that portal.

Gate two is on the OpenAI side, and it is not a HubSpot setting at all. The same document: “OpenAI requires the tenant (organization) associated with your ChatGPT Ads account to approve the connection to HubSpot. During the beta period, only a ChatGPT Tenant Admin can approve this access.” If the person connecting the account is not a tenant admin, the document says “you'll be prompted to notify your admin”, and the approval happens at connection time: “The admin can approve access through the OAuth flow during account connection.”

Read together: a Super Admin opts the portal into the beta, a tenant admin approves the OAuth handshake, and then the tenant's ad accounts become selectable in HubSpot. The client's admins hold both switches, so the blocking dependency is organisational rather than technical.

One caveat. Both documents are HubSpot's, on one host, and OpenAI's post does not describe the mechanism at all — so the gates are single-source, and the connect document's date line, “Last updated: September 17, 2026”, sits one day after OpenAI's announcement.

What the HubSpot integration actually does

HubSpot's summary of the integration is: “Connect your ChatGPT Ads account to HubSpot to create ad campaigns, track performance alongside your other ad channels, and attribute contacts and deals to your ChatGPT ad spend.” Its documentation names two mechanisms behind that summary, and they are the only two any source describes.

The first is UTM auto-tracking, from the connect document: “When you turn on auto-tracking, HubSpot automatically appends UTM parameters to your ChatGPT ad URLs so you can see which contacts clicked your ads”. The parameters are appended to the ad URL, so the tracking attaches to the click.

The second is workflow enrolment, from the campaign document rather than the connect document: “Contacts that interact with your ChatGPT Ads can be enrolled in HubSpot workflows, so you can trigger automated follow-up directly from ad engagement.” The trigger is ad engagement; the action is a workflow the client already controls.

The rest of the operating surface is ordinary. Campaigns are created in HubSpot, and the campaign document names exactly one creative type to pick: “Select ChatGPT Chat Card”.

What it does not do: the conversation stays outside the CRM write path

Neither mechanism describes the ad's outcome: one appends tracking parameters to a URL, the other enrols a contact that interacted with an ad. Nothing in HubSpot's documentation, OpenAI's post, or the coverage acquired for this page says the sponsored conversation itself completes a purchase, creates or updates a record, or books a meeting. That is a measured absence: a word-boundaried scan of the eight documents acquired for this research for transaction, checkout, appointment, booking, transcript and contact-creation vocabulary returned no such claim.

The practical reading is that “attribute contacts and deals to your ChatGPT ad spend” is a reporting claim, not a write path. HubSpot is saying it can tie a closed deal back to the campaign that started it, not that the conversation populates the CRM.

HubSpot's marketing copy for the bundle is looser than its documentation — it reads as a benefit statement, names no product and describes no mechanism. Treat the documentation as the specification and the marketing as positioning.

The Shopify app is the merchant-side door

The Shopify listing describes a different job. Where the HubSpot integration is advertiser-side — an ad account connected into a CRM a business already runs — the Shopify app is merchant-side: it moves catalogue data and conversion signals between a store and the ad platform. Its capability text reads “Connect an existing ChatGPT ad account or create a new one directly from Shopify”, “Automatically sync your Shopify product catalog to ChatGPT Ads Manager” and “Run ad campaigns across ChatGPT using a Shopify pixel and conversion events”, and it summarises the loop as “Track performance and manage campaigns without leaving Shopify”.

The listing facts: the developer entity is OpenAI, with a San Francisco address (“Developer OpenAI 1455 3rd Street, San Francisco, CA, 94158, US”), support comes from OpenAI, the listing is free, and its date field reads September 3, 2026 — thirteen days before OpenAI's announcement post.

On availability, OpenAI's post is the primary: “Also available today, US-based Shopify merchants can use the new ChatGPT Ads app”, and “The app will be available internationally in markets where ChatGPT Ads are available starting September 23”.

That split is why this page does not duplicate the Shopify commerce playbooks on this site: those cover making a catalogue legible to agents, while this page covers where an advertiser's buying desk and its permissions live.

The one dated commercial peg: HubSpot's spend match

HubSpot is running a dated offer alongside the integration, and it is HubSpot's own offer rather than an OpenAI commitment.

HubSpot's newsroom puts it as: “A $750 match on ChatGPT Ads spend for new accounts opened by September 30”. The offer page's FAQ gives the mechanics: “Eligible new advertisers in the U.S. may qualify for up to $750 in ChatGPT ad credit when you spend $750. The offer is for new advertisers only. New advertisers who sign up before Sept. 30, 2026 will have 14 days to spend $750. Then you will get a coupon for the value of $750, which must be spent within 90 days.”

That is four gates in HubSpot's own words: United States eligibility, new advertisers only, a signup before 30 September 2026, and “Offer available to new HubSpot customers only.” A long-standing HubSpot client fails that fourth gate, and the 14-day spend window runs from the signup, not the announcement.

Two things to leave open with a client. No ISO currency code appears on either HubSpot page, so the currency of the credit is unstated. And the “Offer terms” link both pages point to resolves to OpenAI's own ad-credit terms page, which returns 403 and has no public archive snapshot — so HubSpot's description of the offer is verifiable, and the binding terms behind it are not.

How to brief a client before anyone connects anything

Three questions decide whether this is an agency project or a client-side administration task.

Then write the availability sentence into whatever you send: this is a beta behind two admin approvals, and the ad format itself remains a select-advertiser test in the United States.

Frequently asked questions

Can you run ChatGPT Ads from HubSpot today?

Yes, inside a beta rather than as a generally available feature. A HubSpot Super Admin has to opt the account into the ChatGPT Ads in HubSpot beta, and a ChatGPT tenant admin has to approve the OAuth connection before the tenant's ad accounts can be connected in HubSpot.

Who has to approve the ChatGPT Ads connection in HubSpot?

Two people, on two systems. A HubSpot Super Admin opts the portal into the beta, and a ChatGPT tenant admin approves the connection through the OAuth flow at connection time. Nothing below Super Admin opens the beta, and an app user who is not a tenant admin can only notify an admin.

Does the HubSpot integration write leads into the CRM?

No source says so. HubSpot documents two mechanisms: UTM parameters appended to the ad URL so you can see which contacts clicked, and enrolment of contacts that engaged with an ad into HubSpot workflows. Attribution and follow-up are documented; the conversation itself creating or updating a record is not.

Is the HubSpot integration a beta or generally available?

It is a beta. Both HubSpot documents carry a BETA badge, and the connect document's own instruction is that a Super Admin opts an account in. Nothing in the sources describes general availability for either the integration or the ad format, which remains a select-advertiser test in the United States.

What does the Shopify app do that the HubSpot integration does not?

The Shopify app moves commerce data: it connects or creates an ad account from the store, syncs the product catalogue into ChatGPT Ads Manager, and runs campaigns on a Shopify pixel and conversion events. The HubSpot integration connects an advertiser's ad account into a CRM. One is merchant-side, the other advertiser-side.

Does HubSpot's spend-match offer apply to my client?

Only if four conditions hold at once: the client is in the United States, is a new advertiser, is a new HubSpot customer, and signs up before 30 September 2026. New HubSpot customers only is stated separately on the same page, so a long-standing HubSpot client fails that gate.

Is the Shopify app available outside the United States?

Not yet. OpenAI says US-based Shopify merchants could use the app from 16 September 2026, and that it will be available internationally in markets where ChatGPT Ads are available starting 23 September.

Related reading

Sources

Accuracy note: every mechanism on this page is quoted from HubSpot's own documentation, which is the only source that describes it; OpenAI's post states the capability but not the permission chain, so the gates are single-source. openai.com and ads.openai.com return 403 to automated fetches from this host and are cited above with their archive timestamps rather than treated as missing. Re-verify the beta flags and the 30 September 2026 deadline before repeating either to a client.