Skip to main content

​
Introduction

etracker is a German web-analytics platform with a strong focus on GDPR-compliant, cookieless tracking for European audiences. It captures visits, visitors, page views, sessions, and conversion events at the site level, and exposes that data through a REST reporting API. The connector reads from etracker’s v7 report API and surfaces both the report catalogue and per-report metadata, so the available metrics, breakdowns, and date-grouping support reflect what the etracker account itself defines. Reports are configured inside etracker; this connector retrieves their results. One data source binds to a single etracker report, so the exact metric and breakdown list depends on the report selected. As an analytics connector, session, event, and breakdown data are standardized so widgets can aggregate alongside ad-platform sources without additional configuration. To connect this data source, see How to connect etracker to Adriel.

​
Data refresh strategy

​
Architecture data

The report catalogue and each report’s metadata — the available columns, including whether the utm_date date column is present — are fetched from etracker on demand at query time. There is no nightly architecture sync. Metadata responses are cached per data source for roughly 30 minutes, so a newly changed report definition can take up to that long to appear.

​
Reports data

etracker is a real-time connector. Report data is fetched from https://ws.etracker.com/api/v7/report on demand each time the dashboard is loaded, so figures reflect whatever etracker has currently processed. There is no daily cache job and no scheduled sync window — freshness is bounded only by etracker’s own data-processing lag.

​
Architecture levels

Account → Site/Project → Report → Row A single etracker report ID is configured per data source. To query a different report — campaign performance versus site overview, for example — a separate data source is created.

​
Metrics

How to read the columnsetracker’s metric catalogue is driven by the selected report’s definition. Each report’s columns are fetched from the {reportId}/metaData endpoint, and the non-attribute columns become that data source’s metrics. The fields below are the standard analytics metrics most etracker reports expose; the actual list per data source depends on the chosen report.Italic text in the API Key column indicates that the literal key is the report’s own column identifier, which varies per report. Column data types are mapped from the report metadata: float and integer become Number, percent becomes Percentage, staytime becomes Duration, and any unrecognized type falls back to Text.Data type vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.

​
Users & sessions

​
Engagement

​
Events & conversions

​
Ecommerce

​
Breakdowns

How to read the columnsCode style like day is the literal breakdown key sent to the etracker API. Italic text indicates that the literal key is the report’s own column identifier, which varies per report.

​
Date

​
Report attributes

​
Limitations

Based on the current connector, etracker has:
  • Report-bound metrics and breakdowns — each data source binds to a single report ID, and its available metrics and breakdowns reflect that report’s column list. Querying a different report requires a new data source.
  • Date breakdowns require a utm_date column — day, week, and month groupings are surfaced only when the report’s metadata declares a column with id === 'utm_date'. Reports without that column cannot be time-sliced and return aggregate rows only.
  • A static access token with no refresh — authentication is a single long-lived token entered at connection setup and sent as the X-ET-Token header. There is no rotation, expiry handling, or OAuth refresh inside the connector. Tokens are rotated in etracker’s own UI; a revoked token fails every subsequent request until the connection is re-saved.
  • A rate limit of 5 requests per 30 minutes — this limit is shared across all requests from the connector, so high-frequency refresh schedules may experience queuing delays.
  • API version pinned to v7 — all requests target https://ws.etracker.com/api/v7/report. New etracker API versions require a connector update before they can be used.

​
API references

  • etracker Reporting API v7 — base endpoint https://ws.etracker.com/api/v7/report
  • GET /api/v7/report — lists the available reports (IDs and names) for the account
  • GET {reportId}/metaData — returns a report’s column definitions (metrics and attribute breakdowns)
  • GET {reportId}/data — returns a report’s result rows for the requested range and breakdown

​
See also