Analytics & tracking

Drop a Google Analytics (GA4), Google Tag Manager, or Meta Pixel ID into the config and tracking works on every page. The Content-Security-Policy opens only for the providers you enable; blank IDs load nothing and the CSP stays locked.

If you are building a front end

This one is configuration and UI rather than an endpoint you call — it ships with the template and turns on from config or the dashboard.

Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.

How to turn it on: site.config.ts -> analytics.googleAnalyticsId / googleTagManagerId / metaPixelId.
Who can use it: none (config-only); CSP auto-widens per configured provider.
Where it lives: every page (root layout)

See it in context

Marketing & lead capture — the full walkthrough, step by step: Landing pages, giveaways, quizzes, and attribution — clicks become tracked leads.

Machine-readable

This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.