Five new Profound reports built on the platform's v2 API carry the identifier of every dimension alongside its name, so visibility, citation and sentiment data now joins directly to your Models, Regions, Topics and Assets reports.

Profound released a second generation of its reporting API. Improvado now offers five reports built on it, alongside the Profound reports you already run. Nothing has been renamed, removed or migrated, and no existing extraction changes behaviour — the V2 reports are additional report types you can choose to add.

What you get

• Identifiers, not just names. Every breakdown — model, topic, region, persona, prompt — now arrives with its identifier as well as its label. The existing reports carry names only, which means matching them to your Models, Regions, Topics or Assets reports depends on the text matching exactly. The V2 reports join on the identifier instead.
• New metrics. Citation rank and citation share on citations, and average position on visibility.
• Richer filtering. Pre-filters become a nested structure that combines conditions with and, or and not, and adds regular expression and case-insensitive matching.
• Answers V2 delivers the raw material behind every other report: one row per model answer, with its prompt, model, topic, region, tags, and the mentions, citations, search queries and sentiment claims extracted from the answer text. Nothing is aggregated. The full answer text is an optional column, so you can leave it out to keep the extraction small.

Before you switch a dashboard over

The V2 reports are a different generation of the API, not a drop-in replacement. Four differences matter if you plan to move existing reporting across.

• Dates are inclusive, and in Eastern Time. Both the start and the end of the date range are included in the results.
• Yearly granularity is not available. The V2 reports support daily, weekly and monthly buckets.
• Saved pre-filters do not carry across. A filter written for one of the existing reports uses the older flat list of conditions and has to be rewritten in the nested form for a V2 report.
• Each report limits how many breakdowns you can combine, and the limit differs. Citations accepts one dimension besides Date, or Topic and Model together; Sentiment accepts up to two; Visibility and Query Fanouts accept any combination. Selecting more than a report allows produces an error that names exactly which selection to change.

Numbers will not tie out exactly against the existing reports

Expect small differences rather than identical figures. The clearest cause is that Citations V2 groups by registrable domain, folding subdomains together, where the existing citations report groups by hostname — so www.example.com and help.example.com become one row rather than two. Treat a V2 report as a new series rather than a continuation of the old one, and run the two side by side over a period you know before retiring anything.