Analytics and Tracking

Connector

Also called Integration, data connector

The integration that authorises a reporting tool to read a platform's data and maps it into usable fields.

Quick facts: Connector

Category
Analytics and Tracking
Also called
Integration, data connector
Level
Beginner
Affects
Report reliability, available fields, account access
Where to see it
Looker Studio connectors, Google Sheets add-ons, Supermetrics and similar
In this article4
  1. How a connector works
  2. Why connectors matter
  3. Common mistakes with connectors
  4. How to act on it

How a connector works

A connector is the piece of software sitting between a platform and a reporting tool. It does three jobs. It handles authorisation: you sign in to the platform, agree to grant the tool read access, and the tool stores a token rather than your password. It requests data on a schedule through the platform’s interface for developers. And it maps what comes back into the dimensions and metrics you can drag onto a chart.

Connectors come in three broad kinds. Native ones are built by the reporting tool itself and are usually the most reliable. Community ones are written by other people and published for anyone to use, with no promise of support. Paid third-party ones cost money and generally exist because they cover platforms or fields the native connector does not. Which one you choose determines which fields you can ever chart, because a connector that does not expose a field makes that field unavailable no matter that the platform holds it.

Why connectors matter

A connector is a single point of failure sitting under every report built on it. When it stops, nothing shouts. The chart keeps rendering yesterday’s numbers, or quietly draws a flat line, and someone presents it before anyone notices.

The token behind it is the other reason to care. Reports commonly run on the authorisation of whoever set them up. If that was a personal account belonging to a staff member or a contractor, the reporting stops when the account is removed, and the history stored behind it can go with it. This is a routine problem when marketing work moves between agencies or freelancers.

Common mistakes with connectors

Authorising with a personal login is the first and the most expensive to fix. The second is trusting the connector’s field names. A field called conversions in a connector reflects however that platform counted conversions, including its attribution window, and putting it next to a differently defined field from another platform produces a chart that is not comparing anything.

Ignoring failures is the third. Connectors hit request limits, tokens expire, permissions are revoked when someone tidies an account, and platforms change their interfaces. Each of those produces a report that is wrong rather than obviously broken, which is worse. Assuming a free community connector will still be maintained next year is optimistic too.

How to act on it

Authorise through an account the business owns and grant access to individuals on top of it, so people can come and go without the reports dying. Prefer the native connector unless it genuinely lacks something you need.

Before you build anything on a new connection, check its field list against the questions the report must answer, then verify one number against the platform it came from. Put the last refresh date somewhere visible on the report so a stale data source announces itself, and check the connections whenever a platform changes its permissions. Keeping this housekeeping deliberate is most of what makes dashboards and reporting trustworthy over time.

Do and do not

Do

  • Authorise through an account the business owns
  • Check the field list before promising a chart
  • Show the last refresh date on the report

Do not

  • Trust field names to mean the same across platforms
  • Build anything important on an unmaintained community connector
  • Assume a rendering chart means a working connection

Questions people ask about this

Why did my dashboard stop updating?

Usually the connector rather than the report. The stored authorisation may have expired, the account that granted it may have lost access to the platform, the request limit may have been reached, or the platform may have changed something the connector relied on. Reconnect the source, confirm the account still has permission, and check whether the tool logged an error.

Are free connectors safe to use?

Safety and reliability are different questions. Reputable community connectors are generally fine to authorise, but nobody is obliged to maintain them, and one that stops working can take a set of reports with it. For anything a business depends on, prefer a connector the reporting tool builds and supports itself, and keep a note of what you would do if it disappeared.

Can one connector serve several accounts?

Yes. A single connector type is usually used many times over, once for each account or property you point it at, and each of those becomes its own data source in the report. Name them clearly, because a report drawing on several similar-looking sources is easy to misread when only the tool's default labels are showing.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.