Integrations / Marketing Automation
Loops
Server-side event delivery to Loops (loops.so) via the Send Event API. Identifies contacts by plaintext email or user ID, triggers Loops workflows by eventName, attaches event-specific data as eventProperties, and updates contact fields (firstName, lastName, userGroup, subscribed) via contactProperties. Marketing consent maps to the contact's subscribed flag.
Datafly Signal delivers first-party events to Loops server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Loops expects.
Why route Loops through Datafly Signal
Profiles update from the server, not the browser
Events reach Loops even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
One consent decision governs every destination
Loops is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutloginpagepurchasesign_upview_itemVertical presets
Default. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Loops documentation.
Frequently asked questions
Does Datafly Signal integrate with Loops?
Yes. Datafly Signal delivers first-party events to Loops server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Loops expects. The integration is included in every deployment at no additional cost.
How is server-side Loops tracking different from the Loops tag?
The Loops tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Loops from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Loops?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Loops through pipeline configuration without a code change.
Do I need to keep the Loops tag on my site?
No. Signal delivers to Loops from the server, so no client-side Loops script is required on your site.
Other marketing automation integrations
Ready to move Loops server-side?
See how Datafly Signal delivers first-party events to Loops from infrastructure you control, with hashed identity and consent enforcement built in.