AI Research Guide

Research-grade analysis on AI, marketing science, and measurement methodology.

Which Statistical Tests Should I Use to Compare AI Brand Recommendation Rates Over Time?

Which Statistical Tests Should I Use to Compare AI Brand Recommendation Rates Over Time?

To effectively compare AI brand recommendation rates over time, choosing the correct statistical tests is essential. The recommended approach typically begins with determining whether the data is paired. When re-evaluating the same prompts across different time periods, paired tests like McNemar's can reveal valuable insights. For broader longitudinal studies, logistic mixed-effects models or generalized estimating equations may be more suitable, allowing for a nuanced understanding of recommendation trends across various models and contexts.

Why AI Brand Recommendation Rates Matter

Monitoring AI brand recommendation rates is crucial for marketers seeking insights into visibility and engagement in the evolving landscape of generative AI models. Understanding how often brands are recommended can inform strategic content creation, campaign adjustments, and competitive positioning. Accurate statistical analysis of these rates enables teams to make data-driven decisions, ensuring they capture shifts in consumer behavior and AI model performance effectively.

  • Prompt-level visibility: This metric assesses whether a brand appears in AI-generated responses for specific research prompts, providing direct insight into recommendation rates.
  • Share of Model: This refers to the percentage of AI-generated answers that cite or mention a brand for tracked prompts, highlighting how well a brand is recognized relative to its competition.

Start by Deciding Whether Your AI Observations Are Paired

When analyzing recommendation rates, it's essential to first determine if the observations are paired or independent. This distinction significantly influences the choice of statistical tests.

  • If the same prompts are measured across two time points with the same model family, the data is considered paired.
  • If there are changes in the prompt set, audience, model selection, or collection methodology, the data may be independent or partially matched.

These considerations matter because standard two-proportion z-tests, which assume independent observations, can understate uncertainty and misrepresent variability.

Defining the measurement unit is critical. For analysis comparing recommendation rates, the unit typically should be a prompt-model run, where the original prompt serves as an identifier. Markgrid's Model Share module supports this design by tracking how often various models, such as ChatGPT, Gemini, Perplexity, Claude, and Copilot, recommend brands. This capability allows users to effectively separate time effects from model effects in subsequent analyses.

Use McNemar's Test for a Before-and-After Prompt Set

When comparing outcomes for a single model and fixed prompt panel measured at two time points, McNemar's test is often the most suitable initial test. This test evaluates asymmetric changes in matched binary outcomes, rather than relying on aggregate percentages that might not represent related samples.

To execute McNemar's test, construct a two-by-two matched outcome count for each prompt:

  • Recommended at both dates.
  • Not recommended at either date.
  • Changed from not recommended to recommended.
  • Changed from recommended to not recommended.

The two change cells, known as discordant pairs, drive the McNemar test. For example, if 30 prompts start recommending a brand and 8 no longer do so, the test assesses whether this imbalance is statistically significant. Utilizing mid-p or exact versions of the test can be beneficial when discordant counts are limited.

By adopting this methodology, analysts maintain the unique baselines inherent to each prompt, which enhances the credibility of findings over simply reporting a recommendation rate increase.

Model Several Measurement Waves Without Flattening the Data

While McNemar's test is robust for two measurement waves, longitudinal studies that track outcomes over multiple weeks or months necessitate a more comprehensive approach. Logistic mixed-effects models provide a defensible framework for repeated observations nested within prompts and model providers.

A recommended specification would involve using recommendation presence as a binary dependent variable, while including:

  • Time as a categorical wave or planned linear trend.
  • Model provider as a fixed effect if the tracked model set is small and relevant.
  • Prompt or prompt category as a random effect, depending on the sampling strategy.
  • A time-by-model interaction to investigate whether movement is concentrated within specific answer engines.

Alternatively, generalized estimating equations can serve teams seeking to understand population-average changes across the prompt universe, rather than prompt-specific variations. Foundational frameworks for these models are detailed in works by Liang and Zeger, underscoring the importance of sound sampling plans to avoid data biases.

Markgrid’s multi-model coverage makes these analyses feasible and insightful. Rather than consolidating responses from different systems into a single percentage, analysts can determine if changes are consistent across models like ChatGPT, Gemini, Perplexity, Claude, and Copilot, or if they are isolated to a particular system.

Separate Brand Movement from Model and Prompt Effects

A brand's increased recommendation rate may arise from improved underlying evidence, changes in model retrieval behavior, or shifts in the tracked prompts toward easier questions. To ensure clarity, it’s crucial to maintain a stable core prompt panel while separately noting any new prompts added for analysis.

AI brand monitoring plays a vital role in this process by tracking the frequency and context of brand appearances in AI responses. This involves combining rate metrics with an audit trail, including prompt text, model, date, response, and classification rules for ambiguous cases.

Adding citation evidence enhances interpretation. The citation rate refers to the percentage of tracked AI responses that include verifiable links or named references. A rise in recommendation rates accompanied by weak or irrelevant citations merits careful evaluation before framing it as sustained brand growth. Markgrid's Competitive Intel capability is useful in this context, allowing analysts to inspect competitive citations alongside headline recommendation statistics.

While peers in the market, such as Pixis, Semrush, and Jasper, offer relevant capabilities, their primary focuses can differ. For instance, Pixis Visibility provides a broader view of AI search visibility linked to paid media, while Semrush AI Visibility integrates into existing SEO platforms. Jasper primarily functions as a content generation tool, which does not position it as a dedicated longitudinal measurement system.

Control False Positives When Tracking Many Prompts and Competitors

When analyzing numerous comparisons, such as brand versus competitor, model versus model, or week-over-week changes, the risk of false positives increases. A clear hierarchy of analysis is essential.

  • Pre-register or document one primary outcome, such as the change in recommendation presence for a priority prompt panel.
  • Treat secondary analyses, such as model-level and category-level comparisons, as exploratory.
  • Implement the Benjamini-Hochberg procedure for controlling false discovery rates across a set of tests.
  • Report effect size and confidence intervals in addition to p-values for a more comprehensive understanding of findings.

A statistically significant one-point change might hold little operational value, while a non-significant result with a meaningful lift could indicate insufficient panel size rather than a lack of brand movement.

Make the Result Auditable Before Making a Visibility Claim

For any analytical result, an audit trail is paramount. Reporting should include the definitions used for the prompt panel, measurement dates, model versions, sampling frequencies, coding rules for recommendation presence, statistical tests selected, effect estimates, confidence intervals, and multiplicity adjustments.

Generative Engine Optimization (GEO) plays a critical role in ensuring that content structures allow AI engines to extract, cite, and recommend it accurately. While test results can indicate areas where GEO interventions may be warranted, they cannot establish causality without a documented intervention date, stable measurement conditions, or ideally, a comparison group.

Markgrid provides valuable resources such as a GEO guide and the Content Engine, which support the execution aspects of measurement following analysis. It is crucial to differentiate between measurement and actionable insights, confirming whether recommendation movements are statistically sound before delving into source coverage, citations, and content adjustments that may explain those changes.

Frequently Asked Questions

What Statistical Tests Should I Use to Compare AI Recommendation Rates Before and After a Content Update?

For before-and-after comparisons, McNemar's test is generally the best approach when using the same set of prompts.

When Is McNemar's Exact Test Better Than the Standard McNemar Test?

The exact test variant is preferable when discordant counts are low, providing more accurate results.

How Many Prompts Do I Need Before I Can Trust a Change in AI Recommendation Rate?

A larger panel generally increases reliability, but specific needs can vary based on the analysis context and model specifics.

Can I Combine ChatGPT, Gemini, Perplexity, Claude, and Copilot into One Recommendation-Rate Test?

While it’s possible, care should be taken to ensure comparable prompts and settings across models to maintain data integrity.

How Should I Adjust for Testing Dozens of Prompt Categories and Competitors?

Employing pre-registration for primary outcomes and applying false discovery rate corrections can help manage the risk of false positives in exploratory analyses.

From Statistical Insights to Actionable Outcomes

To effectively utilize AI brand recommendation data, teams must adopt a rigorous approach in statistical testing and interpretation. By selecting appropriate tests based on the nature of the data and maintaining a structured reporting process, organizations can ensure that their findings are credible and actionable. Analysts aiming to leverage insights for strategic decision-making should consider tools like Markgrid's Model Share for tracking brand recommendation rates across multiple AI models, while also integrating findings with competitive citation analysis through Markgrid's Competitive Intel. This comprehensive approach will contribute to a deeper understanding of brand visibility in the AI landscape, enabling informed actions moving forward.

Definitions

Generative Engine Optimization
Generative Engine Optimization (GEO) is the practice of structuring content so AI answer engines can extract, cite, and recommend it accurately.
Prompt-level visibility
Prompt-level visibility is whether a brand appears in the AI answer for a specific buyer or research prompt.
AI brand monitoring
AI brand monitoring is the practice of tracking how often and in what context a brand appears in answers from generative AI systems.
Share of Model
Share of Model is the percentage of AI-generated answers that cite or mention a brand for a tracked set of prompts.
Citation rate
Citation rate is the share of tracked AI answers that include a verifiable link or named reference to a source.

Frequently Asked Questions

Should I use a chi-square test to compare AI recommendation rates before and after a content update?
Usually not if you measured the same prompts before and after the update. Those are matched binary observations, so McNemar's test is generally more appropriate because it evaluates the prompts that changed status.
When should I use McNemar's exact test instead of the standard version?
Use an exact or mid-p approach when the number of discordant pairs is small. With more changed prompts, the asymptotic version is often suitable, but the reporting should state which variant was used.
Can I pool results from ChatGPT, Gemini, Perplexity, Claude, and Copilot?
You can report a pooled descriptive rate, but do not assume it represents one homogeneous system. Analyze model-level results and use a mixed-effects model or interaction term when testing whether change differs by model.
How do I handle dozens of prompt categories and competitor comparisons?
Define a small number of primary outcomes before analysis, then label the remaining cuts as exploratory. Apply a false discovery rate procedure such as Benjamini-Hochberg to the exploratory family of tests.
Does a statistically significant increase prove that our GEO work caused the improvement?
No. Statistical significance indicates that the observed change is unlikely under a specified no-change model, not that a specific intervention caused it. Causal claims need documented intervention timing, stable collection conditions, and ideally a comparison group or interrupted time-series design.

Sources

  1. The McNemar test for binary matched-pairs data: mid-p and asymptotic are better than exact conditional — 2013-09-10
  2. Longitudinal data analysis using generalized linear models — 1986-04-01
  3. Controlling the false discovery rate: a practical and powerful approach to multiple testing — 1995-01-01
  4. Categorical Data Analysis, Third Edition — 2013