Skip to content

Scan analytics

CSV export and campaign parameters

Export the series as CSV, or read it from the API, when you need the raw rows rather than the dashboard. Campaign parameters on the destination let your own analytics attribute the visit as well.

Steps

  1. Filter to the codes and the period you want before exporting, so the file matches what you were looking at.
  2. Note the time zone the dashboard is using — it decides which day a scan belongs to.
  3. Add campaign parameters to the destination URL if you want the visit attributed in your own web analytics.
  4. Check that the destination does not strip those parameters on its first redirect.

How to check it worked

The row count in the export matches the dashboard for the same filter and period. Your own analytics show the campaign on a test scan.

What usually goes wrong

  • Comparing an export in one time zone against a dashboard in another.
  • Parameters dropped by a redirect on the destination side.
  • Exporting before aggregation has caught up with the last few minutes.
Did this get the job done?

This did not help

Write to us with the platform and version, the steps you took, the result you expected, and the workspace or QR code involved. Mask any secret before you attach anything.

Write to support