Integrations / Personalisation
Ninetailed
Server-side delivery to the Ninetailed (Contentful Personalization) Experience API. Upserts visitor profiles from page, identify, and track events for personalisation and audience targeting. Traits are sent as plain profile attributes (no hashing). Events are batched into the events[] array (up to 200 events / 50 identify / 50 profiles per call).
Datafly Signal delivers first-party events to Ninetailed server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Ninetailed expects.
Why route Ninetailed through Datafly Signal
Profiles update from the server, not the browser
Events reach Ninetailed 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 Ninetailed rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Ninetailed 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_cartidentifypagepurchasesign_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 Ninetailed documentation.
Frequently asked questions
Does Datafly Signal integrate with Ninetailed?
Yes. Datafly Signal delivers first-party events to Ninetailed server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Ninetailed expects. The integration is included in every deployment at no additional cost.
How is server-side Ninetailed tracking different from the Ninetailed tag?
The Ninetailed 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 Ninetailed from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Ninetailed?
The blueprint ships with mappings for add_to_cart, identify, page, purchase, sign_up, view_item. Any event in your schema can be mapped to Ninetailed through pipeline configuration without a code change.
Do I need to keep the Ninetailed tag on my site?
No. Signal delivers to Ninetailed from the server, so no client-side Ninetailed script is required on your site.
Other personalisation integrations
Ready to move Ninetailed server-side?
See how Datafly Signal delivers first-party events to Ninetailed from infrastructure you control, with hashed identity and consent enforcement built in.