Name the Google report the connection must supply
Google's Generative AI performance report (Search) covers AI Overviews and AI Mode, excludes Search Labs experiments, and defines impressions as links to your site shown to users. Google says these insights rolled out worldwide on August 31, 2026. If the report is missing, Google says insufficient impressions are the usual reason; site exclusion can also matter. Google's report documentation
If that is the evidence your purchase depends on, put the report's full name in the requirement. A missing native report should stay unresolved rather than become a claim that nobody encountered the business in any AI system.
Keep three kinds of evidence separate when evaluating a dashboard:
Scroll horizontally to read all columns. Use the focused table region with the arrow keys.
| Evidence being reported | What the record can support | What to inspect before paying |
|---|---|---|
| Google's generative AI report | Google recorded links to your site being shown in supported AI search features. | The named source report and selected reporting scope. |
| General Search Console data imported into a tool | The connected property's reported Google Search performance. | The source report, property, dates, filters and imported fields. |
| Answers collected by running monitored prompts | What those saved answers said and linked to under the recorded conditions. | Exact questions, collection method, answers, links and failure records. |
This is a comparison of evidence types, not a screenshot or a ranking of products. Source definitions: Google, Peec's Search Console integration and Peec's collected chats.
Peec's documentation separates imported search data from collected answers
Peec provides a concrete example of why the distinction matters. Its Search Console integration documentation describes Google clicks, impressions, click-through rate and average position alongside AI search data. It explicitly says the retrieval and citation figures come from tracked prompts rather than Search Console. Peec's integration documentation
Peec also says these imported data do not distinguish regular search results, AI Overviews and AI Mode. If your purchase requires the dedicated generative report, ask for that specific import to be demonstrated. Its presence remains unverified here, not proven absent. Peec's explanation of the imported numbers
In a demo, choose one displayed metric and follow it back to its origin. If the presenter opens general Search performance to explain an “AI impressions” tile, resolve the mismatch before accepting the label. If it opens a set of generated answers, the measure belongs to that collected sample. The screen's location inside an AI product does not change the event being counted.
Match the connected property to the website you intend to measure
Google's Domain properties include subdomains and multiple protocols. URL-prefix properties include only matching URLs, including the specified protocol and any path. Those are different reporting populations. Google's property definitions
Consider an illustrative company evaluating a tool for docs.example.com. A connected Domain property for example.com can include the company's store, support site and other subdomains. Its search totals would not automatically describe the documentation site alone. Record the chosen property and any filter before comparing it with a prompt project focused on the docs.
Peec's integration page explicitly warns that a Domain property's numbers cover the whole domain even when the tracked project focuses on one subdomain. It also says the connection requests read-only access, managed by Project Owners or Company Owners. Read-only describes permitted operations; it does not narrow the selected property's coverage. Peec's property and access details
Ask your administrator to verify the requested access and the intended dataset before connecting an account. The demo can use a vendor-owned, non-sensitive example; it does not require exposing a client's property to establish what the product supports.
Leave the demo with a completed acceptance record
Copy this record into the purchasing notes and complete it for one displayed metric. A second analyst should be able to repeat the comparison without the original presenter. The fields are an editorial acceptance template, not a provider schema or a claim that every product exposes them.
Scroll horizontally to read all columns. Use the focused table region with the arrow keys.
| Record field | Evidence to retain |
|---|---|
| Dashboard label and source | The displayed metric, named source report or answer collection, and source field. |
| Website coverage | Selected property type and identifier, plus page or subdomain filters. |
| Reporting window | Dates and time zone, source update time and import time. |
| Counting rule | Property or page aggregation; any deduplication, filtering or calculation the connector adds. |
| Missing-data behavior | What unavailable, stale and failed imports look like in the interface and export. |
| Reconciliation result | Source value, imported value, explained difference and the saved evidence. |
| Commercial and access scope | Applicable plan, required role, granted permissions, history, export access and revocation procedure. |
Two checks deserve a visible result. Google warns that unavailable values displayed as ~ or - become zeros in downloads. Ask how an import preserves their meaning; an exported zero alone cannot resolve it. Google's export documentation
Google also counts a property's repeated appearances differently from distinct page appearances. A page-total comparison and a property-total comparison can therefore differ. Ask for the connector's counting rule rather than demanding that unrelated totals match. Google's counting rules
Record the outcome as demonstrated, an accepted limitation, or unresolved. If the tool cannot provide the source you require, a broader score does not settle the purchase question. If consolidation saves useful work, assess that benefit separately from any claim that it supplies new observations.
Price the reporting work and answer evidence separately
A connector may justify its cost by saving your team manual reporting work. Evaluate that benefit through the demonstrated workflow and applicable offer. It does not need to create new observations to be useful.
Answer monitoring is a separate benefit to evaluate. Peec documents responses generated by running prompts across platforms, with answer text and associated records. Its visibility score measures the share of responses mentioning a brand. Such a sample can help investigate what an assistant says; it does not count the audience that encountered those answers. Collected chats · Visibility definition
Keep citations, mentions and recommendations distinct when reviewing that evidence. A source link and a named product establish different observations; deciding whether the answer recommends a product requires reading its advice. For the collection specification, use our guide to AI measurement methods.
Gist's public platform page describes brand and source-link tracking across named AI services. It does not establish an import of Google's generative AI report or the full commercial terms of such a connection. Require the same source demonstration and written scope from Gist as from any competitor. Gist's platform overview
Before committing, write one sentence describing what the purchase must add to the evidence you already have. Then make the demo prove that sentence with a traceable record.