If you manage brand tracking for multiple clients, the Tracksuit API lets you bring their brand health data into your own reporting, analytics, and planning tools.
Rather than exporting data client by client each month, you can build a single integration and use it across multiple brands and trackers.
Why agencies use Tracksuit's API
One integration, many brands
A single API key can access every category view (tracker) the account it belongs to has access to, so you build the connection once and reuse it across clients.
A single view across clients
Consolidate multiple brands' brand health into one dashboard or report instead of exporting each separately.
Automated client reporting
Replace manual monthly exports with a feed that refreshes itself, freeing analyst time.
Richer client stories
Combine brand health with the media spend or campaign data you already hold to show how brand investment relates to outcomes.
What you'll need
A technical resource to build and maintain the connection. It's a REST API, so it needs code or a low-code tool.
An admin on the relevant Tracksuit account to generate an API key (see the Authentication guide).
Somewhere for the data to land. The API isn't a native BI connector, so most agencies pull into a data warehouse (e.g. BigQuery, Databricks) and point Looker Studio, Power BI or Tableau at that. See [Connect to a data warehouse].
Use a service account for production integrations. Rather than generating a token under a personal login, create a dedicated user (e.g. data-integrations@yourcompany.com), give it admin access, and generate the token from there. This helps integrations survive staff changes and makes API usage easier to identify.
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
Access and permissions
How you get a key depends on whose Tracksuit account the data sits in.
You've bought Tracksuit yourself. You're the customer, so there are no client permissions to manage. One API key accesses every tracker your agreement covers ā build once, reuse. The API only returns the data your account has permission to access. If you need additional brands, categories, or metrics, reach out to your Brand Champion.
You're accessing a client's Tracksuit account. You'll need their permission, in one of two ways:
They add you as a user with admin rights and you generate the key yourself. This is the recommended approach because nothing sensitive changes hands and API keys are easier to manage and rotate.
The client generates the API key and shares it with you securely using a password manager or secrets store (never email or Slack). Use this as a fallback, as shared keys are harder to rotate and should be replaced if they're ever exposed.
A key only ever sees the brands and trackers its account can access. Run a dedicated service-account token per client (e.g. client-name@youragency.com) so integrations survive staff changes and access stays separated. API keys are valid for 365 days and don't refresh automatically, so set a reminder to rotate them before they expire.
Good practice to follow
Don't sum demographic slices weighting differs per slice; pull the total directly.
Use the 1st of the month for date parameters (wave dates).
Handle pagination via
next_token.Mind the monthly cadence in models. Data updates monthly with each wave, so if you're feeding it into models that run weekly or daily, plan how you'll align it (for example, carrying the monthly value forward). See {{Data freshness and wave timing}}.
Expect differences from other providers. If you already hold brand health data from another source, don't assume the numbers will line up. Methodology, sampling and question wording differ, so absolute values won't match. Compare trends and direction rather than levels, and don't splice the two series into one.
Getting started
Ready to get started? Share the Quick-start guide and Authentication guide with the person building your integration.