Omnisend on your landing pages
Store ads often send traffic to a page before the product page: a fit quiz, an advertorial, a giveaway. The email is captured there, but Omnisend only knows about people once they reach the store. Everyone who left in between is a paid click with no follow-up.
Omnisend is one of LanderLab's built-in integrations. Switch it on for a page and each lead becomes an Omnisend contact, with the quiz answers and the campaign as custom properties, ready for the automations you already run for your store. When several test pages should share one set of rules, or some leads should be kept out, Omnisend also works as an action in a LanderLab workflow.
Omnisend contacts from your pages and workflows
For a single quiz or advertorial, the built-in integration does the job: each submit becomes a contact in Omnisend, ready for the flows you already run for your store. Omnisend is also one of the actions in LanderLab Workflows (beta), for when the same contacts should pass a filter or come from several pages.
Shoppers on your Omnisend list before they buy
Store ads often send traffic to a quiz, an advertorial or a giveaway before the product page. The visitor who leaves an email there hasn't bought anything yet. With the contact in Omnisend, your store's emails can reach them after they close the tab, and the click you paid for gets more than one chance to turn into an order.
Map the quiz result to a custom property and the follow-up can show the exact product the quiz matched.
Every test page, one workflow
A workflow's Lead trigger can listen to several pages at once, so every angle you test for a product feeds Omnisend through the same rules. Switch a page off in the trigger when its ads stop, and the rest keep sending.
Because every page feeds the same action, the contacts from each angle carry the same custom properties. A segment on the page property puts the quiz, the advertorial and the giveaway side by side in Omnisend's reports, measured on orders.
Consent and channels stay in Omnisend
Omnisend tracks email and SMS subscription separately on each contact, and its Welcome automation only sends to contacts subscribed to email. That keeps your sending rules in one place. Check the status a test contact arrives with before you build a launch around the Welcome automation.