Skip to content
C CountdownFlow Help Center Sign in

Interpreting campaign performance data

Analyze interactions like opens, clicks, and conversions without overestimating results.

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.

Decoding tracking metrics

Recorded events reflect requests and actions that reached CountdownFlow tracking channels. Email image requests, website visits, clicks, and conversions are distinct signals; do not aggregate them to represent unique customers.

Mail proxies, prefetchers, and security scanners can trigger image or link requests without human interaction. Furthermore, a single user may generate multiple requests. These nuances are critical when evaluating email opens.

Defining conversion events

When enabled, landing pages can record supported CTA clicks as conversions. This tracks a click, not necessarily a completed transaction. An integration-recorded conversion reflects the specific business event sent by your system. Define and document these criteria before comparing campaign performance.

Accessing specific reports

  1. 1Choose your workspace and navigate to Analytics.
  2. 2Apply campaign and date filters to refine the report scope.
  3. 3Analyze metric labels and chart contexts rather than assuming every count equates to an inbox open.
  4. 4Evaluate activity in relation to email send times, updates, and other marketing efforts.
  5. 5For sales analysis, cross-reference data with your store’s confirmed orders while accounting for differences in event definitions.
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)

Why metrics may vary

  • Senders may categorize cached proxy requests differently than the countdown service.
  • Ad blockers, consent preferences, or disabled image settings can interfere with tracking.
  • Date ranges, time zones, or workspace settings may vary across reports.
  • Plan retention limits affect data availability; historical record gaps do not necessarily indicate delivery failures.

Related articles