Landing pages are coming soon. This page describes the planned feature. For now, capture opt-ins on your own forms and write consent via the Consent API.
Landing pages are form-centric lead-capture experiences—not a generic website builder. The goal is to collect contacts, record consent, and feed campaign flows.

​
Editor

Blocks typically include:
  • Hero — image or color, headline, subline
  • Text — rich text
  • Media — image or gallery
  • Form — drag-and-drop fields (name, email, phone, custom), consent checkbox (preconfigured), validation
  • Video — embeds
  • Countdown — time-limited offers
  • Social proof — testimonials, logos, metrics
  • Footer — legal links (required)

​
Submission flow

  1. Visitor submits the form and confirms consent where required.
  2. Spam controls (rate limits, honeypot/human checks) run before accept.
  3. Contact is created or updated (deduplication via email hash).
  4. Consent record is stored with landing page id, IP hash, and timestamp.
  5. Tags can be applied per form configuration.
  6. Double opt-in email can be sent when enabled.
  7. After submit: thank-you view or campaign start.
  8. Conversion is logged for analytics (including UTM parameters when present).

​
Hosting

  • Hosted URL on the platform subdomain (path per page).
  • Custom domain (CNAME + TLS) where configured.
  • Embed as an iframe on your own site.
  • Rendering is server-side with CDN caching for performance.

Contacts

PII, consent, tags, segments.

Email capabilities

Deliverability and action-based sends.