Integrations / Personalisation
Kameleoon
Server-side delivery to the Kameleoon Data API (POST /visit/events). Sends page views as PAGE events and conversions as CONVERSION events (with goalId + revenue) so experiment exposure and goal attribution work first-party, immune to ad blockers and browser tracking prevention. Visitor matching uses the Kameleoon visitorCode cookie with an anonymous_id fallback.
Datafly Signal delivers first-party events to Kameleoon server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kameleoon expects.
Why route Kameleoon through Datafly Signal
Profiles update from the server, not the browser
Events reach Kameleoon 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 Kameleoon rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Kameleoon 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
pagepurchaserefundsign_upVertical 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 Kameleoon documentation.
Frequently asked questions
Does Datafly Signal integrate with Kameleoon?
Yes. Datafly Signal delivers first-party events to Kameleoon server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Kameleoon expects. The integration is included in every deployment at no additional cost.
How is server-side Kameleoon tracking different from the Kameleoon tag?
The Kameleoon 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 Kameleoon from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Kameleoon?
The blueprint ships with mappings for page, purchase, refund, sign_up. Any event in your schema can be mapped to Kameleoon through pipeline configuration without a code change.
Do I need to keep the Kameleoon tag on my site?
No. Signal delivers to Kameleoon from the server, so no client-side Kameleoon script is required on your site.
Other personalisation integrations
Ready to move Kameleoon server-side?
See how Datafly Signal delivers first-party events to Kameleoon from infrastructure you control, with hashed identity and consent enforcement built in.