This entire product site is authored, validated, and rendered with Sights.See how it works
Menu

The form is content. Its steps are progressive enhancement.

This noindex demo presents one native form as three shorter steps, validates the complete request, and redirects to a success page. A trusted site-wide integration can carry finite first/latest-touch UTM and Google Ads context into the submission; Google click IDs require ad-storage consent. Local review discards values; isolated Cloudflare staging retains synthetic submissions for seven days and can deliver independently tracked email and webhook events.

Environment-selected action

Tell us about a fictional project

Use synthetic information only. Local review discards it; Cloudflare staging retains it briefly while exercising storage and queued delivery.

Demonstration only. Do not submit confidential, sensitive, regulated, payment, health, or time-critical information.

Step 1 of 3

How should we reach you?

Use fictional contact details for this controlled demonstration.

Step 2 of 3

What shape is the project?

Choose the closest options. These answers remain part of one server-validated submission.

When would the fictional project begin?Required

Step 3 of 3

Add context and confirm

Finish with a non-confidential outline and the required acknowledgement.

Keep this fictional and avoid personal or sensitive information.

The trusted action—not page JSON—owns submission behavior. Read the delivery boundary

One accepted record can feed email and Zapier

The queue reloads the authoritative D1 record, then tracks each configured destination independently. Page authors still select only the trusted action name.

  • Secret endpoint

    The complete Catch Hook URL lives in an encrypted Worker secret and is pinned to its declared HTTPS origin.

  • Versioned event

    Zapier receives stable form fields, labels, conversion identity, and explicitly approved attribution in a machine-readable envelope.

  • Independent retries

    A webhook failure can retry without resending an email that was already accepted, and every receiver gets a stable deduplication key.

A lead becomes a conversion only after acceptance

The browser lifecycle gives an approved GTM container enough information to measure a real submission without making analytics part of form delivery.

  • Server-confirmed event

    Rejected requests and honeypot responses cannot emit the form-success conversion event.

  • Stable transaction ID

    One non-identifying request UUID follows storage and measurement so Google Ads can deduplicate a redirect fallback.

  • Consent-gated matching

    Enhanced conversion data is limited to trusted email or telephone mappings and appears only after ad-user-data consent.