Integrations / Analytics
FullStory
Session replay and product analytics event tracking.
Datafly Signal delivers first-party events to FullStory server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload FullStory expects.
Why route FullStory through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so FullStory receives the complete event stream.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what FullStory needs to attribute the event to the right session.
One consent decision governs every destination
FullStory 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_usedpagepurchasesign_upsubscription_startedview_itemVertical presets
Retail, 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 FullStory documentation.
Frequently asked questions
Does Datafly Signal integrate with FullStory?
Yes. Datafly Signal delivers first-party events to FullStory server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload FullStory expects. The integration is included in every deployment at no additional cost.
How is server-side FullStory tracking different from the FullStory tag?
The FullStory 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 FullStory from your server, so delivery does not depend on browser conditions.
Which events can Signal send to FullStory?
The blueprint ships with mappings for feature_used, page, purchase, sign_up, subscription_started, view_item. Any event in your schema can be mapped to FullStory through pipeline configuration without a code change.
Do I need to keep the FullStory tag on my site?
No. Signal delivers to FullStory from the server, so no client-side FullStory script is required on your site.
Other analytics integrations
Ready to move FullStory server-side?
See how Datafly Signal delivers first-party events to FullStory from infrastructure you control, with hashed identity and consent enforcement built in.