The reading library.

Close or continue the action with that explicit finding. A correct source-page change can be useful even when the available AI observations do not establish a change in visibility.

Read the source guide: AI Citation Tracking: What to Measure Before You Change Content →

A copilot connected to your CRM, project management tool, or database that generates weekly summaries, status updates, and performance snapshots without anyone manually pulling data.

Read the source guide: AI Copilots for Internal Teams: What to Build First →

Measure AI mentions, source citations and recommendations with a reproducible baseline. Follow the evidence into site visits and qualified inquiries, then use a decision report to choose the next improvement. Start with a reproducible citation method, define the baseline and select prompts before interpreting platform-specific observations. Define the 12 measures, build a dashboard that exposes missing data, compare like-for-like cohorts and prioritize the 16 signals that justify action. Turn observations into a weekly review, explain their limits to stakeholders and adapt evidence checks for sensitive contexts. Document referral and CRM evidence, improve the path to a qualified inquiry and write a case study that separates observations from causal claims.

Read the source guide: AI Search, GEO and Automation: The Complete Topic Map →

A referral or CRM source field does not provide the original prompt. Record a buyer's voluntarily shared explanation as self-reported evidence, with its source and date.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

It is a useful source signal documented by OpenAI, but a URL parameter is not a cryptographic proof and can be copied or manually added. Review it with the available referral context and your collection method.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Use a documented, permitted identifier created in your own workflow. For example, a successful inquiry can receive an internal request ID that is also stored on the CRM record. Keep the source evidence attached to that request rather than overwriting the contact's entire acquisition history every time a form is submitted. Track the method and confidence of every join. An exact request-ID match is different from a salesperson's recollection. Multiple contacts may belong to one opportunity, and one contact may submit multiple requests. Choose whether the commercial report counts requests, accounts or opportunities, and deduplicate at that level. Keep identity details in authorized systems; public dashboards should contain only the aggregates required for the decision.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Minimum useful fields: Observation ID, prompt, surface, time, response, cited URLs. What it establishes: A result in a defined test.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Minimum useful fields: Internal inquiry ID, created time, evidence category, qualification. What it establishes: A distinct request and its source evidence.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Minimum useful fields: CRM ID, linked inquiry IDs, stage dates, amount convention. What it establishes: Commercial progression under the CRM definitions.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Preserve the available source values before applying your reporting categories. OpenAI says its ChatGPT search referral URLs include utm_source=chatgpt.com. Inspect a real, permitted test click through your own redirects and forms. Confirm the actual values recorded instead of assuming every arrival will use a particular medium. OpenAI publisher documentation explains this signal. Maintain a versioned mapping from known source domains or campaign values to an AI-referral category. Keep the original value for auditability. Do not replace an unknown source with AI because traffic arrived after a visibility campaign. Do not place personal information or a private prompt in UTM parameters. For records needed to join analytics and CRM, use an appropriate internal identifier under your consent and data-handling rules.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

No. Keep it unknown or in the category supported by the collected data. Missing visibility into a journey is a reporting limitation, not evidence of an AI touchpoint.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Fictional example: analytics records 12 successful inquiry events for a source cohort. The CRM contains 10 distinct inquiry IDs after two repeat submissions are deduplicated. Eight match the recorded source evidence, one has only a self-reported AI discovery answer, and one has unknown acquisition. Report eight observed-source inquiries, one self-reported inquiry and one unknown. Do not report 12 unique AI leads. If three of the eight observed-source inquiries become opportunities, report that progression with the cohort dates. Any opportunity value is pipeline under the CRM's amount convention, not collected revenue. A later direct visit or another marketing touch may also matter. The cohort shows an association supported by recorded evidence; incrementality needs a separate evaluation design.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Build around evidence records before choosing software. An answer observation describes what appeared in a particular test. An acquisition record describes a recorded visit. An inquiry record describes a submitted request. An opportunity record describes the commercial process. Each needs an identifier, timestamp and evidence type. A spreadsheet may be enough to reconcile a small cohort. A warehouse becomes useful when volume and joins require it. Neither architecture creates evidence that was never collected. Begin with the citation tracking foundation, then decide which joins can be supported in your existing analytics and CRM. Download the blank attribution ledger to document the records you can support. It is a reusable worksheet, not an automatic analytics or CRM integration. Populate it with appropriate internal references and aggregated evidence, without personal information.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Use session-scoped acquisition dimensions to review recorded visits. First-user dimensions answer a different question about initial acquisition, while event-scoped attribution can allocate credit for key events. Google documents these distinctions in traffic-source scopes. State the scope in the report title so readers do not mistake one result for another. Choose a meaningful, successfully completed action to measure. A click on a submit button can occur without a valid inquiry reaching the CRM. Google describes key events as events important to the business; defining one still does not make it a sales-qualified lead. Reconcile the event against the actual inquiry before using it as a commercial outcome.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

Test a complete path through landing page, consent state, successful form submission and CRM creation. Check redirects, cross-domain steps and embedded forms where they exist. Compare distinct inquiry IDs with counted events, investigate missing joins, and keep test submissions out of outcomes. Recheck after site or form changes. Publish a coverage note: which sources are identifiable, how many inquiries could be joined, and what remains unknown. Use the lead-journey guide to interpret conversion stages and the CFO reporting memo to turn the evidence into a decision. The measurement hub connects these workflows.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

They can use different scopes and attribution rules. Session acquisition, first-user acquisition and event-level credit answer different questions. Document the dimension and model before comparing totals.

Read the source guide: AI Visibility Attribution: Connect Referrals, GA4 and Your CRM →

No. Open pipeline is not realized profit, and an influence label does not prove incrementality. Report pipeline separately with the amount convention, evidence category and stage date.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

A monthly decision memo is a practical starting cadence, with commercial follow-up matched to the sales cycle. Escalate material measurement failures or budget issues when they occur rather than waiting for the next memo.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Evidence to show: Distinct inquiries, acceptance and stage dates. Decision it can inform: Whether observed demand fits the business.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Evidence to show: Period costs, missing joins and open outcomes. Decision it can inform: Whether further learning is worth funding.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Evidence to show: Source cohort, landing pages and meaningful actions. Decision it can inform: Whether destinations support the next step.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

If finance asks how much revenue AI generated, answer with the strongest available evidence and state what it cannot establish. If there is no mature commercial evidence, say that directly and explain the decision the earlier indicators can still support. If the panel changes, show the old and new series separately instead of presenting a discontinuity as improvement. Assign a measurement owner and a sales owner to resolve discrepancies before the next memo. Use the case-study framework when a stronger evidence packet is available, and the ChatGPT measurement boundaries to explain why monitoring is a sample. The measurement hub provides the complete reading path.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

It can support further investigation, but the decision should also consider the questions covered, evidence quality, costs and commercial relevance. The score's construction and denominator must be clear.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Use the same six fields each month. The blank monthly decision memo provides a reusable starting point. It contains no results and does not connect automatically to analytics or a CRM; the owner must fill it with verified records. Keep the evidence appendix available for anyone who wants to inspect the observations or reconciliation. Example decision rule, to agree before the test: fund another period if the measurement is reliable and a specific unresolved buyer question has a plausible remedy. Expand only when qualification quality and economics meet the organization's own threshold across a suitable observation period. Pause if the work repeatedly misses its defined audience or the measurement cannot support the intended decision. These are suggested rules, not universal benchmarks.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Pipeline is a set of open commercial possibilities under your CRM's value convention. Won bookings, recognized revenue and collected cash are also distinct. Use the financial measure your organization actually manages, label it, and avoid adding incompatible measures together. Attribution assigns credit under a rule; it does not by itself establish what would have happened without the work. Google explains that traffic-source scopes and attribution models answer different questions. For an incremental ROI claim, you need a defensible incremental profit estimate and the related costs. Until then, report observed-source outcomes and their limits.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Report the cost, zero qualified outcomes, work completed, observable leading indicators and remaining uncertainty. Recommend a bounded next step only if the evidence supports a useful learning objective.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Lead with a bounded decision: continue the current test for another period, move effort to a specific issue, increase a budget with stated conditions, or pause. State the requested amount, what it buys and the next review date. Then explain which evidence supports that recommendation. A useful opening is: We recommend one further month at the existing budget to test whether clearer integration pages improve qualified inquiries from recorded AI referrals. Citation coverage improved in our panel, but commercial evidence remains limited. This is a decision template, not a statement about Arrow AI results. It gives finance something concrete to assess without turning an early signal into a revenue promise.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Use separate rows for delivery, visibility, traffic and commercial outcomes. Delivery proves work was done. Visibility describes a defined observation panel. Traffic describes recorded visits. Qualified inquiries and opportunities require CRM evidence. No row should silently substitute for another. Put the current count, comparison count, denominator and evidence source beside each claim. Link the panel definition from the AI citation tracking guide and document the source-to-CRM join with the attribution model. Keep an explicit unknown category where journey evidence is missing.

Read the source guide: AI Visibility Reporting for a CFO: A Monthly Decision Memo →

Construct a small question set around actual client selection criteria: business type, service need, jurisdiction and desired deliverable. Record the engine, interface, language, market, date, complete answer and cited URLs. Inspect whether answers correctly associate the firm with its professionals and scope. An answer that invents a qualification or serves an unsupported jurisdiction should enter the correction queue. Record qualified inquiries using only the information required for initial assessment. Compare the mix of suitable and unsuitable requests, noting whether prospects mention AI discovery. A movement in inquiries after a source update is an observation, not proof that the page alone caused it. The finance overview provides the commercial context, and citation tracking explains how to separate mentions, citations and recommendation observations. Begin with the free audit when the gaps are not yet documented.

Read the source guide: AI Visibility for Accounting Firms: Verifiable Credentials and Engagement Fit →

Run each cohort with recorded language, location settings, session setup and date. Keep API observations separate from public-interface observations. If location cannot be controlled, label it unknown or describe the collection context rather than assigning a country based only on the prompt language. Classify the response language, recommended companies, linked sources and product accuracy. Distinguish a correct recommendation linking to an English page from a missing local recommendation. The first may indicate a journey problem even when the company is present. Use the same measurement definitions across markets. Report counts and missing observations. Our citation tracking method explains the distinction between a mention, a citation and a recommendation.

Read the source guide: AI Visibility for Multilingual B2B Markets →

Observe which resources answer real sales questions and which journeys lead to qualified inquiries. Use page analytics alongside customer feedback. Clicks into a hub are useful context, but they do not establish that the reader found a satisfactory answer. Inspect actual AI source links separately. If a resource is cited, check the context; a citation does not validate the whole hub. If it is not cited, first assess its value to buyers before creating more pages. The fintech answer-hub dossier focuses on explaining product scope and boundaries. The local-service dossier addresses service fit and practical information. For recurring consulting questions, use the consulting FAQ dossier. Start with Arrow's answer resources or request a free audit to identify the useful paths your existing site lacks.

Read the source guide: An Answer Hub Playbook for Useful Buyer Journeys →

No ChatGPT Search, Google AI Mode, AI Overview, Perplexity consumer search, Claude, Gemini, or Copilot observation was performed for this example. No provider answer was requested. Brand mention rates, citation rates, recommendation rates, ranks, referral traffic, and qualified leads remain null. Search Console index coverage and generative AI impressions require a separate account-backed export. They cannot be inferred from these public HTTP responses.

Read the source guide: Arrow AI public audit example: source checks with real traces →

The technical score summarizes public website checks. Confirmed brand references in API answers are reported separately, with a denominator. An unmeasured platform has no score; neither metric guarantees a consumer search recommendation.

Read the source guide: Arrow GEO — AI Visibility Platform →

Test prompts reflecting the stated requirements rather than only the category name. Check whether answers describe your product accurately, cite the comparison, and repeat unsupported claims. Keep the observed AI answer separate from your own suitability assessment. Connect the page to an appropriate demo or evaluation path and track qualified opportunities mentioning the comparison. Log which requirement brought the buyer forward and which unresolved limitation stopped the evaluation. The SaaS overview can provide the commercial context, while the comparison guide and citation tracking guide support the editorial and measurement work. Start with a free audit when the source gap is unclear.

Read the source guide: B2B SaaS Comparison Pages for AI Search: Fit, Integrations, and Switching Costs →

Track prompt coverage, cited pages, citation frequency, competitor mentions, answer sentiment, source quality, backlinks, structured data, branded search lift, AI referral traffic, CRM lead quality, and whether answer pages route visitors into demos, audits, or sales conversations.

Read the source guide: Best AI Visibility Platforms for B2B Teams in 2026 →

Measure indexed pages, prompt visibility, citations, competitor mentions, referral traffic, branded search, form submissions, demo requests, and pipeline influenced by answer-ready pages.

Read the source guide: Best ChatGPT Visibility Strategy for B2B Teams in 2026 →

Measure prompt visibility, AI citations, source mentions, branded search, demo requests, organic pipeline, sales call mentions, and conversion from answer-ready pages.

Read the source guide: Best GEO and AEO Partners for SaaS Companies →

Track the work you can substantiate: policy clarified, operational issue reviewed, source corrected or answer observed with more accurate attribution. Do not reduce the whole task to a positivity score. A more accurate answer may still mention a genuine limitation. Keep customer outcomes distinct from public descriptions. Fewer avoidable support questions can be a useful operational signal, while a corrected AI response is an observation about a particular interaction. Neither alone proves that the other caused it. Use public proof to improve the evidence behind your own claims. If the response invents a factual allegation unsupported by the displayed sources, continue with the unsupported claims guide. The cluster audit keeps the issue connected to the wider business record.

Read the source guide: Can Negative Reviews Change How AI Describes Your Business? →

Use the platform's policy process for reviews that violate its rules. Google explains that disagreement or dislike is not itself a basis for removing a review. Keep a report grounded in the applicable policy and evidence. A report submitted is not a review removed. Track the decision separately, and do not promise that reporting a review will change an AI answer. The answer may rely on other information or continue to summarise a historical source. Avoid fake reviews, fabricated testimonials and selective evidence presented as a complete customer picture. They make the public record less trustworthy. The useful work is to improve the real service, make current facts accessible and respond accurately to specific issues.

Read the source guide: Can Negative Reviews Change How AI Describes Your Business? →

Create separate reporting columns for brand mention, linked citation, landing-page visit and qualified inquiry. Open a sampled citation to confirm it points to the intended canonical page and supports the nearby statement. A citation to an old pricing page may technically count as visibility while creating the wrong commercial expectation. Use your analytics acquisition data to inspect ChatGPT referrals, including the documented campaign parameter where available. Then review the destination and conversion path. Do not divide observed prompt citations by site visits and call the result a click-through rate: the two measurements usually cover different populations. Keep the sampled visibility panel alongside actual referral and conversion reporting.

Read the source guide: ChatGPT AI visibility: discovery, citations and qualified visits →

Start with a fixed set of unbranded buyer questions, the actual sources shown and qualified visits from ChatGPT. Keep each metric separately defined.

Read the source guide: ChatGPT AI visibility: discovery, citations and qualified visits →

API tests can support controlled, repeatable research, but label them as API observations. A developer chooses inputs and available controls for a specific endpoint and model. That setup is not automatically identical to a buyer's consumer session. Use separate series for consumer observations and API tests; explain any comparison protocol before drawing a connection. OpenAI's web search API documentation distinguishes inline citation annotations from the broader list of retrieved sources and documents controls such as domain filtering and location. A URL in retrieved sources is not necessarily a citation shown in the final answer. A filtered test also answers a narrower question than an unrestricted search.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

A source label or referral does not provide the original conversation. A prospect may voluntarily share it, but that is separate evidence and should be recorded as such.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

Useful question: How did the model answer without this retrieval tool? Boundary to disclose: This is not a live search-citation test.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

Useful question: What appeared in this defined interface setup? Boundary to disclose: Sample and context do not cover every user.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

No. The API can expose a broader set of consulted sources than the citations shown in the answer. Count final-answer citations and retrieved sources as different evidence types.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

A defined test can record the order or presence of brands in an answer, but it does not establish a universal position across questions, contexts and users. Report the observation setup and date.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

Keep them separate by default. If you publish a composite, disclose its components, weighting and purpose, and preserve the separate results so readers can understand the differences.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

Referral analytics can show recorded arrivals and subsequent website behavior. OpenAI documents the chatgpt.com UTM source used in search referrals. That signal does not include the original prompt. OpenAI publisher FAQ provides the current referral guidance. Review the landing pages and inquiries in the source cohort, then inspect qualification in the CRM. A visitor may copy a URL, return later through another route, or decline analytics collection. Treat incomplete journeys as a coverage limitation. Do not multiply sampled mention rates by an imagined number of users to manufacture impressions. The attribution guide describes the evidence fields needed downstream.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →

OpenAI explains that ChatGPT may search automatically, rewrite a question into search queries, use approximate location and use relevant memories when enabled. Search citations can also be incomplete or incorrect. These documented behaviors make context relevant to interpretation. OpenAI's search guide describes them. Choose a reproducible setup for your observation panel and record its limits. A fresh conversation reduces one source of carryover, but does not make the observation representative of every buyer. Label account state, visible model or mode where available, search behavior, language, location setting and prior conversation. Do not invent a hidden model version when the interface does not expose it.

Read the source guide: ChatGPT Visibility for B2B: What Can You Actually Measure? →