Loops integration

Trials, waitlists and demo requests from your ads should be in Loops before the welcome email is due. The page's webhook saves each signup as a Loops contact as the form is sent, on the right list, with the campaign on the profile.

  • Webhook
  • Landing pages, Quiz funnels, Workflows (beta, by HTTP Request)

Why connect it

Why Loops and LanderLab

  • Workflows that start on the signup

    Loops workflows can start on Contact added, Contact added to list or Event received, so a page signup starts onboarding the moment it lands.

  • Repeat signups update, not fail

    Saving through Loops' update call creates new contacts and updates existing ones, so someone who signs up twice from two ads keeps one contact.

  • Mailing lists chosen per page

    The trial page, the waitlist and the webinar page can each subscribe to their own Loops list, and each list gets its own workflow.

  • Source and campaign on the contact

    Loops' source and userGroup fields plus your custom properties hold the channel, campaign, variant and answers for every signup.

  • No connector in the middle

    The webhook calls Loops directly, and your API key stays in the request header, never in the page's code.

Loops on your landing pages

Loops is where a lot of SaaS teams run onboarding and launch email. The signups that matter most, the ones from paid search and LinkedIn, often come in through a landing page outside the app, and they reach Loops late or without the details that would put them in the right workflow.

LanderLab's webhook saves each signup to Loops through its API, as an update that creates the contact if it's new and updates it if it isn't, so a repeat signup never fails. The request can subscribe the contact to a mailing list and carry the campaign, the variant and any quiz answer as contact properties. There's no Zap in between.

It fits SaaS and app teams buying traffic for trials, waitlists, webinars and demos on Google, LinkedIn or Meta.

Trial and waitlist signups into Loops, as they happen

For a SaaS trial, the first hour decides a lot. When the landing page saves each signup to Loops as the form is sent, the welcome email and the first onboarding nudge arrive while the person still has the tab open.

Because the request is an update that creates missing contacts, a person who already exists in Loops, from the app or an earlier campaign, is updated instead of rejected. Nobody falls through because they signed up twice.

Loops lists and workflows matched to the page

Each page can subscribe its signups to a different Loops mailing list: trial, waitlist, webinar. A Contact added to list workflow on each list sends the sequence that fits. If you want a separate path for one quiz answer, an event sent from LanderLab Workflows (beta) can start an Event received workflow instead.

Know which campaign brought each Loops contact

Loops has default properties for source and user group, and custom properties for the rest. Set source to the channel, put the plan or team size in user group, and send utm_campaign and the A/B variant as custom properties. You can then filter the audience by campaign and see which ad sets bring users who activate.

Test the trial page against real signups

Run two versions of the trial page on the same Google Ads traffic. The Leads tab filters signups by variant, and the variant property on each Loops contact lets you follow both groups through onboarding, so you choose the page by activation, not only by form fills.

Use cases

Ways to use Loops on paid traffic

  • 01

    Trial signups from Google Ads

    An invoicing tool runs search ads to a trial page. Each signup joins a Loops list with team size and campaign as properties, and an onboarding workflow starts right away.

  • 02

    Waitlist for a product launch

    A waitlist page on Meta and LinkedIn subscribes each signup to a launch list in Loops. On launch day the team emails the list, and the campaign property shows which ads built it.

  • 03

    Webinar registrations from LinkedIn

    A webinar page saves each registrant to Loops with role and company size, and a list workflow sends the reminder, the replay and a trial invite.

FAQ

Loops integration FAQ

Anything not here, ask us.

Loops and LanderLab

When is Loops worth connecting to my landing pages?

When your SaaS email runs in Loops and you buy traffic for trials or waitlists: signups arrive as they happen, on the right list, with the campaign attached, so workflows start on time.

Does LanderLab integrate with Loops?

Yes, through the page's Webhook integration: it calls Loops' contacts API, which creates the contact or updates the one you already have.

Do I need Zapier to send leads to Loops?

No. The webhook saves the contact through Loops' API itself, list and properties included.

Will a repeat signup cause an error in Loops?

Not when the page uses Loops' update call, which creates the contact if it's new and updates it if it already exists.

Will Loops see my UTMs and quiz answers?

Yes. Hidden fields capture the UTMs from the ad's URL, and both can be sent as Loops contact properties.

Other integrations

Plug in the rest of your stack.

Connect Loops and launch your next page.

Build the page, switch Loops on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59