Measure search, AI visibility and pipeline without mixing them up
A useful dashboard distinguishes discovery from demand and demand from revenue. The measures can be related, but adding them into a single “AI growth” score conceals the decisions the team needs to make.
The useful starting points
- Use first-party platform reports where available.
- Keep AI visibility separate from traffic and revenue.
- Report denominators, sample sizes and attribution limitations.
Define the outcome before the metric
Start with the commercial question. If the team needs more qualified evaluation conversations, track the number and fit of those conversations. Search impressions help explain discovery, but they do not establish whether a prospective customer understood or trusted the offer.
Write definitions for enquiry, qualified enquiry, meeting held, accepted opportunity and closed business. Include the time period and deduplication rules. This prevents different teams from presenting incompatible totals as if they measured the same outcome.
Use current platform reporting
As of September 2026, Google provides a dedicated generative AI performance view in Search Console, with impressions and page, country, device and date dimensions. Google announced worldwide availability on August 31. This complements the overall Search performance view.
Bing’s AI Performance reporting includes citation activity and newer preview views for intents, topics, citation share and period comparison. Bing describes citation share as an observational measure, not traffic share, a ranking or a quality score.
- Record the report, date range and filters used.
- Do not add overlapping overall and AI report totals together.
- Inspect individual landing pages and relevant markets.
- Keep third-party estimates visibly separate from first-party data.
Treat prompt tracking as a sample
A prompt monitor observes selected questions under selected conditions. Define the buyer, market, platform and question set before collecting results. Use repeated observations and keep the denominator rather than reporting “we appeared” from a single run.
Record whether the page was cited, the company was mentioned or the company was actually recommended. These are different outcomes. Preserve examples to understand context, but do not treat one answer as a durable ranking position.
Connect visits to the CRM carefully
Track referral traffic and on-site conversions, then map accepted leads to CRM opportunities where identifiers and consent allow. Use source-page context and self-reported discovery as complementary evidence. A buyer can discover the company in one place and return through another.
Define sourced and influenced pipeline before reporting them. Deduplicate opportunity value across channels. Show actual closed revenue separately and explain whether the amount is booked value, annualized contract value or recognized revenue.
Use a small weekly and monthly scorecard
Weekly operations can focus on accessibility, form delivery, qualified enquiries, response time and campaign issues. Monthly reviews can examine nonbrand search relevance, AI visibility trends, accepted opportunities and content performance.
Use trend comparisons with equivalent periods and explain small samples. Where data is missing, state what cannot yet be concluded. The final output should be a decision: repair access, improve the offer, refine content, adjust targeting or change follow-up.
Illustrative scorecard: 20 observed prompts × 3 repeats per platform, 12 qualified enquiries, 7 held meetings and 3 accepted opportunities. These are separate sample measures, not a causal claim or a Qognition performance result.