You can skip a lead capture screen when an email address is already available in the experience. This reduces friction, shortens the experience path, and supports progressive profiling by collecting only missing data.
Before you begin
Confirm that the experience can receive an email address before the participant reaches the lead capture screen.
Make sure the incoming value maps to the same attribute used by the lead capture field.
Use a consistent attribute name, such as email, across your embed, URL parameters, and integrations.
1. Pass the email as a hidden attribute
You’ll first need to ensure the experience has access to the user’s email address before they hit the lead capture screen.
Options:
Via URL parameter
Append [email protected] to the URL of the experience.
Via embedded script / SDK
If embedded on-site, you can pre-populate the email attribute using BlueConic Experiences embed options.
Via integration with a CDP or ESP
Use a connected platform (like BlueConic or Klaviyo) to pass the known email as a BlueConic Experience attribute.
2. Create an Attribute called “Email”
Go to the Attributes Tab.
Create a Text attribute called email (or use your existing lead capture field)
3. Set conditional logic to skip the lead capture screen
In the Builder tab, do the following:
Click on the Lead Capture screen (or the screen collecting the email).
Add logic conditions at the top of the screen:
“Only show this screen IF email is empty or is not known.”
This means if the experience already has a value for email, the screen will be skipped automatically.
Logic Example:
Show this screen only if:
email → is empty
This logic is evaluated before the screen is rendered.
4. Test Your Experience
Before going live:
Test the URL with
[email protected]Make sure the lead capture screen is skipped.
Test a version without the email to confirm the screen appears as expected.
5. Optional: Use Outcomes or Redirects
If your lead capture gates specific outcomes or redirect behavior, make sure the logic still functions as expected for known users:
Use branching logic based on whether the email is known or unknown.
You can also set alternate “thank you” screens for known users.
Tip: If you're collecting additional information beyond email (like name, preferences, etc.), use progressive profiling by skipping fields that are already known and only asking for what’s missing.