Skip to content
CountdownFlow Help Sign in

Understand countdown analytics and conversions

Read activity reports without confusing image requests, visitors, clicks and completed purchases.

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.

What an event means

Recorded events describe requests and actions that reached CountdownFlow’s tracking channels. An email image request, website visit, click and conversion are different signals. Do not add them together and label the total as unique customers.

Mail proxies, prefetchers and security scanners can request images or links without a human interaction. Repeated requests can also come from one person. These limits are especially important when evaluating email opens.

Conversion is defined by your setup

A landing page can record supported CTA clicks as conversions when you enable that option. That measures interest, not necessarily a completed payment. An integration-recorded conversion should represent the business event you explicitly send. Agree on that definition before comparing campaigns.

Read the right report

  1. 1Select the intended workspace and open Analytics.
  2. 2Use the available campaign and date filters to narrow the report.
  3. 3Review the metric labels and chart/table context rather than treating every count as an inbox open.
  4. 4Compare activity against email send time, publishing changes and other marketing activity.
  5. 5For sales decisions, compare with your store’s confirmed orders and account for the different definitions.
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)

Why numbers can differ

  • A sender may count a cached proxy request differently from the countdown service.
  • Ad blockers, consent settings or disabled images can prevent tracking.
  • The selected date range, timezone or workspace may differ between reports.
  • Plan retention can limit accessible history. Older records are not automatically evidence of a delivery failure.

Related articles

Add a countdown to an email newsletterEmbed the generated HTML, choose PNG or GIF, and test real inbox behavior. Build, save and publish a hosted landing pageUse the block editor without confusing the saved draft with the version customers can see. Filter reports and export available dataCreate a useful reporting workflow and understand plan-based history limits.