- Fullstory integrates with multiple Adobe products. Specific plan and role requirements vary by integration.
- See individual integration articles for details.
Fullstory integrates with multiple Adobe products in different ways, from installing the Fullstory snippet via Adobe's tag manager to streaming Fullstory event data into Adobe Experience Platform. This guide helps you find the right integration path based on your Adobe products and your goals.
Getting started? Most customers integrating Fullstory with Adobe should start with the Fullstory Extension for Adobe Experience Platform Data Collection. It handles deployment, configuration, and data mapping entirely through Adobe's UI—no custom code required.
This article will cover the following:
- What are you trying to do?
- Choosing your integration path
- Integration articles
- Legacy approaches
- Frequently Asked Questions
What are you trying to do?
When customers say "Fullstory + Adobe," they usually mean some combination of three things. Not every integration covers all three, and not every customer needs all three.
- Get the Fullstory snippet on the page: Deploy Fullstory on your website using Adobe's tag management system, without modifying your codebase directly.
- Send Fullstory data to Adobe: Pass Fullstory session replay URLs or event data into Adobe Analytics eVars, Adobe Experience Platform, or other Adobe tools so your team can link sessions to analytics data.
- Send Adobe data to Fullstory: Capture Adobe Analytics eVar and prop data in Fullstory using Data Layer Capture, so you can search and segment sessions using your existing analytics dimensions.
Choosing your integration path
The right path depends on your tag manager and what you want to accomplish.
- If you use Adobe Experience Platform Data Collection (formerly Adobe Launch or Adobe Tags): Use the Fullstory Extension for AEP Data Collection. This is the recommended approach for most customers. The extension handles Fullstory deployment, configuration, and data mapping entirely through Adobe's UI.
- If you use Tealium iQ: Use the AEP Session URLs via Tealium iQ guide to send Fullstory session URLs to Adobe Experience Platform through your Tealium setup.
- If you want to stream Fullstory events to AEP server-side: Use AEP Activation Real-time Event Streams to configure real-time streaming from Fullstory into Adobe Experience Platform via the Anywhere: Activation product.
- For customers with the older at.js (non-web SDK), if you want to capture Adobe Analytics data in Fullstory: Use Adobe Analytics (Data Layer Capture) to automatically ingest Adobe Analytics eVar and prop data into Fullstory.
- If you use Adobe Analytics (not AEP) and want session URLs in an eVar: Use the Adobe Analytics - Fullstory Session URLs guide for a lightweight JavaScript approach using AppMeasurement.
Integration articles
The following articles cover each integration path in detail.
| Article | Description |
|---|---|
| Fullstory Extension for AEP Data Collection | Install, configure, and map Fullstory data using Adobe Experience Platform Data Collection. Recommended for most customers. |
| AEP Session URLs via Tealium iQ | Send Fullstory session replay URLs to Adobe Experience Platform through Tealium iQ. |
| Adobe Analytics - Fullstory Session URLs | Send Fullstory session replay URLs to Adobe Analytics eVars using AppMeasurement. |
| AEP Activation Real-time Event Streams | Stream Fullstory events to Adobe Experience Platform server-side using Anywhere: Activation. |
| Adobe Analytics (Data Layer Capture) | Capture Adobe Analytics eVar and prop data in Fullstory using Data Layer Capture. |
| Fullstory and Adobe Target | Integrate Fullstory with Adobe Target for A/B testing insights. |
| Data Layer Capture | General data layer capture overview, including Adobe Analytics and other supported data layers. |
Legacy approaches
Some older documentation references Adobe Dynamic Tag Manager (DTM), which has been deprecated by Adobe. If your team is still using DTM, see the Adobe Experience Platform Launch (ex Adobe DTM) article for reference. For new implementations, use the Fullstory Extension for AEP Data Collection instead.
Frequently Asked Questions
What is the difference between Adobe Launch, Adobe Tags, and Adobe Experience Platform Data Collection?
They are the same product under different names. Adobe has rebranded its tag management system over the years: Adobe Launch became Adobe Tags, which is now officially called Adobe Experience Platform Data Collection. If your team uses any of these names, the Fullstory Extension for AEP Data Collection article is the right starting point.
Which integration path should I choose if I am not sure?
Start with the Fullstory Extension for AEP Data Collection. It is the most comprehensive option and handles Fullstory deployment, configuration, and data mapping through Adobe's UI without requiring custom code.
Can I use multiple integration paths at the same time?
Yes. The integration paths serve different purposes and can complement each other. For example, you might use the Fullstory Extension to deploy Fullstory and configure data mapping, while also using Data Layer Capture to bring Adobe Analytics eVar data into Fullstory, and Activation to stream Fullstory events to AEP server-side.