In Ads Manager Beta, you can measure campaign performance with reporting tools that help you track delivery and monitor results. As the platform evolves, we’ll introduce additional metrics, reporting views, and insights over time.
Metrics
You can currently track the following metrics across all levels (campaign, ad group, and ad):
Impressions: Number of times your ads were shown
Clicks: Number of times users clicked on your ads
Spend: Total amount spent delivering your ads
CTR: Percentage of impressions that resulted in clicks
Avg CPC: Average cost per click
Avg CPM: Average cost per thousand impressions
Conversions: Number of conversion events attributed to your campaigns, if conversion measurement is set up. To get started with conversions, visit our measurement documentation
These metrics are available in table view, chart view, and CSV export downloads and can be used to evaluate delivery, engagement, and pacing across your campaigns.
How conversions appear in reporting
Ads Manager displays a combined Conversions total for the selected reporting scope and date range.
To view individual conversion events:
Open the three-dot menu
Select Edit columns
Expand Conversions & events
Choose the events you want
Select Save changes.
Selected event columns can also appear in CSV exports. Availability may vary by account and reporting period. The Segment menu controls Device and Country breakdowns; it does not add conversion-event columns.
Note: Conversions may not be reflected in Ads Manager immediately. Please allow 24–48 hours for attributed conversions to be included in reporting.
Table view
Table view is the default reporting view for monitoring performance in Ads Manager Beta.
Navigate to the Campaigns, Ad Groups, or Ads page
Review performance metrics directly in the table on each page, including impressions, clicks, spend, CTR, Avg CPC, Avg CPM, and conversions when available
Product reporting
For product-feed campaigns, the Products tab is an insights-backed reporting view, not a complete feed inventory. Products appear after an active campaign delivers and generates reporting data. Use the product count during ad-group setup to confirm feed readiness and eligibility.
CSV download
CSV downloads allow you to export reporting data from Ads Manager Beta for offline analysis.
To export cumulative reporting for the current table, select the three-dot menu, then Export → Export current table view. To export specific rows, select those rows, then choose Export → Export cumulative values. Both options use the same cumulative metrics; the difference is which rows are included.
For daily reporting, choose Export → Export daily values.
Insights charts
Ads Manager Beta includes chart views that allow you to analyze performance trends over time.
Select the chart icon next to the three-dot menu
Click View insights
Select the metric(s) you want to view: impressions, clicks, spend, or any combination of all three
Set the date range you want to analyze
Measurement and reporting FAQ
How are conversions measured?
OpenAI tracks conversions using first-party measurement signals after someone clicks an ad; for details, see Conversion Measurement.
How do I validate that the JavaScript Pixel is installed correctly?
Install the JavaScript Pixel on pages where you want to measure ad activity, confirm it initializes with the correct pixel ID, and use debug mode while testing. See the JavaScript Pixel documentation for installation, event, and troubleshooting guidance.
Can I deploy the Pixel through Google Tag Manager?
Yes, as long as your tag manager loads the Pixel snippet on the correct pages and does not block or reorder the initialization and event calls. If the tag manager prevents the Pixel from loading reliably, install the snippet directly or use server-side measurement where appropriate.
How should I measure Shopify, headless storefront, or server-side purchase events?
Use the browser Pixel for browser-side events and the Conversions API for server-side events. If you pass server-side conversions, preserve and send the available click reference values, such as oppref, so events can be attributed correctly.
Why do Ads clicks differ from Google Analytics sessions or landing-page visits?
Ads clicks measure ad interactions. Analytics sessions depend on page load, redirects, consent settings, browser blocking, UTM handling, attribution windows, and time zone settings. Compare the same date range and time zone, then use CSV exports to check campaign and ad-level activity.
Can I add dynamic URL parameters?
Yes. Dynamic URL parameters are available in Ads Manager Beta. You can add custom landing page query parameters using your own text or supported macros, including {campaign_id}, {ad_group_id}, {ad_id}, and {ad_account_id}. Ads Manager populates supported macros automatically at delivery time.
You can configure query parameters from the three-dot menu on the Campaigns, Ad Groups, or Ads page by selecting Edit campaign, Edit ad group, or Edit ad. In the edit modal, use Landing page query parameters to add the parameters you want appended to landing page URLs.
More specific settings take precedence. The hierarchy is: Ad URL, then Ad, then Ad Group, then Campaign. If a parameter is already set at the Ad URL level, campaign, ad group, or ad-level settings will not overwrite it.
Why do conversions appear as one metric in reporting?
The Conversions column combines attributed conversion events into a single total. To include individual event metrics, add the relevant columns through Edit columns → Conversions & events before exporting. Event-specific CSV headers may appear as attributed_event_account_created or attributed_event_registration_completed.
Why do my conversion events show 0 in Ads Manager?
A conversion event can be firing or accepted and still show 0 in Ads Manager if it does not match the conversion event configured for the campaign.
For standard events, the configured event type must match the event you send. For custom events, Ads Manager must use Event type: Custom and the custom event name must exactly match the event name you send. A matching display name alone is not enough.
Also make sure the correct conversion is attached to the campaign before traffic starts. If you correct the configuration, test again with new eligible traffic. Historical events from the mismatched setup will not backfill.
What is automatic advanced matching, and how do I enable it?
Automatic advanced matching helps match website conversions to your ads using supported customer information entered into website forms. The OpenAI Pixel securely hashes this information in the browser before including it with conversion events. To enable it, go to Tools → Conversions → Data Source in Ads Manager and select Enable for all Web data sources. No changes to your Pixel implementation are required.
For additional information, see Conversion Measurement.
What should I include before contacting support about reporting?
Include the following:
Ad account ID
Campaign & Ad Names
Date range and Time zone
Ads Manager CSV export
Analytics comparison
Pixel ID
Event names
Sample conversion timestamps
Screenshots of the discrepancy.
This helps support isolate implementation issues from reporting or attribution differences.