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 newIdentify users with their user ID, and traits like firstName become contact properties.
Add a mailingLists object to traits, with each list ID set to true or false.
A track call named after an event in Loops sends that event, and it can start a workflow.
Add the destination in RudderStack and paste in a Loops API key. The docs walk through each step.
In RudderStack Destinations, click New destination, search for Loops, and pick a source.
Which RudderStack calls does Loops use?
Two. An identify call creates or updates a contact, and a track call sends an event to Loops that can start a workflow.
Do I need an email address?
For new contacts, yes, or the identify call fails. Once a contact has been sent to Loops with its user ID, you can leave the email out, but it’s best to always include it.
How do I add contacts to mailing lists?
Add a mailingLists object to the identify traits. Each key is a mailing list ID, and the value is true to subscribe or false to unsubscribe.
Why isn’t my event reaching the right contact?
Call identify before track, so the event is associated with a specific contact. The event name in the track call also has to match the event in Loops.
How do I check that data arrived?
In RudderStack, a source’s Events tab shows incoming calls, and a destination’s Events tab shows any errors sending to Loops. In Loops, check the Audience page for contacts and the Events page for each event payload.
Is there a free plan?
Yes. The free plan includes unlimited contacts and up to 4,000 emails to your first 1,000 contacts in any rolling 30-day window, marketing and transactional combined. Upgrade to send to more subscribed contacts.