Prompt Tracking: Choosing Prompts That Represent Your Buyers

Prompt tracking is the practice of running a fixed set of buyer questions through AI answer engines such as ChatGPT, Perplexity, Gemini, Claude and Google AI Overviews on a schedule, and recording whether your brand is mentioned, cited and recommended. The data is only as good as the prompts you choose. Most teams start by pasting their keyword list into a tracker and get a costly report that measures questions no buyer asks. In October 2026, AI answers shape shortlists in cloud security, consumer security and AI software, so choosing the prompt set is a research decision. This guide gives a vendor-neutral method for prompt tracking. You source prompts from real customer language, cluster them into buying jobs, score them, prune them, and turn the findings into content.

What is prompt tracking?

A prompt tracker records how AI assistants answer a defined set of category questions over time and where your brand appears in those answers. Each tracked prompt is run on a schedule. The tracker then records mentions, position, sentiment and the sources the model cited.

It looks like rank tracking, but the unit of measurement is different. A rank tracker checks one URL's position for one keyword. A prompt tracker checks whether an assistant names you, how it describes you and which pages it relied on. That answer can change between two identical runs.

If you are still defining the KPIs, start with our guide to AI visibility metrics and baselines, then return here to build the prompt set behind them.

Why prompt selection decides whether the data is worth anything

The prompts you pick set your cost, your bias and what your team ends up building. A weak prompt set produces confident numbers about the wrong market. Most trackers charge by prompt volume or by prompt runs across engines, so every low-value prompt costs budget and drags down the average.

• Cost: tracking 500 prompts across five engines means 2,500 answers per cycle. Pruning 30% of low-value prompts saves money and reviewer time.
• Bias: prompts written by the marketing team over-represent the brand's own vocabulary. Branded prompts inflate visibility because the model is answering about you by design.
• Measurement quality: broad prompts like "best security software" return generic lists that swing every week. Specific prompts with constraints return stable, comparable answers.
• Strategic value: a prompt that matches a real buying job tells you which page, review or thread is missing. A vanity prompt tells you nothing you can act on.

Buyers also rarely type a bare question. They paste requirements, describe their stack and follow up. Gartner argues that context engineering is replacing prompt engineering as the way enterprise AI gets useful output. Your tracked prompts should carry the same context your buyers supply.

How to build a buyer-representative prompt set

Collect real customer language, cluster it into buying jobs, and sample across funnel stages and segments. The steps below work whether you use a spreadsheet or a dedicated platform.

Source prompts from customer language

1. Collect raw wording from sales call transcripts, discovery-call recordings, CRM notes, support tickets, site search logs, G2 and app store reviews, Reddit threads in your category, People Also Ask boxes, and any internal AI assistant logs. Keep the original phrasing intact.
2. Normalize each item. Tag the canonical task (the decision underneath), the category, the intent stage (learn, evaluate, choose, implement, diagnose), the constraints (role, budget, team size, geography, compliance), and the evidence the buyer expects (pricing, docs, reviews, certifications).
3. Cluster in two passes. First, group by canonical task plus intent stage using semantic similarity. Then check each cluster's edges. If one answer satisfies every prompt in it, keep it together. If changing one constraint changes the recommendation, split on that constraint.
4. Merge, split or hold. Merge clusters with the same decision and evidence. Split clusters where constraints need different proof. Hold ambiguous or one-off prompts until they recur.
5. Validate against AI referral data. In GA4, filter sessions referred by chatgpt.com, perplexity.ai, gemini.google.com and copilot.microsoft.com, then check which landing pages they reach. Those pages point to the questions assistants already send you.

Referral data undercounts. Traffic from assistant mobile apps often arrives without a referrer. On iOS, device-level attribution depends on the Identifier for Advertisers, a random device identifier Apple assigns to every device, which many users decline to share. Use GA4 to check direction, and expect it to miss part of the traffic.

Describe the buyer behind each cluster

Every cluster should answer six questions: who the buyer is, which funnel stage they are in, what they are deciding, which criteria matter, what objection they raise, and where they are. Put those details directly into the prompt wording.

• Persona and stage: a CISO evaluating vendors asks different questions than an engineer troubleshooting a deployment.
• Use case: "for Kubernetes workloads" or "for a family with teenagers" changes the shortlist.
• Urgency and budget sensitivity: "fastest to deploy" and "cheapest option under $X per seat" pull different brands.
• Decision criteria: buyers name requirements like SOC 2, data residency, integrations and refund policy.
• Geography and language: "best antivirus for a family" (US), "best anti-virus for a family of five" (UK), "beste Antivirensoftware für die Familie" (DE) and "meilleur antivirus pour toute la famille" (FR) are the same intent with different answers.

Size the sample and balance breadth against depth

Size the set by buying job instead of keyword count. As a starting point, track 10 to 25 prompts per priority buying job. That is enough to cover phrasing and constraint variants without paying for duplicates. For one product line, 150 to 300 prompts is a workable range. Weight the mix towards decisions you can win:

• About 50% non-branded discovery and evaluation prompts
• About 25% competitor comparison prompts
• About 15% branded defense prompts
• About 10% post-purchase and implementation prompts

To avoid selection bias, have sales or customer success write a share of the prompts blind, without seeing the keyword list. Never seed a prompt with your brand name unless it is deliberately a branded prompt.

Rewrite weak prompts

Prompt library to adapt

How to score and prune prompts

Score every prompt with a weighted decision matrix, then keep, revise or retire it against fixed thresholds. Rate each criterion from 1 to 5, multiply by its weight, and sum the results for a score out of 5.

For example, "Which CSPM tool suits a fintech on AWS and Azure?" might score intent 5, value 5, recommendation 4, relevance 4, regional fit 4 and repeatability 3. The weighted total is 4.25, a clear keep.

How to measure prompts without fooling yourself

Measure each prompt as a rate across repeated runs and engines. A single AI answer is one sample. Run each prompt three to five times per cycle per engine and report the share of runs.

Metrics that matter

• Inclusion rate: runs that mention you ÷ total runs.
• Share of mentions: your mentions ÷ all brand mentions in the set.
• Share of first mention: runs where you are named first ÷ total runs.
• Recommendation rank: your average position when the answer is a ranked list.
• Sentiment: positive, neutral or negative framing, reviewed by hand on branded prompts.
• Citation frequency: how often your domain is a cited source, separate from being mentioned.
• Competitor overlap: which brands appear alongside you, and which appear when you do not.
• Change over time: four-week rolling averages, never a single week.

For more on reading mentions versus citations, see our guide on tracking whether AI answers mention you.

Pitfalls to control

• Wording sensitivity: "best" and "top" can return different lists. Track two or three phrasing variants per cluster and report the cluster average.
• Model volatility: log the model and version per run, and annotate trend lines when a model updates.
• Personalization: memory and chat history skew answers. Use clean, logged-out sessions or API calls.
• Location: set the market explicitly in the prompt or the collection location.
• Recency: browsing-enabled answers react to last week's news, so separate those runs from model-only runs.
• Hallucinations: a mention with wrong pricing or features counts against you. Flag it.
• Citation mismatch: the model may name you while citing a competitor's comparison page, or cite your page without naming you.
• Prompt contamination: earlier turns that mention your brand bias the answer. Run each prompt in a fresh session.

Qualitative review

Numbers say where you are missing, and reading the answers says why. For every prompt where a competitor appears and you do not, record three things: the sources the model cited, the criteria it used to rank vendors, and the claim it made about the winner. If Reddit threads and review sites dominate the citations, owned content alone will not close the gap.

Mapping the method to tools

On G2 as of October 2026, Profound rates 4.6 from 1,124 reviews, with reviewers singling out prompt tracking, citation analysis and competitor benchmarking. Some also flagged a confusing average position rank that surfaces generic non-brand entries. Scrunch AI rates 4.6 from 73 reviews and is praised for custom prompts and competitor comparison, though some users cannot edit personas after creating them. Semrush rates 4.5 from 3,945 reviews.

Worked example: from prompt set to content changes

This example follows the method from prompt selection to measurable change. The figures below are illustrative, for a modeled mid-market cloud security vendor.

1. Source and cluster: the team pulls 900 raw questions from Gong transcripts, Zendesk tickets, G2 reviews and r/cybersecurity and r/devops. It clusters them into 14 buying jobs, such as "CSPM for multi-cloud fintech" and "replacing a legacy SIEM".
2. Score: 240 candidate prompts are scored. 180 score 3.5 or higher and enter tracking across ChatGPT, Perplexity, Gemini and Google AI Overviews, with three runs each per week.
3. Baseline over four weeks: non-branded inclusion is 22%. The main competitor sits at 48%. On comparison prompts, the most cited sources are the competitor's own "vs" pages, two Reddit threads and a G2 category page.
4. Prune: after six weeks, 35 prompts are retired. Twenty never named a vendor, ten targeted markets the company does not sell in, and five were news-driven.
5. Act on gaps: the team publishes three comparison pages, an evidence page covering SOC 2, ISO 27001 and data residency, and an FAQ correcting a pricing claim assistants repeated wrongly. Its engineers also answer the two cited Reddit threads with disclosed, guideline-compliant replies.
6. Outcome after 12 weeks: non-branded inclusion rises from 22% to 35%. The vendor's own comparison pages now appear among cited sources, and the wrong pricing claim disappears from branded answers.

Turning findings into content

• Missing on comparison prompts: publish honest comparison pages with tables the model can quote.
• Wrong facts in answers: publish an evidence page with certifications, pricing structure and specifications.
• Lost on criteria prompts: write answer-shaped articles that define the criteria and show where you meet them.
• Missing in one region: build local pages with regional support, compliance and spelling.
• Citations dominated by third parties: earn presence on review sites and in the Reddit threads the model reads.

Maintenance cadence

• Weekly: review inclusion and citation movement, read answers for the top 20 business-value prompts, and flag hallucinations.
• Monthly: add prompts from new sales and support language, apply the keep, revise and retire thresholds, and update the competitor list.
• Quarterly: refresh the baseline, re-weight the scorecard, check model updates and re-run regional and language variants.

Where Tellr fits in prompt tracking

Tellr fits teams that want the prompt research to drive the work rather than end in a dashboard. It is a managed earned-visibility program run by a senior team on its own platform. Each week it tracks which domains Google and its AI Overviews cite for the category's queries, labelled as your site, competitors, Reddit, review sites or references. It then produces the fix. It needs a few weeks to map the category and agree the brief, so it does not suit a three-week launch.

• Comparison pages, reviews and answer-shaped articles written to be quoted by ChatGPT, Perplexity, Gemini, Claude and Google AI Overviews, published to your CMS
• Subreddit mapping, a daily thread radar and guideline-checked replies behind an approval gate
• Weekly citation share reporting with a monthly program review
• API access and "Tellr for Claude", an MCP server for questions about your program

Whatever stack you choose, the method is the same. Build prompts from buyer language, score them, prune hard and tie every gap to an asset. Done that way, prompt tracking tells your team what to build next instead of sitting in the budget as a cost line.

FAQ