If you’re the technical team member setting up the integration, get started with the Quick-start guide and the Authentication guide.
Why marketers use the Tracksuit API
Brand tracking data gets more useful the closer it sits to where decisions happen. The Tracksuit API helps your technical team connect Tracksuit to the reporting, analytics, and business intelligence tools your organization already uses.
Rather than manually exporting brand health data from the dashboard each month, the API automatically keeps it flowing into your existing reporting workflows. That makes it easier to bring brand health into the same reports, dashboards, and models as your media, customer, and commercial data, helping your team understand the role brand plays in business performance.
How marketers are using it
Once connected, marketers are using the API to:
Connect brand health to commercial outcomes
Combine brand health metrics with sales or spend data to understand how brand investment relates to business performance.
Automate recurring reporting
Replace manual exports with a direct data feed into your existing dashboards and reporting workflows.
Feed models
Incorporate brand health data into marketing mix models, forecasting frameworks, and other advanced analytics.
For example, customers are already using the API to combine sales and brand data in board-level reporting, automate executive updates, power household penetration models, and support audience and channel planning.
What data is available
Funnel metrics: awareness, consideration, preference and usage, over time
Demographics & cross-demographics: slice by age, gender, region, persona and more, including combinations
Multi-dashboard views: pull all trackers available to you into one view
Competitor brands in your category
Custom rolling average: anywhere from 1 to 12 months (the 1-month data point isn't available in the dashboard itself)
Statements: how your brand scores on brand imagery statements (the associations and attributes people link to your brand)
Conversion: conversion rates between funnel stages (e.g. how many of those aware of you go on to consider you)
Category profile: the demographic make-up behind a chosen metric, so you can see who sits at each stage of the funnel
Media consumption: which channels your category's audience consumes content on
The API does not currently include: Imagery data, Training Ground modules
What to know before you start
Like the Tracksuit dashboard, API data refreshes monthly with each survey wave.
While the API is ultimately designed to help marketers get more value from their brand health data, the integration itself is usually set up by a technical person, such as your data team or agency.
Who does what?
👩💻 Technical team
Builds and maintains the API integration, manages authentication, and connects Tracksuit data into your reporting environment.
🎯 The marketer is ultimately who the API is for
Defines the business questions the integration should answer, decides how brand health data will be used, and turns the insights into action through reporting, planning, and decision-making.
Setup is self-serve for your technical team, and a single API key provides access to all the brands and trackers you can already access in Tracksuit.
How to brief your technical team
Ready to build?
You don't need to understand the code. Your job is to tell them what you want the data to do and where you want it to live, they'll handle the connection.
What to tell them
What to tell them
What it is: a read-only REST API that serves the same brand health data as the Tracksuit dashboard (funnel metrics, statements, conversion, demographics, competitors, media consumption).
Where you want it to land: e.g. Power BI or Tableau, a data warehouse (Snowflake, BigQuery, Databricks), Google Sheets, or a marketing mix model.
What you want to do with it: e.g. an automated monthly report, a board tracker combining brand and sales data, or a feed into a model.
How fresh it needs to be: the data only updates monthly with each survey wave, so a monthly refresh is enough, no need to build anything real-time.
It's not a native BI connector. The API doesn't plug straight into Power BI, Tableau or Looker out of the box. In most setups they'll pull the data into a data warehouse (Snowflake, BigQuery, Databricks) or another store first, then point the BI tool at that.
Questions to ask them
Questions to ask them
Where will the data live, and how will we see it? (A dashboard, a sheet, a warehouse table?)
Will it run automatically, on a monthly schedule? The data only changes monthly with each wave, so there's nothing to gain from pulling more often, just check it's automated (not a manual job) and set to refresh once the new wave lands.
Who owns the API key, and how is it stored securely? (It should live in a password manager or secrets store — never in email or Slack.)
Who's responsible for rotating it? Tokens last 365 days with no auto-refresh, so someone needs a reminder to regenerate before it expires.
Are we using a service account rather than a personal login? This keeps the integration alive if someone leaves.
Point them to the technical guides
Point them to the technical guides
Once they're ready to build, send your implementer to:
Quick-start guide from key to first successful call
How to authenticate the Tracksuit API generating and storing the key (needs admin access)
Endpoint reference every endpoint, parameter and response field
Three things to make sure they get right
Three things to make sure they get right
Don't sum demographic slices. The data is weighted per slice, so adding age groups (or regions) together won't equal the total. Pull totals directly. See Why API numbers may differ from the dashboard.
Use the 1st of the month for date ranges, they map to survey waves. And set smoothing to 3 months if the numbers need to match what you see in the dashboard.
Handle pagination. Large pulls come back in pages via next_token — if that's skipped, you'll silently only get the first page. See the Pagination guide.
How big a job is this?
Setting up a fresh integration is typically a small piece of work, and a single key gives access to every tracker you can already see in Tracksuit. If they're migrating an existing v1 integration, that's roughly a 1–2 day job. See the Migration guide.
If you don't have a data team or agency, you can still connect simple feeds yourself with Connect via low-code tools.