Connect Trakkr data to Looker Studio for advanced brand visibility analytics and reporting
Connect your Trakkr brand visibility data directly to Looker Studio (formerly Google Data Studio) to create powerful dashboards and reports. This community connector allows you to visualize your brand’s presence across AI models and prompts in real-time.
The Trakkr Looker Studio Connector provides access to:
Before setting up the connector, you’ll need:
sk_live_
sk_live_
)/get-brands
API endpoint to list all accessible brandsParameter | Description | Example |
---|---|---|
API Key | Your Trakkr API key | sk_live_1234567890abcdef... |
Brand ID | 32-character brand identifier | 0000000000000x000000000000000000 |
Data Type | Choose data to fetch | Brand Scores (Time Series) or Brand List |
Breakdown Options | Optional filtering | By Model , By Prompt , or both |
Date Range | Days to look back (max 90) | 30 |
And then click “Connect”.
Returns daily visibility and presence metrics for your brand.
Available Fields:
Date
- Report date (YYYYMMDD format)Brand ID
- Your brand identifierBrand Name
- Human-readable brand nameVisibility Score
- Brand visibility metric (0-100)Presence Score
- Brand presence percentage (0-100%)Breakdown Options:
Returns all brands accessible with your API key.
Available Fields:
Brand ID
- Brand identifierBrand Name
- Human-readable brand nameField | Type | Description | Range |
---|---|---|---|
visibility | Number | Brand visibility score | 0-100 |
presence | Percent | Brand presence percentage | 0-100% |
Field | Type | Description |
---|---|---|
model | String | AI model name (e.g., “OpenAI”, “Anthropic”) |
model_visibility | Number | Model-specific visibility score |
model_presence | Percent | Model-specific presence percentage |
Field | Type | Description |
---|---|---|
prompt_id | String | Unique prompt identifier |
prompt_text | String | Actual prompt text |
prompt_visibility | Number | Prompt-specific visibility score |
prompt_presence | Percent | Prompt-specific presence percentage |
Field | Type | Description |
---|---|---|
model | String | AI model name |
prompt_text | String | Prompt text |
model_prompt_rank | Number | Average rank in responses (null if not mentioned) |
“API Key is required”
sk_live_
“Brand ID is required”
/get-brands
endpoint to find your brand ID“Date range cannot exceed 90 days”
“API error” responses
Missing Data Points
Inconsistent Scores
Why is my visibility/presence over 100?
This typically occurs when you’ve selected a breakdown option but the data is being aggregated. When you break down by model or prompt, the connector may aggregate scores across multiple data points, which can result in values exceeding 100. To get accurate individual scores:
Why don't I have visibility/presence score with model prompt breakdown?
The model-prompt breakdown doesn’t include visibility and presence scores because these are aggregate metrics that don’t make sense at the individual query level. For each specific model-prompt combination:
Instead, the model-prompt breakdown provides the model_prompt_rank
field, which shows your brand’s average position in responses for that specific combination.
Where do I find my brand ID?
You can find your brand ID in several ways:
Using the API directly:
In your Trakkr dashboard:
From the API documentation:
/get-brands
endpoint to list all accessible brandsBrand IDs are 32-character hexadecimal strings that uniquely identify each brand in the Trakkr system.
How often does the data refresh?
The connector fetches data in real-time, but Trakkr implements caching on the back-end. This means that your data may be up to 180 minutes old. Trakkr implements caching to ensure that your dashboards load as quickly as possible.
Can I use multiple brands in one dashboard?
Currently, the connector is designed to work with one brand per data source. To create a multi-brand dashboard:
What's the difference between visibility and presence scores?
A high visibility score means your brand is frequently mentioned, while a high presence score indicates those mentions are in positive or relevant contexts.
If you encounter issues with the Looker Studio connector: