Prepared for Dollar General

Customer Journey Analytics + Fullstory

See the whole journey. Fix the exact moment it breaks.

Adobe Customer Journey Analytics and Fullstory work at different levels of the customer experience. Used together, they give Dollar General a clear path from spotting a problem to proving the fix worked.

Two perspectives

Complementary, not competing

One platform shows the customer's journey across every channel and what it means for the business. The other shows what customers actually encountered inside a web or mobile experience.

Customer Journey Analytics

Context at scale

Who is engaging, what they do across channels, what sequence leads to an outcome, how large the opportunity or issue is, and what it means to the business.

Fullstory

Depth within the digital experience

What customers encounter in individual web and mobile experiences, where friction occurs, and what may be contributing to that behavior.

Customer Journey Analytics compared with Fullstory
Customer Journey AnalyticsFullstory
PerspectiveCustomer and interactions over timeDigital session and experience interactions
Primary questionWhat is happening across the customer journey, and what is the business impact?What did the customer experience within the digital interaction?
ScopeCross-channel, online and offlineDeep web and mobile experience
Example dataWeb, app, marketing, CRM, loyalty, customer service, POSClicks, scrolling, errors, performance and experience signals
Typical workflowPopulation → segment → journey → outcomeSession → behavior → issue → diagnosis

Where they overlap (funnels, paths, segmentation, drop-off), use CJA as the enterprise measurement layer and go to Fullstory when teams need to dig into the experience itself.

A Dollar General example

A coupon is clipped online. The purchase happens in a store.

Digital behavior often drives outcomes in another channel. CJA connects the sequence using customer identity, so the analysis moves from "what happened in this session?" to "what happened across this customer's journey?"

  1. 1
    Offer receivedMarketing
  2. 2
    Visits DG.comWeb
  3. 3
    Clips a couponWeb · Fullstory depth
  4. 4
    Opens the appMobile · Fullstory depth
  5. 5
    Store visit and purchasePOS
  6. 6
    Contacts supportCustomer service
Fullstory shows

What the customer experienced

For example: selects a coupon, tries to apply it, gets an unclear response, repeats the action, then leaves checkout.

CJA quantifies

What it meant for the business

  • How many customers hit the issue, and which segments
  • Where they left the journey
  • Whether they bought later online or in a store
  • Whether they contacted customer service
  • The conversion and revenue opportunity tied to them

A continuous model

Detect, quantify, investigate, improve, measure

Each platform does what it is best at, and every fix is measured against real customer and business outcomes.

  1. Adobe CJADetect

    Find where an important journey is underperforming.

  2. Adobe CJAQuantify

    Size the affected population, segments and outcome.

  3. FullstoryInvestigate

    See what customers encountered and where friction occurred.

  4. Product · UX · EngineeringImprove

    Address the experience or technical cause.

  5. Adobe CJAMeasure

    Confirm abandonment fell and conversion, store purchase and repeat purchase improved.

Adobe CJAFullstory and DG teams

Combined use cases

Questions only the two platforms can answer together

Pick a scenario to see how each platform contributes.

Fullstory

What friction did the customer experience while interacting with a digital coupon?

Adobe CJA

Did that customer ultimately purchase in a Dollar General store?

Connecting the platforms

Bring in the right signals, not every click

The goal is not to copy every Fullstory interaction into CJA. Start light, and go deeper only where the use case justifies it.

1

Connect the session

Link a journey in CJA to the relevant Fullstory session so an analyst can move from a population to representative replays.

  • Fullstory session ID and replay reference
  • Customer or session identifier
  • Timestamp and journey identifier

Context without duplicating session data

2

Add selected experience signals

Make a few Fullstory-derived signals available alongside the journey to unlock new questions.

  • Friction and repeated-interaction flags
  • Form abandonment and error indicators
  • Affected page or component, performance issue

Targeted analytical depth

3

Broader behavioral integration

Where the value is clear, selected experience events become part of the Adobe Experience Platform data model and are analyzed in CJA.

  • Fullstory signals into Adobe Experience Platform
  • Identity plus governed customer data
  • Journeys and impact analyzed in CJA

Deepest integration

What to validate before going deeper
  • Identity strategy
  • Session definitions
  • Dataset and schema design
  • Data volume
  • Retention requirements
  • Consent and privacy requirements
  • Governance
  • Data minimization

Recommended operating model

From enterprise journey data to measured improvement

Each layer feeds the next, and the loop closes when CJA measures the result.

Enterprise journey data

Stores and POSLoyaltyCRMWebAppMarketingCustomer serviceSelected Fullstory signals

Adobe Experience Platform

Identity plus governed customer and event data

Customer Journey Analytics

Unified journeys, segmentation, conversion and fallout, attribution, experiment analysis, online-to-offline analysis and business impact

Fullstory experience context

Detailed digital experience investigation

Product, UX and engineering improvement

CJA measures customer and business impact

Did the change work?