Smart Rules just got even smarter. You can now apply Smart Rule logic to individual modules within a landing page, so specific buttons, links, or CTAs can redirect dynamically based on specific conditions (like device type, location, time, or returning vs. new visitors). This unlocks more precise personalization and improved consumer experiences.
What’s new
Before: Previously, our Smart Rules capabilities were set at the page level, so the rule applied to the entire landing page experience, not individual modules.
Now: Smart Rules can now be applied at the module level, so each component of a landing page can have its own smart rule conditions and destination logic—perfect for multi-step journeys and personalization within a single page.
Why it matters
1) Granular Customization
Apply Smart Rules to individual components within a page to create highly customized, precise user journeys.
2) Streamlined Workflows
Build your experience once, then make it dynamic at the module level, eliminating the need to duplicate and manage multiple full pages.
3) Frictionless Re-engagement
Intercept returning users to hide completed tasks and surface the next high-value action based on their conversion history.
Common use cases
Device-specific CTAs: iOS users go to the App Store and Android users go to Google Play, both from the same module.
Regional routing: Send users to the nearest store page or local offer based on location.
Time-based experiences: Promote different CTAs during an event window vs. after it ends.
Sweepstakes reengagement: If someone already submitted your embedded form, use a module-level Smart Rule to hide or replace the form module on their next visit with an “Already entered” message or a new CTA.
How it works
Each module now supports its own decision logic with rules that determine where that module redirects. That means:
Your landing page stays consistent and branded.
Only the relevant module changes behavior based on the visitor’s context.
Set up Smart Rules on a module
Open the Conversion Flow you want to update and click Edit Flow.
Decide which element you want to make dynamic, then click the Logic object (Decision Node) from the Objects Panel.
Adding Logic will surface a + to the right of your landing page—click it to attach the module you want to control.
After the Decision Node, add your destinations (another page in the flow, an external URL, or another route).
Set your Smart Rule conditions and map each condition to the correct destination. As a reminder, make sure to always add a fallback destination for anyone who doesn’t match your rules.
When everything looks right, Save and Publish your Flow.
Example configurations
Example A: Device-based app download
Module: “Download the App” button
If Device = iOS → route to Apple App Store URL
Fallback → route to Google Play URL
Example B: Localized offer
Module: “Find a store” button
If Location = New York → route to New York store locator
Fallback → route to national locator
Example C: Re-engagement routing
Module: Embedded sweepstakes form
If user has previously not converted on form → display embedded form module on landing page
Fallback → Route to brand website
Smart Rules for Modules with Embedded Sweepstakes Forms
If you’re using an embedded sweepstakes form on a Landing Page, visitors who submit and then close the Thank You page can land back on the page and see the form again—creating a frustrating “submit → thank you → back to form → submit again” loop. To prevent this, apply Smart Rules to the embedded form module (not the full page) and place the Decision Node after the landing page, so the form module behavior changes depending on whether they’ve already submitted:
Not converted: show the embedded form
Converted: route the module to a fallback (e.g., “Already entered” page, next-best CTA, or external URL)
Note: If you redirect users to an external destination immediately after submission, you typically don’t need module-level rules to break the loop because they’ve exited the Flowcode experience; if they return later, they’ll start a fresh visit and see the correct experience.
Read more on Sweepstakes capabilities here.
FAQ
Does this replace page-level Smart Rules?
No. Page-level Smart Rules are still great when the entire experience needs to change. Module-level Smart Rules add precision when only specific components should adapt.
Can I use both page-level and module-level rules together?
Yes. Many teams use page-level rules to set the “entry experience,” then module rules to personalize downstream actions.
Will this help reduce duplicated pages?
Yes! This is one of the biggest wins. You can keep a single Landing Page design and apply dynamic logic where it matters most.