FAQs

​

Why do my metrics and breakdowns change when I pick a different etracker report?

Each etracker data source binds to a single report, and the available metrics and breakdowns come from that report’s own column definitions. When a report is selected, the connector reads its columns from etracker: attribute-typed columns become breakdowns, and the remaining columns become metrics. A different report exposes a different column list, so the metric and breakdown options shift accordingly. To report on a metric or breakdown that a report does not expose, the choices are to adjust the report inside etracker so its column list includes that field, or to select a report that already contains it. The connector surfaces whatever columns the chosen report defines and nothing beyond that. For the full field model, see the etracker data reference.

​

Why can’t I split an etracker report by day, week, or month?

Date breakdowns are surfaced only when the selected report includes a date column with the identifier utm_date. When that column is present, the connector adds day, week, and month groupings. When it is absent, the report returns aggregate rows for the requested range and cannot be time-sliced. The fix is to configure the report in etracker so it includes the utm_date date column, then reconnect or select that report. Reports built without a date column will not offer daily, weekly, or monthly splits no matter how the widget is configured.

​

Why did my etracker data source stop returning data after the token was rotated?

Authentication uses a single long-lived access token entered at connection setup and sent to etracker on every request as the X-ET-Token header. The connector does not rotate, renew, or refresh this token on its own. When the token is regenerated or revoked in etracker’s own interface, the stored value no longer matches, and every subsequent request fails until the connection is updated. To restore data, open the data source connection settings and re-enter the current token so it is saved again. After the token is re-saved, requests authenticate normally. For the connection steps, see How to connect etracker to Adriel.

​

How do I report on more than one etracker report on the same dashboard?

Because a data source binds to one report, covering several reports — a site overview and a campaign report, for example — means creating a separate etracker data source for each report. Each connects with its own report selection. Once connected, widgets can pull from multiple etracker data sources on the same dashboard, so several reports can sit side by side. Metrics that share the same meaning across reports can be placed in adjacent widgets for comparison, though figures are not merged across reports automatically.

​

Why does etracker data sometimes lag on dashboards with many widgets?

etracker enforces a shared rate limit of 5 requests per 30-minute window across the connector’s calls. A dashboard that fires many etracker requests at once — a large number of widgets, or several etracker data sources refreshed together — can reach that ceiling, and the remaining requests queue until the window frees up. This appears as some widgets loading later than others rather than as an error. Keeping the number of simultaneous etracker requests modest reduces queuing. If a widget consistently returns an empty result or an error instead of loading late, and the report, token, and breakdown settings are all correct, email support@adriel.com with the affected dashboard URL and the report involved.

​

Related