Skip to main content

Tracksuit API overview

An overview of Tracksuit's API: what's included, common use cases, and how to get started.

🧢 Coach T’s Recap

We're excited to introduce the next generation of the Tracksuit API.

Brand health data is most valuable when it lives alongside the other information your team uses to make decisions.

The Tracksuit API helps you connect your Tracksuit data to the reporting, analytics, and business intelligence tools your team already uses, making it easier to automate reporting and combine brand health with the metrics that matter most to your business.

Here's an overview of what's included, along with some of the ways our early customers and partners are already using it.

What is the Tracksuit API?

The Tracksuit Public API gives you programmatic access to the same brand health data that powers your Tracksuit dashboard.

This allows your team to automatically send Tracksuit data into the tools where you already work, including BI dashboards (Power BI, Tableau), data warehouses (Snowflake, Databricks), analytics environments, and marketing mix models.

Rather than manually exporting data from the dashboard, the API enables brand health data to flow directly into your reporting, analytics, and decision-making workflows.


What's included?

  • 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 can you do with Tracksuit's API?

Here's a snapshot of how our early access customers and partners are already putting Tracksuit's API to work:

  • Build executive dashboards

  • Connect brand health with sales, media, and commercial data

  • Automate recurring reporting

  • Feed marketing mix models and forecasting

  • Report across multiple brands or clients

  • Power internal analytics and business intelligence


Is the API right for you?

The Tracksuit API is designed for teams that want to bring their brand health data into their existing reporting, analytics, or business intelligence workflows.

It's a good fit if you:

  • Use tools like Power BI, Tableau, Looker Studio, Snowflake, BigQuery, or Databricks.

  • Have a data team, analyst, agency, or technical partner who can build and maintain the integration.

  • Want to automate recurring reporting instead of manually exporting CSVs

  • Want to combine brand health with sales, marketing, customer, or commercial data

  • Need to report across multiple brands, trackers, or clients

If you primarily explore insights in Tracksuit or only need occasional exports, the dashboard and CSV exports may be all you need.


Will the API integrate with my tools?

The Tracksuit API isn't a plug-and-play connector. It's a REST API that can be integrated with a wide range of reporting, analytics, and business intelligence platforms.


Whether you connect directly or via a data warehouse depends on whether your tools support REST APIs. Both approaches require technical resources to build and maintain the integration.


How to get started

Whether you're exploring what's possible or you're ready to build, you'll find everything you need here. Browse the guides below to get up and running.

Get connected

Understand the data

Connect with your tools

Build reliably

Migrating an existing integration

Did this answer your question?