Total Visits results do not make sence | Adobe Higher Education
Skip to main content
A
AlexSh16
October 30, 2025
Respondido

Total Visits results do not make sence

  • October 30, 2025
  • 3 respostas
  • 264 Visualizações

I have 2 Adobe Analytics reports being generated using Total Visits by field within date.

Using Identical Field Value and START DATE, and EARLY END Date (Sep 1, 2024 - Sep 30, 2025) I get a report which advises:

                              XXX

                              Out of 1,498,375 visits.

Using Identical Field Value and START DATE, and LATER END Date (Sep 1, 2024 - Oct 26, 2025 12:00 AM) I get a report which advises:

                              XXX

                              Out of 418,835 visits.

 

Logically, 0 sense but am I misunderstanding the function.

 

Any advice, please advise.

Melhor resposta por Jennifer_Dungan

Like the others, I agree that it's hard to see everything that is part of the report with the limited information provided.

 

However, given the behaviour, I also believe that there is likely a segment or two in place that is causing the variances... particularly one that has exclusions at the Visitor level.

 

Consider this:

 

Visit 1 (Aug)

  • Page A

 

Visit 2 (Sept)

  • Page B

 

Visit 3 (Oct)

  • Page C

 

 

Now, if you have a segment that looks like this:

 

VISITOR Exclude [

    Page equals "Page A"

]

 

When you run the report in Oct... you will see the data for that visitor. Same if you run the report in Sept, Page A isn't in the time frame... no exclusion happens. If you run it in Aug, you won't see the data.

 

If you then run the entire time frame, Aug to Oct, you won't get any data... Visit 2 and 3 will also be excluded because of the Visit in Aug, and the fact that you are excluding that visitor.

 

I don't know if this is the case, but it seems like something like this is likely happening.

3 Respostas

MandyGeorge
Community Advisor and Adobe Champion
MandyGeorgeCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
October 30, 2025

Are either of your reports using a segment/filter?

 

Are both reports using the same dimension? I'm not sure if that's what you mean by 'identical field value.' If you have different dimensions, if one doesn't fire as often as the other, there could be fewer visits attributed to it in total.

    Sergei_Kalinichenko
    Sergei_Kalinichenko
    Level 2
    October 31, 2025

    Hi Alex,

    Hard to advice not seeing a full screenshot - many caveats actually can be behind.

    First things that comes to my mind: do you use the same report suite? Many companies do have multiple report suites including virtual ones with predefined filters on the backend. 

     

      Jennifer_Dungan
      Community Advisor and Adobe Champion
      Jennifer_DunganCommunity Advisor and Adobe ChampionResposta
      Community Advisor and Adobe Champion
      November 1, 2025

      Like the others, I agree that it's hard to see everything that is part of the report with the limited information provided.

       

      However, given the behaviour, I also believe that there is likely a segment or two in place that is causing the variances... particularly one that has exclusions at the Visitor level.

       

      Consider this:

       

      Visit 1 (Aug)

      • Page A

       

      Visit 2 (Sept)

      • Page B

       

      Visit 3 (Oct)

      • Page C

       

       

      Now, if you have a segment that looks like this:

       

      VISITOR Exclude [

          Page equals "Page A"

      ]

       

      When you run the report in Oct... you will see the data for that visitor. Same if you run the report in Sept, Page A isn't in the time frame... no exclusion happens. If you run it in Aug, you won't see the data.

       

      If you then run the entire time frame, Aug to Oct, you won't get any data... Visit 2 and 3 will also be excluded because of the Visit in Aug, and the fact that you are excluding that visitor.

       

      I don't know if this is the case, but it seems like something like this is likely happening.

        Termos e condiçõesAccessibility statement

        Loading footer...