GetResponse on your landing pages
GetResponse is a list-building machine: autoresponders by day, automation workflows, webinars. Its weak point on paid traffic is the same as every email tool's. It mails whoever lands on the list, and the list only works as fast as leads reach it.
GetResponse is one of LanderLab's built-in integrations. Switch it on for a page and each lead lands on your GetResponse list as a contact when the form is sent. When some leads shouldn't get there, run it as an action in a LanderLab workflow instead, with a Filter or a Switch in front, and the list stays clean while GetResponse does the emailing.
GetResponse contacts from every page that needs them
For a page whose every lead belongs on the list, the built-in integration is enough: each submit becomes a GetResponse contact on your list, with the answers and tracking values in fields. Nothing to export, nothing to import.
GetResponse is also one of the actions in LanderLab Workflows (beta). A workflow starts with the Lead trigger, which can listen to several landing pages at once, so every angle you test for an offer can feed the same list through one set of rules.
Keep unqualified leads off your GetResponse list
Put a Filter node before the GetResponse action. It checks the fields the page captures against the values you set, and a lead that doesn't match stops there, so your emails go to people you can sell to.
Need more than one destination? A Switch node sends each lead down its own branch, so each geo or each product can end in its own GetResponse action and list.
See where each lead went
The workflow's Runs view shows each lead's path, the branch it took and where it ended up, and marks the run when a step fails. When a contact is missing from GetResponse, you can check what happened to it. If the list uses double opt-in for API sign-ups, the contact shows up once they confirm.
Attribution that survives the autoresponder
Hidden fields capture utm_campaign and the click ID from the ad, and LanderLab adds the page URL and the A/B variant. Sent to GetResponse custom fields, they let you compare campaigns on who opens, clicks and buys from your autoresponders, not on who filled in a form.
