Skip to content
All field notes
Measurement
Published
Nov 12, 2026
Reading time
12 min read

How to Audit Bot-Traffic Claims for ChatGPT Ads

Review ChatGPT Ads click, landing-page and bot signals without treating a vendor label as proof of a billed invalid click. A practical evidence checklist.

AP
AdProof Research
Independent measurement desk
An analyst checks a request log, ad report and bot-signal notes as separate evidence sources on a warm paper workspace.
Keep platform clicks, server arrivals, analytics events and traffic classifications on their own denominators.
In this guide (9 sections)

A high bot score, a datacenter IP, a very short session, or an attribution parameter can each be a reason to investigate. None alone proves that a particular ad click was invalid, billed, or caused a financial loss. Start by reconciling four separate things: what the ad platform reports, what the browser or server received, what your analytics recorded, and what your fraud classifier inferred. Keep the population, time window, and definition attached to every number.

This distinction matters for advertisers testing newer buying surfaces. In an r/adops thread about automated-traffic claims on OpenAI Ads, a vendor disclosed that it sells invalid-traffic detection and refund-audit software, then published its own test results. Its post reports 923 platform clicks, 1,356 server arrivals, and 788 arrivals it classified as automated. Those are different denominators: 788 is 58.1% of 1,356 arrivals, not 58.1% of 923 billed clicks. The post’s headline calls it a share of billed clicks, but the body does not establish that relationship. Treat it as a commercial claim to examine, not an independently audited measurement.

When the same thread was rechecked at about 21:00 IST on November 11, the vendor author had added claims about IP rotation, network attribution, browser behavior and shared TLS fingerprints. Another commenter described a separate ad buy, an extreme automated-traffic estimate and an unresolved refund request; the vendor author also offered comparisons with other platforms. These comments add questions to investigate, but they do not independently validate one another or the original counts. The thread does not publish a reproducible event-level join between platform clicks, server arrivals, classifier outcomes and billing dispositions, nor an independent review of the labels. Treat correlated signals from one request population as evidence about that population, not as multiple independent confirmations. Keep all of the added figures and explanations attributed to their authors.

A separate advertiser thread about short ChatGPT Ads sessions reports clicks, spend, no purchases, and unusually short sessions, then says the discrepancy was still under support review. That post is also a self-reported incident; it does not prove bots or explain the cause. These examples show why the right response is a reproducible audit, not an instant fraud verdict.

Start with the measurement chain#

Write down the distinct events you are comparing. A useful chain is:

  1. Platform click metric: the ad system’s reported clicks for a defined account, campaign, ad, date range, timezone, and filter set.
  2. Landing request: a request that reached your web edge or server, with a timestamp, requested URL, response and available network metadata.
  3. Browser or analytics event: a page view, session, engagement, or conversion recorded by your measurement setup.
  4. Invalid-traffic classification: a rule-based or model-based label applied to an event or session under a documented definition.
  5. Billing disposition: the platform’s charge, adjustment, credit, or written determination for the exact scope being reviewed.

These quantities can differ without proving fraud. A click can occur without a completed page load; a landing request may not execute analytics; redirects, consent choices, blockers, browser lifecycle, delayed processing, or duplicate instrumentation can affect the records. Conversely, one server arrival is not automatically one unique person or one billed click. Do not force the rows into a one-to-one mapping until you know what each system counts.

OpenAI’s Ads Measurement Pixel documentation describes oppref as an attribution reference that the pixel can capture from the landing URL and retain in a first-party cookie. The documentation supports using it to associate a subsequent conversion with an ad interaction; it does not say that the mere presence of that parameter in a server request proves the request was a separately billed click or certifies that the visitor was human. Preserve it as a join key with the platform’s own definition, not as a verdict.

For your campaign

Review the evidence behind a traffic claim

Keep platform clicks, server arrivals and classifier labels on their own denominators. Discuss the measurement scope relevant to your setup.

Discuss traffic measurement

A measurement discussion, with scope confirmed before any next step.

Build a like-for-like comparison before calculating a rate#

Export the platform report and preserve an untouched copy. Record:

  • account, campaign, ad group, and ad identifiers;
  • the exact click column and its definition;
  • date range, account timezone, export time, filters, and segmentation;
  • whether the report is preliminary or mature and when you will re-export it;
  • currency and billing record identifiers, kept in an access-controlled file;
  • the landing URLs and permitted attribution parameters in use.

In parallel, export edge or origin logs for the same interval. Preserve event time and receive time if both exist, the response code, normalized path, redirect chain where available, and a privacy-reviewed representation of the request identifier. Do not retain more personal data than needed. If you hash or truncate IP addresses, document the method and retention window because that changes what later checks remain possible.

Then compare counts only at matching scope. If one platform number is campaign-level for a calendar day in the account timezone and the server count is an hourly UTC extract, convert the intervals before comparing. Separate test traffic, staff visits, uptime checks, security scanners, search crawlers, and landing-page prefetching only when you have a reproducible rule. Do not silently remove inconvenient records.

Hypothetical reconciliation

Suppose an ad report shows 500 clicks for one campaign on a specified local date. Your server logs show 430 landing requests for the campaign’s approved destination, while analytics shows 370 page views. These figures do not imply that 70 clicks were bots and 60 more were blocked. First test whether the export intervals match; check redirect and consent behavior; test whether the analytics tag fires on the final page; and look for requests that reached a different URL or returned an error. Only after reconciling those steps should you classify the remaining unmatched population, and even then “unmatched” is a measurement state, not a fraud label.

Treat bot indicators as evidence with different strengths#

A defensible classifier should state what it observes, what population it labels, and what evidence could reverse that label. A hosting-provider ASN is an infrastructure clue, not a human-versus-bot answer. Legitimate corporate networks, privacy relays, mobile gateways, cloud-hosted browsers, accessibility tooling, automated previews, and platform systems can all complicate network-only rules. A very short session can mean an accidental tap, a fast exit, a page-load failure, a blocked script, a privacy choice, or automation. Low engagement and no conversion are business outcomes; they are not by themselves bot tests.

More fields do not automatically mean more independent evidence. For example, a network address, an ASN lookup, a TLS fingerprint and browser behavior may all describe the same visit and may be correlated by the classifier. Ask whether each signal was measured on the same event, how missing values were handled, which rules contributed to the final label, and whether any evaluation set or review process estimates false positives. Do not add each signal's flagged count together unless the populations are known to be disjoint.

Likewise, behavior signals such as repeated timing patterns, impossible event sequences, or request rates may help identify automation, but their reliability depends on collection coverage and the decision threshold. Ask the vendor or internal analyst for:

  • the exact event-level definition of “bot,” “automated,” “suspicious,” and “invalid”;
  • which requests form the denominator and how deduplication works;
  • the classification window and whether labels are final or provisional;
  • the rule or model version, known exclusions, and false-positive review process;
  • examples from both flagged and unflagged groups, with personal data removed;
  • whether the result identifies a web request, a browser session, an ad click, or a billed interaction.

Do not treat percentages from separately sampled data as directly comparable. A vendor may classify server visits while the ad platform reports clicks. If visit records can repeat, then the denominator may also contain multiple requests for one browser or activity that cannot be joined to a platform row. Show both counts and their separate populations; do not rename one as the other.

Validate attribution parameters without overstating them#

For a permitted test, click through the ad using the normal public experience and follow the redirect chain to the landing page. Capture the final URL, whether the attribution parameter survives, whether the server records the request, and whether the measurement pixel or analytics tag fires. Repeat with documented browser and consent configurations where appropriate. A successful test proves that the tested path worked at that time. It does not establish what happened on every historic click.

For OpenAI Ads specifically, read the official measurement documentation alongside the advertiser’s current reporting export and pixel implementation. A captured oppref may help connect later conversion events to an ad interaction, while the browser or server still needs to record the landing event correctly. Check for redirects that strip query parameters, URL canonicalization, consent-gated scripts, cache behavior, and multiple tags firing the same event. Keep a separate status for “parameter observed,” “landing request observed,” “analytics event observed,” and “conversion attributed.” They answer different questions.

Never paste opaque identifiers, full URLs containing personal data, payment details, or user-level logs into a public forum. Share only the minimum redacted fields needed for a technical support case.

Ask the platform a bounded billing question#

A click-to-session gap is not a billing decision. If the issue might affect charges, ask support to reconcile the platform’s exact click population against the exact account, campaign, ad, dates, timezone, and export. Include an immutable report snapshot, a short redacted request sample, the tracking configuration, and steps to reproduce. Ask whether the requested metric is provisional, whether any invalid-traffic review is open, what adjustment or credit process applies, and when a final answer can be expected.

OpenAI’s Troubleshooting Common Issues recommends including account and campaign identifiers, exact errors, date and time with timezone, and recent changes for relevant support cases; it warns against sending passwords or card details. Its measurement guide describes reporting metrics and their typical update intervals. Use the current official support route and maintain the case number privately. A support request is not confirmation of a credit, an invalid-traffic finding, or a pause in campaign delivery.

For Google Ads, Google documents its own invalid-traffic filtering and invalid-click billing process. That is useful as a platform-specific example of why the vendor’s traffic labels and the platform’s billing disposition are separate. Do not transfer Google’s policies to OpenAI, another publisher, or a different ad system unless that platform’s own current documentation says they apply.

Keep a decision log and avoid premature remedies#

Create a small incident record with one row per claim: the claim, source, observed population, timestamp, confidence, counter-evidence, and next action. Possible statuses include observed, reproduced, classified by vendor, submitted to platform, platform-confirmed, credited, and unresolved. These statuses should not collapse into a single “fraud” field.

Avoid blocklists or network exclusions based only on one ASN, a single short visit, or a headline percentage. A broad block can remove legitimate users and make later measurement less representative. If you test an exclusion, preserve the before/after configuration, limit the test to a defined period and segment, record the eligible traffic population, and check both the intended signal and side effects. A lower flagged share after a block is not proof that the blocked traffic was invalid; the rule itself changed the population.

The Media Rating Council standards index lists its IVT Detection and Filtration Guidelines & Addendum as last updated June 2020 and an interim update memo as last updated April 2024. Those materials can help frame questions about documented methods, controls, and disclosure. They do not certify a particular vendor’s claim, establish that a platform follows a given process, or convert a buyer’s investigation into an accredited result.

Practical checklist#

Before describing traffic as invalid, confirm that you can answer each item:

  • Do the platform clicks and server arrivals cover the same account, campaign, dates, timezone, and destination?
  • Are report maturity, filters, deduplication, redirects, consent and tag coverage recorded?
  • Is the classifier’s numerator and denominator explicit?
  • Are network signals described as clues unless stronger evidence supports the classification?
  • Does the attribution identifier’s official documentation support only the inference you are making?
  • Are platform billing decisions, adjustments and support responses recorded separately from third-party labels?
  • Are examples hypothetical unless they come from a clearly attributed and independently verifiable measurement?
  • Are personal data and opaque identifiers kept out of public reports?

If one answer is missing, state the gap and next evidence needed. This is more useful than presenting a precise but unsupported invalid-traffic percentage.

Where AdProof fits#

For an existing supported campaign, teams can review AdProof’s available campaign and time-window evidence alongside the platform export, server logs, analytics setup, and support record. Confirm the supported source, identifiers, and fields before planning a workflow. AdProof’s anonymized fashion-retail display case study shows a delivery baseline with gross, GIVT-filtered, and final net counts; it is a different campaign and measurement question, not evidence about OpenAI Ads or the vendor claim above. This article does not imply that AdProof currently integrates with OpenAI Ads or independently validates third-party bot labels for that platform.

Frequently asked questions#

Does an attribution parameter prove a click was billed?

No. It may help associate a landing-page or conversion event with an ad interaction under the platform’s documented behavior. Confirm billability using that platform’s click definition, report scope, and support or billing records.

Does a datacenter IP prove a visit is a bot?

No. It is a network signal to investigate. Combine it with a documented classification method, request behavior, repeatability, and checks for legitimate services that may use hosted infrastructure.

If an ad platform reports more clicks than analytics sessions, are the unmatched clicks invalid?

Not by that fact alone. The systems count different events and can have different scopes, timing, filters, consent behavior, and page-load outcomes. Reconcile those mechanics before making a traffic-quality claim.

Can a third-party bot score prove that a platform owes a refund?

No. A classifier may support an investigation, but billing credits depend on the ad platform’s own policy and decision for the defined transactions. Keep a vendor result separate from a platform-confirmed adjustment.

What evidence should I send to support?

Provide the account and campaign identifiers, exact date range and timezone, report export, relevant settings, a reproducible description, and a small redacted sample. Do not send passwords, payment-card details, or unnecessary personal data.

Your next step

Review the evidence behind a traffic claim

Keep platform clicks, server arrivals and classifier labels on their own denominators. Discuss the measurement scope relevant to your setup.

Discuss traffic measurement

A measurement discussion, with scope confirmed before any next step.

Back to all field notes