Skip to main content

Integrations: how linking works

The anatomy of every integration — where keys go, what's stored encrypted, how consent works, and how to verify a link is live.

Updated 2026-07-17

Integrations live in the Widgets & Integrations drawer: open your project in the Studio, click ⋯ → Widgets, and browse by category. Each widget card carries its own setup guide — expand the card to see the exact steps for that service.

02The linking pattern

  1. Create the thing on the provider's side (a GA4 property, a reCAPTCHA site, a Razorpay key pair, a Calendly event).
  2. Copy the public identifier — a measurement ID, site key, link — into the widget's fields.
  3. If the service has a SECRET key, paste it into the secret field: secrets are stored encrypted, never appear in your site's code, and are used only server-side.
  4. Save & enable, then Publish. Widgets ship with the published site, so the link goes live with your next publish.
  5. Verify on the live site — most providers have a realtime or test view that shows your first hit within a minute.
TipTags governed by cookie consent (analytics and marketing) only load after a visitor accepts the banner — so verify them on the live site after accepting, not in the Studio preview.

03What each field type means

  • Plain fields (IDs, links, phone numbers) are validated as you type and stored in your site's spec.
  • Secret fields show “Saved ✓” once stored — the value itself never comes back to the browser.
  • Consent-gated widgets automatically switch your site to the opt-in cookie banner.
  • Plan-gated widgets show the required plan on the card; upgrading unlocks them instantly.