Coverage, reporting and accountability across markets and teams

Answers collected from inside every market you sell in, a report each stakeholder can read, and every number traceable to the stored answers behind it. Rates carry their counts and anything inferred is labelled, which is what a procurement review asks for.

Every market is its own measurement

The same question answered in Zurich, Berlin and Austin is three measurements, not one. Answers are collected from inside each country, stored in full with their sources, and reported per market and rolled up across markets.

  • Per-market views: visibility, recommendation rate, competitors and cited sources for one country and language
  • Roll-up views across markets, with each market's answer count shown, so a small market cannot hide inside a large one
  • A per-engine breakdown inside every market, because one engine dropping the brand in one country is a specific finding
Finding

Ridgewell is named in 3 of 6 engines for alpine hardshell questions and recommended in 0.

Observed over 12 questions · 144 answers · Aug 10–Sep 7, 2026
Question
best hardshell jacket for alpine climbing
Engine
ChatGPT, web, not personalised
Market
United States, collected from inside the market
Collected
Sep 8, 2026, 06:12 UTC
Answer
#a7f3-2026-09-08-us-chatgpt · stored in full
Sources in answer
gearbench.example · trailnotes.example · alpstore.example
ObservedCounted from stored answers.EstimateNever shown as a rate. Where something was not measured you see a dash.

Illustrative example · fictional data.

Who sees what

One workspace per brand or region, roles per workspace. What each stakeholder reads and does.

CMO
Reads the weekly PDF and the roll-up: visibility and recommendation rate across markets, who the engines name instead, and the open briefs by priority. Does not have to log in to make the monthly call.
Regional marketing
Owns one or more markets. Sees the per-market views, the competitors named in their country and the briefs scoped to it, and marks work done.
SEO and content
Takes the briefs that say publish, update or correct. Reads which pages the engines cite and which they ignore, per market, and the questions each page should answer.
PR and communications
Takes the briefs that say earn a placement: the domains each engine relies on where a competitor appears and the brand does not. Reads sentiment by aspect for the brand and each competitor.
Data and analytics
Exports answers and rates as CSV, pulls cited sources over the API, and connects traffic and conversion data where it exists. Checks that every rate carries its count and that observed and inferred figures are labelled apart.

Integration

The product's outputs, in the formats your teams already use.

  • Weekly PDF

    Per domain, every Monday, with the period and the answer count printed on it. Forward it as it is.

  • CSV export

    Answers, mentions with their role, cited sources and rates by market and engine, for your warehouse or BI tool.

  • Cited sources over the API

    The domains and URLs the engines cite for your topics, per market, for media planning and partner briefs. On Enterprise and Government contracts.

  • SSO and DPA

    Single sign-on and a data processing agreement are available on Enterprise contracts. Viewer, editor and admin roles are on every plan.

Procurement

What the contract covers, and where the questions go.

  • Invoiced billing on Enterprise contracts; self-serve plans are billed monthly by card
  • A security review before signature, answered from the documented controls, subprocessors and data flows
  • Quotas for questions, domains, markets, competitors and seats set by contract and changed by contract, with managed onboarding
  • Data residency questions handled in the security review, with an answer specific to your data flows
  • A data processing agreement as part of the contract

Success criteria for an evaluation

Agree these before the baseline. Each one is observed, carries its count, and can be read straight off the product.

Coverage of questions per market
The number of tracked questions collected in each market during the period, against the number agreed in scope. A market below scope is reported as a coverage gap, not as a lower rate.
Share of answers naming the brand
Of the answers collected in the period, how many name the brand at all, shown as a count and a share per market and per engine, and compared with the baseline week over the same questions.
Recommendation rate on transactional questions
Among the questions weighted closest to a purchase, the share of answers in which the brand is recommended rather than only listed or mentioned. Counts are shown; the intent weighting is labelled as an estimate with its inputs.
Cited-source gaps closed
The number of sources the engines rely on for your topics that did not cite the brand at baseline and do at review, with the date each change was first observed.
Time from finding to brief
Days between a gap first appearing in the stored answers and a brief being assigned to a team, read from the product's own timestamps.

A four-week evaluation

One typical sequence. The weeks can stretch; the order should not.

  1. Scope

    Week one. Choose the markets, the topics and the competitors, agree the success criteria above and decide who reads what. Bluemoon generates the questions from your site; regional teams keep, edit or add.

  2. Baseline

    Week two. Daily collection runs from inside each market. By the end of the week every criterion has a baseline with its count, and the first gaps are visible per market and per engine.

  3. Briefs

    Week three. Gaps become briefs with the questions, engines and sources behind them. Content, SEO and PR take theirs. The point of the week is to check that the briefs are actionable inside your organisation, not to finish them.

  4. Review

    Week four. The criteria are read again against the baseline, with counts. Movement is reported as observed; nothing is attributed to work that has not had time to show up in collection. The review ends with the quotas and roles a contract should set.

Questions enterprise teams ask

How long does an evaluation take?
Four weeks is typical: one to scope, one to baseline, one to turn gaps into briefs, one to review against the criteria. Collection starts the day a market is set up, and the first answers arrive within the hour.
Can we evaluate several markets at once?
Yes. Every market is collected from inside its country and language and reported on its own, with a roll-up across markets. Growth covers multimarket scaling; Enterprise and Government contracts set the market quota along with the rest of the scope.
Is single sign-on available?
On Enterprise contracts. Viewer, editor and admin roles are available on every plan and are granted per workspace.
Which certifications do you hold?
We do not list certifications on this page. Controls, subprocessors and data flows are documented on the security page, and we answer your security questionnaire from there as part of the contract.

Plan your evaluation

Tell us the markets, the teams and the criteria that matter. We will scope a four-week evaluation and the contract that follows it.

See pricing