Analytics5 min read
๐Ÿ“ˆ

Analytics

Read deployment health, signature engagement, social-link clicks, and campaign banner performance.

Overview

Analytics shows how signatures, deployments, social links, and campaigns are performing. Use it to confirm deployment health, identify failed Gmail updates, and understand engagement from links and campaign banners.

app.signaturehq.com/analytics
Analytics dashboard โ€” deployment health, signature engagement, and campaign performance
Analytics dashboard โ€” deployment health, signature engagement, and campaign performance

Deployment health

The deployment trend chart reports successful and failed Gmail signature updates over time. Use failed counts to investigate Google API permission issues, inactive users, or quota problems.

  • Successful deployments confirm users received a rendered signature.
  • Failed deployments should be reviewed from deployment history and worker logs.
  • Template drill-downs show per-template deployment history and error details.

Signature engagement

Signature links are wrapped through a privacy-preserving tracking route when deployed. Social Links include platform metadata so clicks can be grouped by LinkedIn, YouTube, GitHub, X/Twitter, and other supported platforms.

Info

Tracking depends on recipients clicking links or loading tracking pixels in their email client. Some mail clients proxy images, block remote images, or prefetch links, so analytics should be read as directional rather than perfect forensic data.

Campaign analytics

Campaign banners emit a 1ร—1 impression pixel and route banner clicks through the campaign tracking endpoint. Daily stats are rolled up into impressions and clicks so campaign activity appears in both campaign details and the Analytics campaigns section.

app.signaturehq.com/campaigns
Campaign analytics โ€” daily impressions and clicks for deployed signature banners
Campaign analytics โ€” daily impressions and clicks for deployed signature banners

Privacy and data handling

  • IP addresses are SHA-256 hashed before storage.
  • User agents and referrers are stored for troubleshooting and aggregate reporting.
  • Recipient identity is not available unless the click belongs to a known deployed DirectoryUser signature owner.
  • No JavaScript is added to deployed signatures; tracking is done through links and remote image pixels only.