Integrations / Marketing Automation
Ortto
Server-side delivery to the Ortto Custom Activity API (/v1/activities/create). Each Signal event upserts the person by email (phone fallback) and records a custom activity (act:cm:<event>) with attributes, plaintext identity fields, and source IP for geo. Honours marketing-consent as the Ortto email-permission flag (bol::p).
Datafly Signal delivers first-party events to Ortto server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Ortto expects.
Why route Ortto through Datafly Signal
Profiles update from the server, not the browser
Events reach Ortto even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Ortto rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Ortto 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_upsubscription_startedtrial_startedview_itemVertical presets
Retail, B2B / SaaS. 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 Ortto documentation.
Frequently asked questions
Does Datafly Signal integrate with Ortto?
Yes. Datafly Signal delivers first-party events to Ortto server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Ortto expects. The integration is included in every deployment at no additional cost.
How is server-side Ortto tracking different from the Ortto tag?
The Ortto 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 Ortto from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Ortto?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, sign_up, subscription_started, trial_started, and more. Any event in your schema can be mapped to Ortto through pipeline configuration without a code change.
Do I need to keep the Ortto tag on my site?
No. Signal delivers to Ortto from the server, so no client-side Ortto script is required on your site.
Other marketing automation integrations
Ready to move Ortto server-side?
See how Datafly Signal delivers first-party events to Ortto from infrastructure you control, with hashed identity and consent enforcement built in.