Skip to Content
Analytics

Analytics

Audience: Marketers and admins

Analytics in HighAdvocacy answer two practical questions: is this campaign being seen? and is it converting into proof we can use? Both widget and webpage channels feed the same metrics, so you can read a single campaign’s performance without worrying about which surface a submitter came from.

Campaign-level KPIs

  • Impressions: how many times the campaign surface (widget or webpage) was rendered.
  • Unique visitors: distinct submitters who saw the campaign.
  • Repeat visitors: visitors who came back at least once.
  • Average time from impression to submission: how long submitters take from first view to clicking Submit.

These four KPIs sit at the campaign level. If a campaign runs on both the widget and the webpage, they aggregate across the two channels.

Platform-level metrics

For each platform configured on a campaign:

  • Platform selection count: how many submitters picked this platform from the choose-a-platform screen.
  • Submissions created: how many actually submitted on this platform.
  • Verified submissions: how many of those were approved.
  • Rejected submissions: how many were rejected.
  • Verification rate: verified divided by reviewed.

Platform-level numbers help you decide whether a platform is worth keeping enabled. A high selection count but a low submission count suggests the draft step is losing people. A high submission count but a low verification rate suggests proof quality or campaign rules need attention.

What is not in analytics today

  • No channel-split dashboard. Submissions table includes a source marker (Widget or Webpage) and you can filter by it, but there is no dedicated channel-split analytics view.
  • No per-recipient email analytics. Open rates and click rates for status emails are not tracked.
  • No proof-rating filters. The Proof Library does not yet filter or sort by star rating.

These are scope choices for the current version.

Last updated on