← All posts

What's New: Secure Analytics Tracking, Python Version Fix

Analytics tracking redesigned for security — enter tracking IDs instead of raw code. Supports Google Analytics, Google Tag Manager, Microsoft Clarity, and Meta Pixel. Plus a deployment fix for Python 3.13.

Two updates today: a security-focused redesign of the analytics tracking feature, and a deployment fix.

Analytics & Tracking (Beta)

The tracking code feature has been completely redesigned for security. Previously, readers pasted raw HTML/JavaScript snippets into a textarea — this worked but carried the risk of malicious code injection.

Now, instead of pasting code, you enter just your tracking ID for each supported provider:

  • Google Analytics (GA4) — enter your Measurement ID (e.g., G-ABC123DEF4)
  • Google Tag Manager — enter your Container ID (e.g., GTM-ABCDEF)
  • Microsoft Clarity — enter your Project ID (e.g., abc123def4)
  • Meta Pixel — enter your Pixel ID (e.g., 1234567890123456)

StarAlign generates the correct tracking scripts server-side using your IDs. Each ID is validated before saving — only properly formatted IDs are accepted.

Security Improvements

The tracking scripts are protected with a strict Content Security Policy (CSP) that uses per-request nonces to authorize only the scripts StarAlign generates. This means:

  • No unauthorized scripts can run on your booking pages
  • Only the analytics domains you actually use are allowlisted (e.g., if you only use Google Analytics, Facebook and Clarity domains are not permitted)
  • Inline event handlers have been removed from the booking page in favor of CSP-compliant alternatives
  • Plugin-based attacks (Flash, Java applets) are explicitly blocked

You'll find the new tracking fields in Settings > Booking Setup under the Analytics & Tracking section (marked as Beta while we gather feedback).

If you previously had tracking code configured, your IDs have been automatically extracted and migrated to the new format. If you were using a provider we don't yet support, you'll need to wait until we add it — let us know which providers you'd like to see.

Deployment Fix

A Python 3.13.12 build issue was causing deploys to fail. We've pinned the runtime to Python 3.13.11 until the upstream fix is released.


This is live now. If you run into any issues with the new tracking setup, reach out and we'll help you get configured.