Integrations / Personalisation
Appcues
Server-side delivery to the Appcues v1 user-activity API. Forwards behavioural events (page views, sign-up, login, feature usage) and identify traits to the user's Appcues profile so product-adoption flows, checklists, and surveys can target users from first-party server-side data.
Datafly Signal delivers first-party events to Appcues server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Appcues expects.
Why route Appcues through Datafly Signal
Profiles update from the server, not the browser
Events reach Appcues 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 Appcues rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Appcues 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_usedloginpagesign_upsubscription_startedtrial_startedVertical presets
B2B / 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 Appcues documentation.
Frequently asked questions
Does Datafly Signal integrate with Appcues?
Yes. Datafly Signal delivers first-party events to Appcues server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Appcues expects. The integration is included in every deployment at no additional cost.
How is server-side Appcues tracking different from the Appcues tag?
The Appcues 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 Appcues from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Appcues?
The blueprint ships with mappings for feature_used, login, page, sign_up, subscription_started, trial_started. Any event in your schema can be mapped to Appcues through pipeline configuration without a code change.
Do I need to keep the Appcues tag on my site?
No. Signal delivers to Appcues from the server, so no client-side Appcues script is required on your site.
Other personalisation integrations
Ready to move Appcues server-side?
See how Datafly Signal delivers first-party events to Appcues from infrastructure you control, with hashed identity and consent enforcement built in.