Analytics

Read analytics for the active product from the terminal. Analytics commands are read-only and require a token or API key with the analytics:read scope.

Analytics commands require --scope <product-slug>/<org-slug>.

# Product share of voice over the last 30 days
tpc analytics sov --scope my-product/pro-org

# Industry ranking (competitor share of voice)
tpc analytics sov --scope my-product/pro-org --by competitor

# Per-prompt sentiment with week-over-week change
tpc analytics sentiment --scope my-product/pro-org --wow

# AI traffic grouped by page
tpc analytics traffic --scope my-product/pro-org --by page

# Cited sources leaderboard
tpc analytics citations --scope my-product/pro-org --last 30d --top 25

Explore: build your own analytics query

tpc analytics explore is the flexible query surface behind the fixed commands above. Pick one metric, group it by at most one value with --by, then scope it with filters and a date window. It calls the POST /api/v1/analytics/explore endpoint, so anything you can do here you can also do from the API or the exploreAnalytics MCP tool.

Metric	Group by (`--by`)	Filters
`sov`	`date`, `prompt`, `topic`, `engine`, `competitor`	`--view`, `--prompt`, `--topic`, `--engine`, `--region`
`citations`	`source`, `category`, `type`, `author`, `model`, `date`	`--view`, `--topic`, `--region`, `--category`, `--content-type`, `--model`, `--author`, `--query`, `--product-mentioned`
`traffic`	`date`, `page`, `model`, `category`	`--traffic-type`, `--provider`, `--category`
`sentiment`	`prompt`	`--view`, `--prompt`, `--topic`

# Product share of voice summary
tpc analytics explore --scope my-product/pro-org --metric sov

# Industry ranking: every competitor's share of voice, ranked
tpc analytics explore --scope my-product/pro-org --metric sov --by competitor --last 30d

# Industry ranking within one topic (category ranking)
tpc analytics explore --scope my-product/pro-org --metric sov --by competitor --topic <topicId>

# Share-of-voice time series for one prompt
tpc analytics explore --scope my-product/pro-org --metric sov --by date --prompt <promptId>

# Citations grouped by source category over the last 90 days
tpc analytics explore --scope my-product/pro-org --metric citations --by category --last 90d

# Top cited sources sorted by unique conversations
tpc analytics explore --scope my-product/pro-org --metric citations --by source --sort-by mentions --top 25

# Weekly AI traffic buckets
tpc analytics explore --scope my-product/pro-org --metric traffic --by date --bucket week

# Human traffic by page
tpc analytics explore --scope my-product/pro-org --metric traffic --by page --traffic-type human

# Sentiment per prompt with week-over-week comparison
tpc analytics explore --scope my-product/pro-org --metric sentiment --compare wow

Date windows default to the last 30 days. Use --last 7d|30d|90d, or --from and --to together to select a range. For SoV, that range selects snapshot dates: omitting --by returns only the latest available trailing-30-day snapshot, while --by date returns one overlapping trailing-30-day snapshot per date. SoV mentions and runs are not start-to-end totals, so you must not sum them across dated rows. The response is a generic table: the API returns column metadata alongside flat rows, so every metric renders the same way. Add --json to get the machine-readable response for scripting:

# Top three competitors as JSON rows
tpc analytics explore --scope my-product/pro-org --metric sov --by competitor --top 3 --json | jq '.rows'

Filters that do not apply to the chosen metric are rejected with the supported list, so agents and scripts get a correcting error instead of silently wrong data. See tpc analytics explore --help for the full flag reference.

Get started

Commands

Recipes

Reference

Analytics

Analytics

Explore: build your own analytics query

​Analytics

​Explore: build your own analytics query

Analytics

Explore: build your own analytics query