Integrations / Customer Data Platform
Lotame
Server-side first-party behavior collection into Lotame's Spherical / Panorama platform via the Behavior Collection Pixel (BCP) on crwdcntrl.net. Forwards page views and key conversion behaviors keyed to the Lotame Panorama ID, immune to ad blockers and browser tracking prevention.
Datafly Signal delivers first-party events to Lotame server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Lotame expects.
Why route Lotame through Datafly Signal
Profiles update from the server, not the browser
Events reach Lotame even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Lotame needs to attribute the event to the right session.
One consent decision governs every destination
Lotame 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_cartpagepurchasesign_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 Lotame documentation.
Frequently asked questions
Does Datafly Signal integrate with Lotame?
Yes. Datafly Signal delivers first-party events to Lotame server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Lotame expects. The integration is included in every deployment at no additional cost.
How is server-side Lotame tracking different from the Lotame tag?
The Lotame 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 Lotame from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Lotame?
The blueprint ships with mappings for add_to_cart, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Lotame through pipeline configuration without a code change.
Do I need to keep the Lotame tag on my site?
No. Signal delivers to Lotame from the server, so no client-side Lotame script is required on your site.
Other customer data platform integrations
Ready to move Lotame server-side?
See how Datafly Signal delivers first-party events to Lotame from infrastructure you control, with hashed identity and consent enforcement built in.