Skip to content
C CountdownFlow Help Center Sign in

Exporting and filtering performance reports

Generate and export historical data while maintaining necessary context for your team.

2 min read

Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.

Generating reports

  1. 1Verify the workspace and campaign selection.
  2. 2Set the reporting window using the date controls.
  3. 3Examine the event types and aggregated totals included in the report.
  4. 4If your plan and role permit, download the filtered data and review sample rows prior to sharing.
Analytics screen and its available reporting controls in the demo workspace
Check the workspace and reporting period before interpreting activity. Image requests, clicks and conversions are different signals. View full-size screenshot (opens in a new tab)

Addressing gaps in history

Historical quotas restrict the time period you can access, rather than triggering retroactive deletions. Verify your workspace allowance before concluding a campaign lacked activity simply because older events are hidden.

Sharing reporting data

Exports often contain sensitive identifiers and event details. Share data only with authorized recipients, maintain workspace separation, and do not merge client reports without permission. Filter out test traffic if required for analysis, but avoid altering live campaigns solely for reporting aesthetics.

Establishing a routine for tracking

Maintain records of the date range, workspace, and metric definitions used for every report. This ensures that month-to-month comparisons remain valid if tracking methods, plans, or conversion definitions are updated.

Related articles