Why Does a Fallout-Based Segment in a Calculated Metric Change Values with Different Date Ranges in Adobe Analytics | Community
Skip to main content
A
AthulV_
Level 2
May 6, 2026
Question

Why Does a Fallout-Based Segment in a Calculated Metric Change Values with Different Date Ranges in Adobe Analytics

  • May 6, 2026
  • 2 replies
  • 61 views

I created a segment based on a fallout touchpoint in Adobe Analytics, and then used that segment within a calculated metric wrapped around an event.

However, I’m noticing that the value of this metric changes depending on the overall date range selected in the report.

For example, when I set the date range from January 1 to January 31, the metric count for January is 100. But when I expand the date range from January 1 to April 30 and then break the data down by month, the count for January increases to 200 instead of remaining at 100 (which I believe is the correct value).

Can someone explain why this is happening? Is this expected behaviour when using a segment derived from a fallout touchpoint within a calculated metric?

    2 replies

    S
    spgberg
    Level 2
    May 6, 2026

    Thanks for sharing your question! I think there are a few additional details that might help us best answer your question:

    • Is your fallout container set to Visit or Person? You can click the gear icon in the fallout to check
    • Does your fallout contain a Date Range dimension? 
    • Is the segment you created set to Event, Visit, or Person?

    While I don’t know quite yet, I have a suspicion that it might be based on the container level you have for the segment wrapped around your event in the calculated metric.

    A
    AthulV_Author
    Level 2
    May 6, 2026

    Thanks for your response! Here are the details you requested:

    1. The fallout container is set to Visitor.
    2. There’s no date range applied within the fallout itself—I’ve only used a date range at the panel level.
    3. The segment I created is also set at the Visitor level.

    Hope this helps! Let me know if you need any additional details.

    B
    BraxtonBu1
    Level 1
    May 6, 2026

    Hi all!

    I believe that this is happening due to the segment being created at the visitor level. When the date range is extended, additional visitors will meet the qualification criteria of the segment. There may be visitors who qualified for the segment after January, so their events are not included in the segment if the date range does not include when they qualified for the segment. If the date range is extended to allow them to qualify for the segment, the events associated with them in January will now be included in the report. 

     

    In short, the extended date range allows for more people to qualify for the segment and now their events for the whole date range may be included as well as a result.

      MandyGeorge
      Community Advisor and Adobe Champion
      MandyGeorgeCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      May 7, 2026

      If you have a segment that is set to a visit or visitor level, that is going to impact where the segment looks for the data and what data it returns. Say for example you have the following segment

      VISITOR
         Page = Page A

       

      And you have a visitor that comes to your site

      April 1 = Page A

      April 2 = Page B

      April 3 = Page C

       

      If you set your date range to be April 2 - 3, it’s going to look on those dates and see if Page = Page A. In this example, it doesn’t, so that visitor won’t be returned. So if you break it down by date you would see

      Day        Visit (Segment, Page = Page A)

      April 2    0
      April 3    0

       

      If you set your date range to April 1-3, it will see that the visitor saw Page A, so it will get included. Then because your segment is at a visitor level, it’s going to include all of their interactions, regardless of which specific day it happened on.

      Day        Visit (Segment, Page = Page A)

      April 1    1
      April 2    1
      April 3    1

       

      Even though the visitor didn’t see Page A on each of those days, because the metric I have is Visit, and they did complete a visit on that day, the segment gets them included. So, for your example, as long as whatever metric you’re using was done by the visitor on those days (such as adding to cart, ordering, etc), even if it wasn’t the same action as in your segment, because they did the segment action at some point in that time period, all of their actions will be included. 

       

      So it’s less the fact that it was created from a touchpoint, but more the fact that it is set to a visitor level. If you want to limit the interactions to specific hits or visits, you can put that visitor segment inside of a hit or visit segment and add additional conditions to limit what information gets returned. 

        Terms & ConditionsAccessibility statement

        Loading footer...