👉 Ready to join the Beta?
Places are limited. Book an onboarding call now or contact your Brand Champion/Partner Manager.
What you'll need:
A technical contact to build the integration eg. developer, data engineer, low-code analyst
Somewhere to send the data e.g. a data warehouse or custom pipeline that can consume a REST API
💬 Beta feedback form: Share feedback, flag blockers, or request data types at any point during the Beta.
API v2 at a glance
The Tracksuit API v2 provides a direct, secure connection to your Tracksuit brand health data. Once connected, data updates flow automatically into your existing reporting, warehousing, or modelling setup.
Data can be filtered by brand, category, time period, and demographic. New data types, including statements, conversion metrics, media consumption, and monthly granularity, are added at each phase of the beta. See the timeline below for details.
What Beta partners get
First access to new data types
Beta partners are the first to access data that isn't available anywhere else yet: statements, conversion metrics, media consumption, sources of awareness, and monthly granularity. All before general release.Build brand into your existing models
Use the API to connect Tracksuit data to your MMM, attribution, or BI setup. You'll need a technical resource to build the integration, but once connected, automated feeds replace manual exports for good.One API, your full portfolio
Every brand, competitor and category in your subscription through a single authenticated connection. Same demographic depth as your dashboard, with more customisation.Direct input into what ships
You'll work closely with a dedicated Product Manager, and your feedback will directly shape the API product roadmap.
What's coming and when
Phase | When | What you get | What we need from you |
Onboarding | Late April - May | API keys, docs, 30-min kickoff call with the product team | Schedule and join your onboarding call |
Phase 1 | May | Funnel metrics, demographic breakdowns, monthly granularity, rolling averages, sample sizes | Test the endpoints against your use case |
Phase 2 | June | Statements, conversion metrics, category profiles | 30-min check-in call + short survey |
Phase 3 | July | Media consumption, sources of awareness, brand activity recall | 30-min check-in call |
Wrap-up | August | Beta programme concludes, with a migration path provided | Final 30-min call + short survey |
Timelines may shift based on learnings.
Before you join
You’ll need
A technical contact: Someone comfortable connecting to a REST API (developer, data engineer, or low-code analyst) to own the integration. We'll support them with technical documentation and onboarding to assist with implementation.
Somewhere to put the data: A chosen tool that can consume JSON from a REST API. For example: BigQuery, Snowflake, or a custom Python/R pipeline. If you're unsure whether your setup is compatible, we're happy to help you work that out.
Common use cases
BI + Dashboard
Brand health alongside media spend, sales and commercial KPIs. One picture, not a separate tab.Agency / Multi-Client
One API connection across your entire portfolio. Data flows into BigQuery, Looker, Power BI or client dashboards automatically.Marketing Mix Modelling
Month-on-month data feeds directly into MMM platforms. No manual exports or reformatting.
Executive Reporting
Automate the data pipeline behind leadership reporting. Your team focuses on insight, not assembly.
Technical overview
For the team building the integration.
Technical details
Technical details
Getting Started
The Tracksuit API v2 is a REST API returning JSON. Authenticate with a Bearer token, call the endpoints below, and parse the response into your pipeline or BI tool. Your API key and base URL will be provided during your onboarding call.
Authentication
Include your API key as a Bearer token in the Authorization header on every request:
Authorization: Bearer {your_api_key}
Each key is scoped to a single subscription and gives access to all brands and categories within it.
Endpoints
GET /v2/category-views— List all category views (survey scopes) you have access to.GET /v2/category-views/{id}— Metadata and available filter options for a category view.GET /v2/category-views/{id}/brands— All brands tracked within a category view.GET /v2/category-views/{id}/funnel— Funnel metrics (e.g. awareness, consideration, preference).GET /v2/category-views/{id}/conversion— Movement between funnel stages.GET /v2/category-views/{id}/statements— Statement performance and importance (Phase 2+).GET /v2/category-views/{id}/media-consumption— Media channel consumption (Phase 3+).
Filtering
All data endpoints accept query parameters:
brand_ids— Array of brand IDs to filter results.start_period/end_period— Date range in ISO 8601 format. Start is inclusive, end is exclusive (e.g.2025-01-01T00:00Z).metrics— Filter to specific metric types.channels— Filter to specific media channels (media-consumption endpoint).filters— Demographic dimension filters (e.g. age, gender).smoothing— Rolling average window, e.g."3mo"or"1y". Defaults to"3mo".
Pagination
Responses use token-based pagination. Include page_size to set results per page. Each response includes a nextToken field — pass this as the next_token query parameter to fetch the next page. When nextToken is absent, you've reached the end.
Example Response
{ "category": { "id": "0", "name": "Energy Drinks" },
"geography": { "id": "0", "name": "New Zealand" },
"rows": [
{
"periodStart": "2026-03-05T00:00Z",
"brand": { "id": "1", "name": "BrandName" },
"demographic": { "type": "age", "value": "18 - 24" },
"metric": "UNPROMPTED_AWARENESS",
"value": {
"percent": 0.8,
"weight": 55.7,
"baseWeight": 304
},
"sampleSizeQuality": "INSUFFICIENT"
}
],
"nextToken": "/AMRWQj1soHW/n0RZfUGaj9u..."
}Dates
All dates use ISO 8601 format (e.g. 2026-03-05T00:00Z).
Error Handling
The API uses standard HTTP status codes:
400— Invalid request. The response includes adetailsarray describing each validation issue.401— Missing or invalid API key.403— Valid key, but not authorised for this resource.404— Resource not found.429— Rate limit exceeded. The response includes aretry_aftervalue — wait this duration before retrying.500/503/504— Server-side errors. Retry with backoff.
All error responses return a JSON body with code and message fields.
Rate Limiting
Limits are applied per subscription — all API keys under the same subscription share a single allowance. If you exceed the limit, the API returns 429 with a retry_after value in the response body. Specific rate limit thresholds will be shared during onboarding.
Compatibility
The API works with any platform that can make HTTP requests and parse JSON — including Looker, Power BI, Tableau, BigQuery, Snowflake, dbt, Python, R, and more.
📘 More detail coming at onboarding
During your onboarding call, you'll receive your API key, base URL, full endpoint documentation, rate limit thresholds, and data refresh schedule. As the Beta progresses, we'll continue to expand this reference with additional endpoints, field definitions, and code examples.
FAQ
What data is available?
What data is available?
The same brands, categories and competitors in your Tracksuit dashboard. New data types, like statements, conversion metrics, and media consumption, are added at each phase of the beta, so what's available grows over time. See the timeline above for details.
Is month-on-month or Statements data available?
Is month-on-month or Statements data available?
Yes. You can access monthly granularity from Phase 1, and Statements data from Phase 2. These are some of the biggest differences from the current API.
How does this relate to the existing Tracksuit API?
How does this relate to the existing Tracksuit API?
API v2 is a new, more complete API. It includes data types not available in v1 (statements, conversion, media consumption, month-on-month) and a more stable contract. We recommend all new integrations use v2.
Do you offer pre-built connectors (Fivetran, etc.)?
Do you offer pre-built connectors (Fivetran, etc.)?
Not yet, the beta is a REST API, which gives you full flexibility over how you connect. Pre-built connectors (e.g. Fivetran, PowerBI) are on the roadmap for later in 2026, and beta partner feedback will help us prioritise which ones to build first.
How much time does the beta take?
How much time does the beta take?
The main investment is your team's time building the initial integration. Once this is built, you will just need around 30 minutes per month to join a feedback call with our product team, plus occasional async feedback.
Can agencies use this for multiple clients?
Can agencies use this for multiple clients?
Yes. One integration surfaces data across your entire subscription portfolio.
Will the API change during beta?
Will the API change during beta?
Yes. Ongoing changes and releases are expected, that's the nature of a co-build. We'll communicate changes proactively and support migration.
Can I use the existing API (v1) and v2 at the same time?
Can I use the existing API (v1) and v2 at the same time?
Yes. Both APIs can be used concurrently, they operate independently and one won't interfere with the other. However, we'd recommend building any new integrations against v2, as it covers a broader set of data types and will be the actively maintained API going forward. If you have an existing v1 integration, there's no rush to migrate during the beta, but we'd suggest planning to move over once v2 reaches general availability.