Step question
Design preview — final page may vary. Use Live preview to see the built site.
Pixel fires a server-side beacon when the page loads. No redirect, no exposed tracking domain.
Use {click_id}, {sub1}–{sub5}, {source}, {medium} tokens.
Capture UTM parameters from the landing URL and include them with leads.
Generates a certificate proving consent was given. Critical for TCPA compliance.
From your Google Ads conversion action. Different from GTM ID.
The label paired with your conversion ID.
When enabled, each step can have variant B overrides. Edit a step to configure its B variant — steps without B overrides will serve the A version.
Compliance
This exact text appears in the page footer. Write the actual disclaimer your visitors will read — not a list of requirements.
The compliance review will check this against your vertical's regulations.
Do not include real personal information in this field. This text is sent to AI models for compliance review.
The full privacy policy text for the privacy page. If left blank, a compliant default will be generated based on your vertical and form fields.
Comma-separated state abbreviations where the offer is not available
Widget
Replace or supplement the native lead capture form with an embeddable widget from a partner network.
Notifications
Optional. Receives a POST with minimal lead data (name, qualifier, UTM) on each submission.
Asset Reference
Config Output
Read-only view of what will be sent to the build engine. Useful for debugging or sharing the config with your team.
Steps
- Select a path to see its steps.