Turn RudderStack events into emails
Add Loops as a RudderStack destination. Your identify calls create and update contacts, and your track calls send events that start workflows.
identifyThanks for subscribing, Sam
You’ll hear from us when we ship something new in Acme.
See what’s newContacts, lists, and events from one destination
Your identify calls update contacts and mailing lists, and your track calls send events.
Contacts from identify
Identify users with their user ID, and traits like firstName become contact properties.
Mailing list subscriptions
Add a mailingLists object to traits, with each list ID set to true or false.
Workflows from track
A track call named after an event in Loops sends that event, and it can start a workflow.
Event properties in emails
Data in a track call’s properties object arrives as event properties you can use in emails.
How it connects
Add the destination in RudderStack and paste in a Loops API key. The docs walk through each step.
Add the destination
In RudderStack Destinations, click New destination, search for Loops, and pick a source.
Add an API key
Generate a Loops API key and paste it into the API Key field.
Watch events arrive
RudderStack shows live events and delivery errors. The Loops Events page shows each payload it processed.
Frequently asked questions
Which RudderStack calls does Loops use?
Do I need an email address?
How do I add contacts to mailing lists?
Why isn’t my event reaching the right contact?
How do I check that data arrived?
Is there a free plan?