Documentation
Ads radar and shopping
The sponsored units and product cards the engines render inside the answers we measure, read against the answers checked, never from an ad platform.
The consumer ChatGPT surface and the Google AI surfaces render two things beside the organic answer: sponsored units and product carousels. We read both exactly as the surface declares them, store one row per unit beside the answer, and report counts against the answers we checked.
Ads radar, on Channels
| Number | What it is |
|---|---|
| Answers with an ad | Measured answers that carried at least one sponsored unit, over the answers checked on the three unit exposing surfaces. |
| Who is buying | Advertisers ranked by units, each marked as you, a listed competitor, or another advertiser, from your own roster. |
| The creatives, verbatim | The title, the copy and the landing domain a buyer saw, with how many times we saw it and on which engine. |
| Competitor buys this slot | On the channel plan, a prompt where a listed competitor already rendered a sponsored unit says so in its rationale. The recommendation does not change: earning a citation still beats bidding where it is earnable. |
Exposure is a floor. The capture accounts are not warm consumer accounts and see fewer ads than a typical user, so a low number means we saw few, not that few exist. Nothing here comes from an ad platform, and Ansengine sells no placement.
Shopping, under Visibility
| Number | What it is |
|---|---|
| Answers with a carousel | Carousel answers over answers checked, per engine as well as in total. |
| Product cards | Every card the engines rendered on your prompts, keyed by product title, with merchant, price range, rating and the engines it appeared on. |
| Your share of cards | Your own cards over all cards, with both counts, and the distinct products behind them. A card is yours when its merchant or domain matches your brand, an alias or your domain. |
| Prompts that trigger a carousel | Where shopping intent shows up in your prompt set, and whether your cards are in it. |
Card order changes run to run, so appearances are counts, never a rank. A carousel is one sample of what an engine chose to show on one day, which is why every number here carries its denominator.
Where the data comes from
The same measurement runs that produce your mention and citation rates. No extra spend, no separate scrape: a unit is stored in the same transaction as the answer it appeared in. The raw provider payload behind it is held on a retention window set per deployment and deleted by a nightly sweep once that window passes, so a unit can be checked against the answer it came from while the payload is still there, and not after. We do not print a number for the window here, because it is a deployment setting and we cannot read yours from this page.