Export click data

For a portable account archive, open Dashboard → Settings → Your data and download the JSON export. It contains your links, campaigns, domains, folders, tags, UTM presets, and conversion events.

For campaign results, open Shared campaigns, choose a 7-, 30-, 90-day, or all-time window, and click Export CSV. Each row includes the destination, total clicks, human visits, bots, conversions, and period. The current public API lists links and records conversions; raw visit-level export is not exposed through account API keys.

Choose the export for the question

The JSON account archive is designed for portability and account-rights requests. It preserves structured records that are not naturally tabular: link inventory, campaign names, verified-domain state, organization labels, reusable UTM naming presets, and the conversion metadata your backend supplied. Keep the original file if you are closing an account or moving governance records into another system.

Campaign CSV is the practical reporting format. A spreadsheet, finance tool, or BI importer can read one row per link without unpacking nested JSON. Pick the reporting window before download; the period_days column records whether the file represents seven, thirty, ninety, or all-time results. Conversion counts follow the same window, which keeps the click-to-outcome comparison coherent.

Read the columns correctly

clicks includes automated fetches as well as people. human_visits is the cleaner numerator for audience response, while bots explains preview generators and crawlers that can otherwise make a new campaign look active before anyone has seen it. conversions contains outcomes explicitly posted by your system; GoTo.now does not guess a purchase from a page view.

CSV uses UTF-8 so international destinations remain readable. Dates in account JSON are serialized in the database's UTC representation. Treat destinations as untrusted text when importing: spreadsheet software may interpret a value beginning with =, +, -, or @ as a formula, so security-sensitive workflows should use an importer that disables formula evaluation.

Build a repeatable reporting routine

Use a stable campaign per launch, client, or placement group. Record a conversion with an externalId such as the order identifier so retrying the event cannot inflate the outcome count. At the end of each reporting period, export the same window, store the untouched file with its generation date, and perform derived calculations in a separate workbook or warehouse table.

Shared web reports solve a different problem: they are convenient, read-only views for a client or teammate and can be revoked or allowed to expire. CSV and JSON are owned copies. If data should disappear when access is revoked, send the report URL; if the recipient needs a durable record, send the export intentionally.