Replicating User Journey Flow and Fallout Visuals in Power BI | Community
Skip to main content
E
ElinaMirin
Level 2
June 23, 2026
Solved

Replicating User Journey Flow and Fallout Visuals in Power BI

  • June 23, 2026
  • 1 reply
  • 98 views

Hello,

 

I have a Power BI Web Analytics Dashboard and I extract my data from Adobe Analytics using Report Builder and Datawarehouse. I am looking to explore ways of replicating Adobe Analytics visuals such as: user journey flow and fallout visual in Power BI. Do you have any ideas of how can I replicate these in Power BI, what data do I need to extract from Adobe Analytics?

I want to mention that I don’t want to use API or Raw Data Feeds as these require a higher level of effort and constant maintenance and my client does not want that. 

Is there any workaround? Or alternatives to understand how users navigate through the website? Any idea is welcomed.

Thank you,

    Best answer by Jennifer_Dungan

    While I don’t have PowerBI, years ago we did something similar for a “BI” dashboard that our developers build for some specific reports.

     

    Basically, at each level, we had to pull data using specific segments at each level… this works more for Fallout which follows a specific flow, I don’t think it would work for a Journey Flow which has a lot of branching…

     

    Let’s use a simple fallout:

    Promotion Page > Product Page > Add to Cart > Start Checkout > Order

     

    1. The first pull has to be the page views of the Promotion Page (simple Hit Segment)
    2. The next would need a sequential segment: View of Promotion Page THEN Product Page  (it’s up to you whether you need to restrict this to direct from Promo to Product, or eventual path)
    3. Then the next would need a more complex segment, matching the step 2 segment and adding the next step of Add to Cart (and this probably should be limited to the direct Product Page)
    4. As you probably guessed, this needs to follow all the sequential logic above, but likely just an “eventual path” model to “Start Checkout”
    5. Then all of the above, plus Order Completed

     

    So you need 5 segments, and 5 requests, then you can display that data into your replication fallout.

     

    However, Journey Flows…. I don’t know how you could replicate this properly, as there is so much branching… unless like above, you are doing a very specific flow…. 

    1 reply

    manpreetkaur27
    Adobe Support
    manpreetkaur27Adobe Support
    Adobe Support
    June 25, 2026

    If you are open to a supported connector, the Adobe Analytics Connector in Power BI is the lowest-effort integration option versus building a custom API or raw-feed pipeline.

    For Fallout-style analysis, you can build a good Power BI equivalent by defining the key journey steps upfront in Adobe Analytics and exporting the step-by-step counts for each funnel stage. This works well for curated journeys such as Home → Search → Product Detail → Cart → Checkout. 

    For Flow / user journey pathing, a true like-for-like replication in Power BI is not realistically supported using only Report Builder and Data Warehouse exports. That type of analysis depends on Adobe’s native pathing logic in Analysis Workspace, which is designed specifically for exploratory journey analysis.

      E
      ElinaMirinAuthor
      Level 2
      June 26, 2026

      Thank you very much for your response! I’ve also tried using the Adobe Analytics connector in Power BI, but unfortunately it does not work properly and it wasn’t a solution even for basic metrics. 

      The idea of exporting the data directly from the workspace is very good, but my concern is if it’s feasible long term (for fallout analysis). Also the website has many pages, so I think this will require to create a separate export for each page.

      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
      Community Advisor and Adobe Champion
      June 26, 2026

      While I don’t have PowerBI, years ago we did something similar for a “BI” dashboard that our developers build for some specific reports.

       

      Basically, at each level, we had to pull data using specific segments at each level… this works more for Fallout which follows a specific flow, I don’t think it would work for a Journey Flow which has a lot of branching…

       

      Let’s use a simple fallout:

      Promotion Page > Product Page > Add to Cart > Start Checkout > Order

       

      1. The first pull has to be the page views of the Promotion Page (simple Hit Segment)
      2. The next would need a sequential segment: View of Promotion Page THEN Product Page  (it’s up to you whether you need to restrict this to direct from Promo to Product, or eventual path)
      3. Then the next would need a more complex segment, matching the step 2 segment and adding the next step of Add to Cart (and this probably should be limited to the direct Product Page)
      4. As you probably guessed, this needs to follow all the sequential logic above, but likely just an “eventual path” model to “Start Checkout”
      5. Then all of the above, plus Order Completed

       

      So you need 5 segments, and 5 requests, then you can display that data into your replication fallout.

       

      However, Journey Flows…. I don’t know how you could replicate this properly, as there is so much branching… unless like above, you are doing a very specific flow…. 

        Terms & ConditionsAccessibility statement

        Loading footer...