Can I see which ChatGPT conversations or prompts my ads appeared in?
No. ChatGPT Ads Manager and OpenAI's Insights API don't show the prompts, chats or conversation topics your ads appeared next to, and OpenAI's ad principles, as PPC Land reported, keep conversations private from advertisers. You get totals instead: impressions, clicks, spend, CTR, CPC, CPM and conversions for your account, campaigns, ad groups and ads, split by time and, in enabled accounts, by country, device, platform (ChatGPT app or web) or product. To judge relevance, give each use case its own ad group, tag clicks with UTMs, and check what those visitors do on your site and in your CRM.
Ask Tofu next
Pick a question and Tofu Ads Agent answers it in chat.
- How do I set up UTMs on ChatGPT ads so I can compare ad groups in GA4?
- How should I split my ChatGPT ads context hints into ad groups by use case?
- Can I see ChatGPT ads results by device or by app versus web?
- How do I judge the lead quality of ChatGPT ads in HubSpot or Salesforce?
- Which conversion event should a B2B ChatGPT ads campaign optimize for?
As of November 2026.
What does ChatGPT ads reporting show?
Numbers about delivery, cost and results, never the chat. OpenAI's Reporting guide lists these metrics:
| Metric | What it tells you |
|---|---|
| Impressions, clicks, CTR | How often the ad showed and got clicked |
| Spend, CPC, CPM | What it cost, in your account's currency |
| Conversions, CPA, post-click conversion rate | Goal conversions from clicks and views inside your attribution windows |
| Attributed sales, ROAS | Purchase value from order_created events (mostly for ecommerce) |
You can pull them for the whole account, one campaign, one ad group or one ad, by hour, day, month or the whole period. Hourly delivery data goes back about 30 days. Daily and monthly delivery data goes back 365 days, except product reports, which go back about 30 days.
Accounts that have segments enabled can add one breakdown per report:
- Country.
- Device.
- Platform: Android app, iOS app, Android web, iOS web, desktop web, web or unknown. OpenAI says Windows and macOS app activity currently shows as unknown, and platform rows carry delivery metrics only, not conversions.
- Product, for product-feed campaigns.
The conversion report can also be split by country or device. It can list attributed events that aren't your campaign goal too, for example sign-ups from a campaign that optimizes for leads.
That's the full list. OpenAI's Insights reference offers no breakdown by prompt, conversation, topic or context hint.
Why doesn't OpenAI show advertisers the prompts?
Because its ad rules keep chats away from advertisers. When OpenAI announced ads in January 2026, its principles said, as quoted by PPC Land: "We keep your conversations with ChatGPT private from advertisers, and we never sell your data to advertisers." OpenAI's announcement page couldn't be read to confirm the wording.
OpenAI's help article "Ads in ChatGPT" says more, in the version we saw in search results: advertisers get only aggregated information that doesn't identify anyone, such as total views or clicks, and never receive users' chats, chat history or memories. OpenAI's help center couldn't be read to confirm the current wording.
So there is nothing like a search terms report. Context hints don't fill the gap either. OpenAI says "Hints are not exact-match keywords," and no report says which hint, if any, matched a conversation.
Microsoft has a similar gap for its ads in Copilot: see whether you can see how Copilot placements perform.
Can I at least see which context hints triggered my ad?
No. The smallest unit in reporting is the ad, and hints sit on the ad group. OpenAI's campaign structure guide says to use ad groups "for different bid configurations, context hints, or product selections."
That gives you the closest workaround: one use case per ad group. If each ad group holds hints about one problem your product solves, the ad group report tells you which problem brought clicks and conversions. For how to write and group hints, see how to write context hints for ChatGPT ads.
How can I tell if my ads show up in relevant conversations?
Judge it by what happens after the click. Five checks:
- Compare ad groups. With one use case per ad group, a group that gets clicks but no engaged visits is probably matching the wrong conversations.
- Tag every click. OpenAI's tracking parameters can add UTMs at the account, campaign, ad group or ad level, with
{campaign_id}and{ad_id}filled in for you, for exampleutm_source=openai&utm_campaign={campaign_id}&utm_content={ad_id}. Add a key naming the use case, such asutm_term=compliance-audits, to each ad group's own parameters so your analytics can tell ad groups apart. When the same key is set at more than one level, the ad level wins, then the ad group. - Watch the landing page. Engaged time, scroll depth and form starts show whether visitors arrived with the problem your ad describes.
- Check lead quality in your CRM. Follow ChatGPT leads to meetings and pipeline, not just form fills. See how to track conversions from ChatGPT ads for the setup.
- Ask. A "How did you hear about us?" field on your form catches buyers who found you through ChatGPT. Some will say what they were asking about.
Don't count on an ad preview for this. OpenAI says a preview "shows appearance; it does not confirm serving eligibility."
If you're still deciding whether ChatGPT ads fit a B2B plan at all, start with whether ChatGPT ads are worth testing for B2B lead generation.
Sources
- Reporting - Ads (OpenAI Developers), checked November 8, 2026
- Insights - Ads API reference (OpenAI Developers), checked November 8, 2026
- Targeting - Ads (OpenAI Developers), checked November 8, 2026
- Overview and changelog - Ads (OpenAI Developers), checked November 8, 2026
- Campaign Management - Ads (OpenAI Developers), checked November 8, 2026
- OpenAI finally pulls trigger on ChatGPT ads after monthslong delay (PPC Land, January 16, 2026), checked November 8, 2026
- Ads in ChatGPT (OpenAI Help Center), seen in search results November 8, 2026; the page itself couldn't be read