Integrations / Personalisation
Chameleon
Server-side event delivery to Chameleon's Observe API for real-time targeting of in-product Experiences (Tours, Microsurveys, Launchers, Tooltips). Sends GA4-style events with uid/email identity and flat custom properties; no PII hashing (Chameleon stores raw first-party identifiers).
Datafly Signal delivers first-party events to Chameleon server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Chameleon expects.
Why route Chameleon through Datafly Signal
Profiles update from the server, not the browser
Events reach Chameleon 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
Chameleon 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
feature_usedloginpagepurchasesign_uptrial_startedVertical presets
Product / 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 Chameleon documentation.
Frequently asked questions
Does Datafly Signal integrate with Chameleon?
Yes. Datafly Signal delivers first-party events to Chameleon server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Chameleon expects. The integration is included in every deployment at no additional cost.
How is server-side Chameleon tracking different from the Chameleon tag?
The Chameleon 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 Chameleon from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Chameleon?
The blueprint ships with mappings for feature_used, login, page, purchase, sign_up, trial_started. Any event in your schema can be mapped to Chameleon through pipeline configuration without a code change.
Do I need to keep the Chameleon tag on my site?
No. Signal delivers to Chameleon from the server, so no client-side Chameleon script is required on your site.
Other personalisation integrations
Ready to move Chameleon server-side?
See how Datafly Signal delivers first-party events to Chameleon from infrastructure you control, with hashed identity and consent enforcement built in.