Using s.products on multiple different funnels | Community
Skip to main content
T
tcrewes1
Level 3
January 29, 2026
Solved

Using s.products on multiple different funnels

  • January 29, 2026
  • 2 replies
  • 38 views

Hi everyone,

I hope you are well. I have a question on the Adobe Analytics products variable.

We currently use our products variable (s.products) for our site's retail journey. However, a separate journey is currently being worked on for a different part of the site/business area. This journey also allows users to purchase multiple different items together, each with their own attributes.

I want to keep everything in the same report suite for pathing/attribution purposes. As far as I'm aware Adobe Analytics only gives us one products variable per report suite. I'm curious if anyone has experience of using the products variable for multiple separate journeys in the same report suite. If so, are there any recommendations/best practices to avoid the data becoming a horrible mess.

For info: We are running a "traditional" Adobe Analytics deployment (not CJA) using App Measurement (not Web SDK) through a third party Tag management system (not Launch). 

Any advice on this would be hugely appreciated.

Thanks

    Best answer by Jennifer_Dungan

    I actually use s.products for about 20 different uses (and they are not all related to “purchases”). I use s.products for our subscription flow (purchase), for our gifting flow (also purchase), for our walls, overlays, newsletter subscriptions, etc. (The reason I need to use s.products is because I need merchandising eVars to hold information about each specific usage)

     

    I use the optional category slot in the s.products notation to distinguish the uses, and each use has its own set of merchandising eVars.

     

    I can use the category or eVars to help build out isolated reports for each usage.

     

    Right now, segments don’t work well for multiple product uses on the same page, however, Adobe will be releasing “sub-hit segmentation” sometime this year that will finally allow us to properly target individual products with our segments.

     

    We are also using “traditional” AppMeasurement.js… but we are using Launch… however, any tag manager where you can use JS to process and set your variables should be fine (I don’t use Launch’s UI for that, 95% of my implementation is custom code to support various complexities).

    2 replies

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    January 29, 2026

    I actually use s.products for about 20 different uses (and they are not all related to “purchases”). I use s.products for our subscription flow (purchase), for our gifting flow (also purchase), for our walls, overlays, newsletter subscriptions, etc. (The reason I need to use s.products is because I need merchandising eVars to hold information about each specific usage)

     

    I use the optional category slot in the s.products notation to distinguish the uses, and each use has its own set of merchandising eVars.

     

    I can use the category or eVars to help build out isolated reports for each usage.

     

    Right now, segments don’t work well for multiple product uses on the same page, however, Adobe will be releasing “sub-hit segmentation” sometime this year that will finally allow us to properly target individual products with our segments.

     

    We are also using “traditional” AppMeasurement.js… but we are using Launch… however, any tag manager where you can use JS to process and set your variables should be fine (I don’t use Launch’s UI for that, 95% of my implementation is custom code to support various complexities).

      T
      tcrewes1Author
      Level 3
      January 30, 2026

      Excellent, thanks ​@Jennifer_Dungan , that’s really helpful. Useful to know that Adobe are working on a solution to the multiple products scenario as well.

        Jennifer_Dungan
        Community Advisor and Adobe Champion
        Jennifer_DunganCommunity Advisor and Adobe Champion
        Community Advisor and Adobe Champion
        January 30, 2026

        Yeah, it should be a game changer.

        In the meantime, I would use a QA / Dev suite to test scenarios with s.products… make sure that you can accomodate the tracking now (before sub-hits is available), and that you don’t break anything existing.

        Vinay_Chauhan
        Community Advisor and Adobe Champion
        Vinay_ChauhanCommunity Advisor and Adobe Champion
        Community Advisor and Adobe Champion
        January 29, 2026

        Adobe supports using a single ‘s.products’ variable for multiple funnels within the same report suite. The recommended approach is to -

        • Use the category field in ‘s.products’ to differentiate journeys or business areas.

        • Use separate merchandising eVars to capture journey-specific product attributes.

        • Build reporting and attribution using the category and merchandising eVars to keep each funnel isolated.

        This works cleanly in traditional AppMeasurement implementations.
        The main limitation today is product-level segmentation when multiple products exist on the same hit, which Adobe has acknowledged and is addressing with sub-hit segmentation.

          T
          tcrewes1Author
          Level 3
          January 30, 2026

          Thanks ​@Vinay_Chauhan . That’s really clear and helpful.

          Terms & ConditionsAccessibility statement

          Loading footer...