Two ways to get ChatGPT Ads data out.
OpenAI's Advertiser API covers campaign management and reporting, with Insights endpoints from account level down to the single ad. The work sits around the calls: a key for every ad account, paging, and spend that can update later than clicks.
Build and run it yourself
- Create an Advertiser API key on the Settings page in Ads Manager. Each key is scoped to one ad account.
- Call
GET /v1/ad_account/insightswithaggregation_level=campaignandtime_granularity=daily. Name the metrics infields: without it, impressions is the only metric returned. - Page with
after.limitdefaults to 20 rows and stops at 2000, and the API allows 600 requests a minute per endpoint. - Read recent days again. Spend reflects finalized activity and can update later than clicks, and conversions take at least a day.
- Keep each account's time zone and currency with the numbers. Days follow the ad account's time zone unless you send another.
- Map each account and campaign to your own markets and product lines, next to the rest of your media data.
Then monitor it, and keep up with the changelog: Insights has gained segments and attribution settings since the first version.
Have Odins run it
- Create an Ads API key in OpenAI Ads Manager, one per ad account, and enter it with the account ID through your Odins onboarding link. The key is never sent by email.
- We sync every day, watch the pipeline and keep up with changes to the API.
- You get spend per campaign per day, in the same structure as every other channel.
- More ad accounts are added when you ask, with one key each.
The same goes for every other source you use. One team runs all of them. See all connectors
What the ChatGPT Ads API offers.
OpenAI calls it the Advertiser API. Reporting runs through the Insights endpoints. OpenAI's own documentation is the reference.
Base URL https://api.ads.openai.com/v1
| Endpoint | What it returns | Good to know |
|---|---|---|
GET /ad_account/insights |
Impressions, clicks, spend, CTR, CPC and CPM, with rows per account, campaign, ad group or ad. | Hourly, daily, monthly or one total. One segment per request. |
GET /campaigns/{campaign_id}/insights |
The same report for one campaign. | Sibling endpoints cover one ad group and one ad. |
POST /conversions/insights |
Conversions per campaign, ad group or ad, split into click-through and view-through. | Returns HTTP 413 past 2,000 summary rows, with no paging. |
GET /ad_account |
Account name, status, time zone and currency. | Shows which account a key belongs to. |
Segments
countrydeviceplatformproduct
- Auth Bearer API key, scoped to one ad account
- Format JSON
- Quota 600 requests a minute per endpoint, 1,200 overall
- History 365 days of daily data
Worth knowing about ChatGPT Ads data.
One key covers one ad account.
Each Ads API key is scoped to a single ad account. A setup with several accounts needs a key for each.
Spend settles after clicks.
Impressions and clicks can show up within minutes. Spend reflects finalized activity and can update later, so recent clicks can arrive before their spend.
Daily history stops at 365 days.
OpenAI serves daily delivery data for the most recent 365 days. Hourly data and product reporting reach back about 30 days.
Spend comes in the account's currency.
OpenAI reports spend in the ad account's currency. Odins keeps the raw data in that currency, so it matches Ads Manager, and applies currency conversion rules after that.
What you get back.
Two layers. The raw one mirrors ChatGPT Ads. The structured one is the table every source lands in, organised by your own markets and product lines.
Structured layer
Per campaign, per day| In the structured table | For ChatGPT Ads |
|---|---|
| Date | Daily |
| Company and market | Set by your routing rules on campaign names |
| Channel and media | Follows your media plan |
| Source campaign | Campaign |
| Spend | Spend, with currency conversion rules applied |
Raw layer
As OpenAI returns itDaily spend per campaign as the Insights API returns it, in the ad account's own currency.
Use it where you work.
In your warehouse
Raw and structured tables delivered to BigQuery, Snowflake, Redshift or Databricks. Some customers use Odins for this alone.
In Odins
Reporting across every channel, and a model that shows what search contributes and where more spend still pays.
Through your AI assistant
Connect Claude, ChatGPT or Copilot to Odins with MCP and ask for the numbers in plain language.
Questions.
Does ChatGPT Ads have an API?
Yes. OpenAI's Advertiser API manages campaigns and serves reporting through its Insights endpoints, at account, campaign, ad group and ad level. You authenticate with an API key created in Ads Manager, scoped to one ad account.
How do I get ChatGPT Ads data into BigQuery?
Create an Ads API key in OpenAI Ads Manager and enter it through your Odins onboarding link. Odins syncs daily and delivers raw and structured tables to BigQuery, Snowflake, Redshift or Databricks.
How far back does ChatGPT Ads data go?
OpenAI's reporting serves daily delivery data for the most recent 365 days. Hourly data and product reporting go back about 30 days.
We run several ChatGPT Ads accounts. Does that work?
Yes. An Ads API key is scoped to one ad account, so each account needs its own key. They all land in the same structure.
How does ChatGPT Ads attribute conversions?
By default the API counts conversions within 30 days of a click and 1 day of an impression, dated to the ad event. The click window can be 7, 14 or 30 days, view-through can be switched off, and conversions can be dated to when they happened.
-1.png?width=1132&height=292&name=Asset%201@2x%20(12)-1.png)