Non-goal events are attributed conversions that a ChatGPT Ads campaign records but does not optimize toward, such as purchases logged on a campaign whose selected goal is lead submissions. They sit apart from your single optimization goal, the one standard conversion event the auction actually bids against.
Reading non-goal events lets you judge a campaign on the full set of outcomes it produces instead of the one number the bidder chases. Ignore them and you either misjudge a campaign that drives revenue its goal never counts, or you keep changing the optimization event and reset the learning each time.
In ChatGPT Ads reporting, a non-goal event is any attributed conversion type that falls outside the single event your campaign was set to optimize. A conversion campaign runs on optimized cost per click, or oCPC, and the auction bids toward one standard event you nominate at creation. Every other conversion the pixel or Conversions API attributes to that campaign is a non-goal event.
Non-goal events exist because OpenAI separates the signal the bidder uses from the outcomes it is willing to report. Since late September 2026, the Insights API can return attributed events beyond the goal when you add the attributed_events expansion to a conversions insights request. The goal conversion count and summary sales stay fixed; the non-goal detail is layered in without changing the reporting clock or windows.
Non-goal events are distinct from custom events, which are non-standard actions you define and which can never serve as an oCPC goal. They differ from the goal event, the only conversion feeding bidding. AirOps helps teams pull goal and non-goal conversions from the ChatGPT Ads Insights API into one view so a campaign is judged on every outcome it drives.
Resources: see how AirOps brings ChatGPT Ads conversion reporting into one workflow.
Non-goal events surface through the same measurement setup that feeds conversion bidding, then appear only when you ask the reporting layer for them.
Install tracking. Deploy the JavaScript pixel, the Conversions API, or both so every standard event reaches your ad account beyond the one you optimize toward.
Set the goal. At campaign creation you nominate exactly one standard conversion event as the oCPC goal; this choice is locked and cannot change later.
Attribute events. As people click your ad and act, ChatGPT Ads attributes each standard event to the campaign using its click and view windows.
Request the expansion. Add the attributed_events include to a conversions insights API call to return event detail alongside the goal count.
Read non-goal rows. The response lists attributed events that are not the goal, which can show positive counts or sales while the goal conversion column stays at zero.
The expanded report tells you what else a campaign produced beyond its optimization target. It does not change delivery, billing, or which event the auction bids toward.
Whether you keep a ChatGPT Ads campaign running, cut its budget, or rebuild it often comes down to how you read its results, and the goal count alone hides much of what a campaign earns and how it supports the rest of your funnel.
Fuller performance picture: Non-goal events show revenue and sign-ups a campaign drives outside its single goal, so you value the campaign on total contribution before deciding its budget. A lead-optimized campaign can quietly produce purchases that never appear in the goal conversions column.
Protected learning: Because the optimization event is locked at creation, non-goal reporting lets you watch other outcomes without swapping the goal and wiping the bidder's learning, a reset that stalls delivery for competent teams who react to a shallow goal count.
Cross-team alignment: Finance and growth often care about different events; non-goal reporting gives each team the outcome it tracks from one campaign setup.
SEO managers use non-goal events to see whether a conversion campaign also drives organic-style actions like content views they never set as the goal.
Growth marketers use non-goal events to compare total revenue a campaign produces against the single goal the bidder optimized toward.
Demand gen leads use non-goal events to confirm a lead-optimized campaign still generates downstream purchases before reallocating spend.
The optimization goal is the single standard conversion event the oCPC auction bids toward, chosen when you build the campaign and locked for its entire life, which is exactly why non-goal reporting exists to show everything else the campaign drives.
Attribution windows are the click and view timeframes that decide which conversions get credited to a campaign, and they govern non-goal reporting too, because an event only shows as a non-goal result once it falls inside the same window that credits the goal.
The attributed_events expansion is the Insights API parameter that layers non-goal event detail onto a conversions report, letting you read other outcomes without touching the goal counts, the summary sales, or the way the campaign is optimized.
Reveal revenue and sign-ups a campaign drives outside its single optimization goal.
Evaluate ChatGPT Ads campaigns on total attributed outcomes across every standard event.
Protect the bidder's learning by reading extra outcomes without changing the goal.
Report purchases on a lead campaign using the ChatGPT Ads Insights API.
Align finance and growth teams around the outcomes each one tracks.
Spot when a shallow goal event is driving low-value conversions early.
Pull the attributed_events expansion on every conversion campaign, because the goal count alone understates what the campaign earns.
Choose your optimization goal deliberately at creation, since it is locked and non-goal reporting cannot substitute for a well-chosen goal.
Keep both the pixel and the Conversions API live, so every standard event is available to read as a non-goal result.
Match each non-goal event to the team that cares about it, so finance sees purchases and growth sees sign-ups from one setup.
Watch the same attribution window across goal and non-goal events, so you compare outcomes on equal footing.
Review non-goal trends before you change budget, because a campaign can earn well on events its goal never counts.
Avoid the habit of swapping the optimization event every time a non-goal result looks interesting; each change resets the bidder's learning and stalls delivery, and the whole point of non-goal reporting is to study those outcomes without disturbing the campaign.
AirOps: Pulls goal and non-goal conversions from the ChatGPT Ads Insights API into one reporting view so campaigns are judged on every outcome they drive.
ChatGPT Ads Manager: OpenAI's interface and Insights API where you set the optimization goal and request attributed events beyond it.
Google Analytics 4: Cross-checks the conversions attributed in ChatGPT Ads against site-side events for the same actions.
Confirm tracking. Check that your JavaScript pixel or Conversions API is already sending every standard event beyond your goal, so the data exists to report. This takes an afternoon and no budget.
Map events to teams. List which standard events each stakeholder cares about so you know what to look for before you query anything. A short mapping keeps the later query focused.
Pull the expansion. Make a conversions insights API call with the attributed_events include to return non-goal detail beside the goal count. The goal conversion count stays unchanged.
Align the windows. Set the same click and view attribution windows for goal and non-goal events so the comparison is fair. Mismatched windows make a campaign look better or worse than it is.
Build a recurring view. Schedule the non-goal pull into your dashboard so every campaign review shows total outcomes beyond the optimized event.
A non-goal event is any standard conversion a campaign attributes outside its optimization goal.
You read them by adding the attributed_events expansion to a ChatGPT Ads conversions insights request.
The optimization goal is locked at campaign creation, so non-goal reporting is the only way to see a campaign's other outcomes without a rebuild.
Swapping the goal to chase a non-goal result resets the bidder's learning and stalls delivery.
The payoff is judging a campaign on every outcome it drives, so spend follows real contribution instead of a single metric.
The difference is what the auction does with each one. The optimization goal is the single standard conversion event you nominate when you build a conversion campaign, and it is the only event the oCPC bidder uses to decide which clicks to chase. A non-goal event is any other standard conversion the same campaign happens to attribute, a purchase on a lead-optimized campaign for example, that the bidder ignores when choosing delivery. Both are measured through the same pixel and Conversions API setup, and both fall inside the same attribution windows. The split is purely about influence on bidding and about where each appears in reporting: the goal event drives the conversions column, while non-goal events show up only when you request the attributed_events expansion. Treat the goal as the steering signal and non-goal events as the wider scorecard that tells you what the campaign earned elsewhere.
Check non-goal events on the same cadence you review the campaign, and keep them off a separate schedule. For most teams that means a weekly look once a conversion campaign has cleared its early learning, plus a closer read before any budget or bid change. Early on, wait until the goal event has gathered enough attributed conversions to be stable, because non-goal counts built on thin data move around for the same reason goal counts do. There is no fixed interval OpenAI prescribes, so tie the review to decisions: before you reallocate spend, before you judge a campaign underperforming, and before you consider rebuilding around a different goal. Checking too often on small numbers invites overreaction, and checking only at the end of a flight means you miss a campaign quietly earning outcomes its goal never counted. A steady weekly rhythm, tightened around decision points, fits how the data matures.
Non-goal events vary between campaigns because they reflect the full behavior of the audience a campaign reaches, and that behavior is shaped by factors the goal setting never controls. Two campaigns can share the same optimization goal yet differ in creative, landing page, product mix, and the conversations where the ad appears, so the downstream actions people take afterward diverge. A campaign that sends traffic to a page with an easy newsletter sign-up will log different non-goal events than one leading to a long checkout. Attribution windows matter too: the same action can count or not depending on whether it falls inside the click and view timeframes set for that campaign. Audience intent plays a part, since higher-intent conversations tend to produce more downstream value across several event types at once. Because of all this, non-goal patterns are a read on the whole funnel a campaign touches, so treat variation as information about that funnel instead of noise.
Not directly, and the honest answer is that you shape non-goal events only through the same levers that shape all conversions. You cannot tell ChatGPT Ads to produce more of a specific non-goal event, because the auction optimizes toward your single goal and nothing else. What you can influence is the setup around it. Make sure every standard event you care about is actually firing through the pixel or Conversions API, or it will never show as a non-goal result no matter how often it happens. Point your creative and landing experience at an audience whose downstream behavior includes the outcomes you want to see. Set attribution windows that genuinely capture how long your buying cycle runs. If a non-goal event matters enough to optimize for, the real move is to launch a separate campaign with that event as its goal, since you cannot change the goal on an existing one.
There is no universal benchmark for non-goal events, so the honest answer is that good means the pattern matches what you expect from the funnel. Because OpenAI publishes no standard rate for them and they depend entirely on your audience, creative, and events, a raw count tells you little on its own. Judge them instead against two internal references. First, your own campaigns: compare non-goal outcomes on a new campaign to past campaigns with similar goals and offers, and treat a large gap as something to explain. Second, your funnel logic: a lead-optimized campaign that also shows a healthy number of downstream purchases is behaving the way you would hope, while one showing leads and almost no later value signals a quality problem. The useful question is directional instead of absolute: are the non-goal events consistent with intent, and are they trending the right way as the campaign matures?