Skip to content
CountdownFlow Help Sign in

Filter reports and export available data

Create a useful reporting workflow and understand plan-based history limits.

2 min read

Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.

Prepare the report

  1. 1Check the workspace and campaign name before exporting.
  2. 2Choose the relevant reporting period using the screen’s available filters.
  3. 3Confirm which events and totals the report includes.
  4. 4If an export option is available and permitted by your plan/role, download the filtered data and verify the first rows before sharing it.
Analytics screen and its available reporting controls in the demo workspace
In the application 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)

Interpret missing history

A history quota limits the period you can access. It is not necessarily a retroactive deletion of older records. Check the workspace’s current allowance instead of assuming a campaign never received activity because older events are not visible.

Share responsibly

Exports may include identifiers and event details. Share only what recipients need, keep workspace data separate and do not combine client reports without authorization. Remove test traffic where your analysis requires it, but do not edit the live campaign simply to make a report look cleaner.

A repeatable reporting habit

Record the chosen date range, workspace and metric definitions alongside every report. This makes month-to-month comparisons interpretable when a plan, tracking method or conversion definition changes.

Related articles