Integrations / Marketing Automation
Ometria
Server-side custom event delivery to Ometria's Data API push endpoint. Pushes the e-commerce funnel (product views, cart, checkout, purchase) and page views as Ometria custom_event records linked to contacts by email, for use in segmentation and cross-channel marketing automation.
Datafly Signal delivers first-party events to Ometria server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Ometria expects.
Why route Ometria through Datafly Signal
Profiles update from the server, not the browser
Events reach Ometria 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 Ometria rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Ometria 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_cartadd_to_wishlistbegin_checkoutpagepurchaseremove_from_cartsearchview_itemVertical presets
Retail. 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 Ometria documentation.
Frequently asked questions
Does Datafly Signal integrate with Ometria?
Yes. Datafly Signal delivers first-party events to Ometria server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Ometria expects. The integration is included in every deployment at no additional cost.
How is server-side Ometria tracking different from the Ometria tag?
The Ometria 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 Ometria from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Ometria?
The blueprint ships with mappings for add_to_cart, add_to_wishlist, begin_checkout, page, purchase, remove_from_cart, search, view_item. Any event in your schema can be mapped to Ometria through pipeline configuration without a code change.
Do I need to keep the Ometria tag on my site?
No. Signal delivers to Ometria from the server, so no client-side Ometria script is required on your site.
Other marketing automation integrations
Ready to move Ometria server-side?
See how Datafly Signal delivers first-party events to Ometria from infrastructure you control, with hashed identity and consent enforcement built in.