Conversion time is the ChatGPT Ads reporting basis that files each attributed conversion on the date the conversion actually happened. The default Conversions column files that same conversion on the date of the ad click or impression that earned credit, so both count identical conversions on different days. If you compare ChatGPT Ads spend to revenue by date, conversion time decides whether this week's sales reflect clicks that are still converting or the day those clicks happened. Read the wrong column and a recent week looks dead while delayed conversions file back to older click dates, pushing you to cut a campaign that is working.
Conversion time tells reporting to organize your ChatGPT Ads conversions by when each purchase, lead, or sign-up occurred, giving you a timeline of outcomes keyed to the moment of conversion. Every conversion ChatGPT Ads attributes carries two timestamps: the ad event time, meaning the click or impression that earned credit, and the conversion time, meaning when the person completed the action you measure. Standard reporting uses the ad event time by default, and the "Conversions by conv. time" column re-files the same attributed events on their conversion date. The underlying attribution does not shift: the click still wins over a view, the configured click window still applies, and last-touch logic still decides which campaign gets credit.
Conversion time sits beside the attribution window and the ad event time view in ChatGPT Ads reporting. The attribution window decides whether a conversion counts at all; conversion time decides which calendar day it lands on once counted. AirOps tracks how your pages earn visibility and conversions across AI surfaces like ChatGPT, so you can tie reporting shifts to the content driving them.
Resources: See how AirOps brings AI ad measurement and content performance into one view
Conversion time reshuffles data you already have, changing the date each attributed conversion is reported under through these steps.
Attribute the conversion. ChatGPT Ads matches a fired event to an eligible click or impression inside the configured window, using the oppref click id or server-side data.
Stamp two times. The platform records the ad event time, when the click or impression happened, and the conversion time, when the action completed.
Pick the basis. The default Conversions column files the event on its ad event time; adding "Conversions by conv. time" files it on the conversion date.
Backfill recent days. As delayed conversions settle over the next 24 to 48 hours, ChatGPT Ads attaches them to the correct conversion date, so recent days keep filling in.
Hold bidding steady. Switching the column changes reporting only; optimization, bidding, and billing keep running on click-attributed events.
The conversion time view tells you which days your audience actually converted, which makes it easier to reconcile ChatGPT Ads against your own order records. It does not tell you which ad days drove those conversions, so keep the standard column beside it when you judge performance.
The column you read shapes the budget decision you make. Picking conversion time or the default view changes whether a recent week looks profitable, which feeds directly into what you pause, scale, or defend in the next planning cycle.
Cleaner reconciliation with your books: Conversion time files sales on the day they happened, which lines up with your order dates and makes the ChatGPT Ads number easier to defend to finance.
A failure mode it prevents: Read only the default Conversions column early in a campaign and recent days look weak, because conversions from this week's clicks have not landed yet, and a team can kill a working campaign on that false signal.
Honest trend reading: Conversion time shows demand on the actual day it occurred, so week-over-week trends reflect customer behavior and seasonality, separate from the lag between click and purchase.
Growth marketers use conversion time to reconcile ChatGPT Ads conversions against daily order reports before signing off on spend.
Demand gen leads use conversion time to judge whether a recent week's pipeline is genuinely soft or just waiting on conversions that have not filed yet.
SEO managers use conversion time to compare when AI-driven purchases actually land against the days their landing pages earned clicks.
The ad event time is the date of the click or impression that earned credit for a conversion, and it is the basis the default Conversions column uses when it files each result on your report.
The attribution window is the span after an ad interaction during which a conversion can be credited, set per campaign in ChatGPT Ads at 7, 14, or 30 days for clicks and 0 or 1 day for views, and it decides whether a conversion counts before conversion time decides which day it lands on.
Conversion lag is the gap between the ad event time and the conversion time, and the longer that gap runs the more the two reporting bases diverge for any recent date range.
Align ChatGPT Ads conversion counts with the dates in your own sales records.
Spot delayed conversions that the default date view hides in recent weeks.
Read week-over-week demand by the day customers actually converted.
Reconcile reporting without touching bidding, which keeps optimization stable.
Compare performance across a 7, 14, or 30-day click window on a consistent conversion date basis.
Keep both columns visible, since the default view shows ad-day performance and conversion time shows customer-day demand.
Segment by a single conversion event before reading either column, so you compare purchases to purchases and never an account-wide total.
Match your date range to the attribution window, because a 30-day click window needs at least 30 days of settled data to read cleanly.
Wait 24 to 48 hours before judging a recent day, since conversions in ChatGPT Ads keep settling over that period.
Reconcile conversion time against your order export weekly, so discrepancies surface while you can still explain them.
Check the account time zone before comparing a late-night order to the Ads Manager day.
Avoid treating the conversion time column as a fix for numbers that are wrong at the source. If your pixel is misfiring or deduplication is off, both columns will report the same bad data on different dates, and switching views only hides where the real problem lives.
AirOps: Connects your AI search visibility and content performance to downstream conversions, so you can see which pages feed ChatGPT Ads results across answer engines.
ChatGPT Ads Manager: Adds the "Conversions by conv. time" column through Edit columns and sets the click and view attribution windows per campaign.
Google Analytics 4: Records on-site conversions with their own timestamps, giving you an independent conversion-date view to reconcile against ChatGPT Ads.
Open your column editor. In ChatGPT Ads Manager, go to Edit columns on the Campaigns page and add "Conversions by conv. time" next to the standard Conversions column. You can do this today at no cost.
Confirm your attribution window. Check whether the campaign uses a 7, 14, or 30-day click window and a 0 or 1-day view window, so you know how far back conversions can file.
Segment by conversion event. Filter to a single event like purchase or lead, so both columns compare the same action.
Pull your own order export. Export sales from your store or CRM with order dates, giving you a source of truth to compare against the conversion time column.
Reconcile and set a cadence. Line up the two reports by date, note the gap, and schedule a weekly check so reporting stays trustworthy as campaigns scale.
Conversion time is the ChatGPT Ads reporting basis that files each attributed conversion on the date it actually occurred.
You turn it on by adding the "Conversions by conv. time" column in the Ads Manager column editor.
It changes reporting dates only and never alters bidding, billing, or optimization.
The main risk is reading a recent period too early, when delayed conversions have not yet filed to their true dates.
The leverage is reconciling AI ad results against your own order records, giving finance a conversion count it can trust.
Conversion time and the default Conversions column count the exact same attributed conversions; the single difference is the calendar day each one is filed under. The default column reports a conversion on the ad event time, meaning the day of the click or impression that earned credit. Conversion time reports it on the day the customer completed the action. Because of that, the two columns rarely match for a recent date range, and they converge only once every click in the window has had time to convert. For a marketer, the practical read is simple: use the default column when you want to judge which ad days drove results, and use conversion time when you want to match sales to the days they happened. Neither column changes how the campaign bids or how much you are billed, so you can keep both on screen and switch your attention between them depending on the question you are answering.
Allow at least 24 to 48 hours before you trust conversion time for any recent day, because ChatGPT Ads needs that long for attributed conversions to settle and appear. For a brand-new campaign, the honest answer is to wait longer than a single reporting cycle. If your click attribution window is 30 days, conversions can keep filing back to a given day for up to a month, so a week-old period is still incomplete. A workable rule is to treat the last few days as provisional and only judge a period once its full attribution window has elapsed. In the meantime, watch clicks and spend, which refresh far faster, to confirm the campaign is delivering. Reading conversion totals too early is the most common way teams misjudge a launch, because the recent days look empty while the conversions are simply still in flight. Patience here protects you from cutting a campaign that is on track.
Conversion time shows different totals because it moves delayed conversions onto the day they happened, while your click-date reporting leaves them on the day of the ad interaction. When someone clicks today and buys next week, the default view credits today and conversion time credits next week, so any window that includes recent activity will show a gap. Several other factors widen the difference: time-zone and timestamp boundaries, deduplication of repeated events, consent and browser conditions, and modeled measurement all shift where a conversion lands. The gap is largest for recent ranges and shrinks as older periods fully settle. This is expected behavior, so a difference between the two columns is no proof that tracking is broken. The fix for genuine mismatches is to check the source: confirm the pixel fires once, the account time zone is right, and you are segmenting by the same conversion event in both views.
No. Switching to the conversion time column changes only how reporting is displayed, and it has no effect on how your campaign bids or how OpenAI optimizes delivery. ChatGPT Ads runs its optimization and conversion bidding on click-attributed events, and that logic stays fixed regardless of which columns you add or remove in the reporting view. If you want to influence bidding, the levers are elsewhere: the conversion event you attach as the optimization goal, the quality and completeness of the events you send through the pixel or Conversions API, and your budget and targeting settings. The column choice is purely a lens for reading results. This separation is deliberate, because it lets you reorganize how you view conversions for reconciliation without any risk of disturbing a campaign that is already learning. Treat conversion time as an analysis tool and make bidding changes through the campaign settings that actually feed the optimizer.
There is no single benchmark gap, because the healthy distance between conversion time and ad event time depends entirely on your sales cycle. A low-consideration ecommerce purchase often converts within a day of the click, so the two bases stay close and the gap is small. A considered B2B lead can take weeks, so a wide gap is normal and expected. The useful practice is to establish your own baseline: measure the typical lag over a settled period, then watch for changes against that baseline. A gap that suddenly widens can signal a tracking delay, a pricing or seasonality shift, or a change in the audience you are reaching. A gap that collapses can mean faster-converting demand or a measurement problem. Instead of chasing an industry number, treat your own stabilized lag as the yardstick and investigate movement away from it.