Integrations / Personalisation
AB Tasty
Server-side delivery to AB Tasty's Universal Collect (ariane) API. Maps Signal pageviews to PAGEVIEW hits, generic conversions to EVENT (action tracking) hits, and orders to TRANSACTION hits, keyed on the AB Tasty visitor id from the first-party ABTasty cookie.
Datafly Signal delivers first-party events to AB Tasty server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload AB Tasty expects.
Why route AB Tasty through Datafly Signal
Profiles update from the server, not the browser
Events reach AB Tasty 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
AB Tasty 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_checkoutgenerate_leadpagepurchasesign_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 AB Tasty documentation.
Frequently asked questions
Does Datafly Signal integrate with AB Tasty?
Yes. Datafly Signal delivers first-party events to AB Tasty server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload AB Tasty expects. The integration is included in every deployment at no additional cost.
How is server-side AB Tasty tracking different from the AB Tasty tag?
The AB Tasty 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 AB Tasty from your server, so delivery does not depend on browser conditions.
Which events can Signal send to AB Tasty?
The blueprint ships with mappings for add_to_cart, begin_checkout, generate_lead, page, purchase, sign_up, view_item. Any event in your schema can be mapped to AB Tasty through pipeline configuration without a code change.
Do I need to keep the AB Tasty tag on my site?
No. Signal delivers to AB Tasty from the server, so no client-side AB Tasty script is required on your site.
Other personalisation integrations
Ready to move AB Tasty server-side?
See how Datafly Signal delivers first-party events to AB Tasty from infrastructure you control, with hashed identity and consent enforcement built in.