Unspecified data - Adobe Analytics | Community
Skip to main content
R
reddy_y-11
New Participant
September 21, 2023
Solved

Unspecified data - Adobe Analytics

  • September 21, 2023
  • 1 reply
  • 6391 views

Hello everyone,

 

V11 (Expiry after HIT ) - capturing the data like "A, B, C , D ". 

V11 fires in every server call.

 

Here my question are

  1. more number in Occurence then page views and custom page view(e1) why?
  2. In Dashboards should we use Occurence are not ? If yes in which seniro we should consider Occurence?
  3. In Dashboards should we use Page views are not ? If yes in which scenario we should consider Page views?
  4. To aviod unspecified what are the steps need to be consider?
  5. Why unspecified values are following into Analytics?

 

 

 

Please help me on this.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by leocwlau

Hi @reddy_y-11,

Two reference documents

Unspecified, None, Other, and Unknown in reporting | Adobe Analytics.

Occurrences | Adobe Analytics

So it doesn't seem v11 fired (or has data) in every server call as there are lots of tracking without v11

To your questions:

1. Occurrences including non-page view tracking.

2. I generally discourage the use of occurrences as it is the count of "hit" and no business contest. There are 1000 custom events that can be used to measure and give more meaningful reports, such as download, button click, video play, and etc.

3. When you want to know how many pages have been viewed, as traffic or as engagement.

4. No, you cannot avoid "Unspecified" as it is the nature that not all evars have values in all tracking. However, in your case, you are expecting v11 to have value on all server calls but seeing "Unspecified", you need to check the tracking and see where the data is missing.

5. As above and the nature

1 reply

leocwlau
leocwlauAccepted solution
New Participant
September 21, 2023

Hi @reddy_y-11,

Two reference documents

Unspecified, None, Other, and Unknown in reporting | Adobe Analytics.

Occurrences | Adobe Analytics

So it doesn't seem v11 fired (or has data) in every server call as there are lots of tracking without v11

To your questions:

1. Occurrences including non-page view tracking.

2. I generally discourage the use of occurrences as it is the count of "hit" and no business contest. There are 1000 custom events that can be used to measure and give more meaningful reports, such as download, button click, video play, and etc.

3. When you want to know how many pages have been viewed, as traffic or as engagement.

4. No, you cannot avoid "Unspecified" as it is the nature that not all evars have values in all tracking. However, in your case, you are expecting v11 to have value on all server calls but seeing "Unspecified", you need to check the tracking and see where the data is missing.

5. As above and the nature

    Jennifer_Dungan
    Jennifer_Dungan
    New Participant
    September 21, 2023

    I agree with @leocwlau, v11 doesn't seem to be fired on all server calls, the discrepancy is too large.

     

    It's almost as though you are setting v11 on page views, but not on actions (but without knowing your tracking this is a guess).

     

    Unlike Leo, I don't tell people not to use Occurrences, however, I do stress caution when using it... if you do use it, you should know exactly what you are pulling, why and also, you will often need to pair it with a segment to get exactly what you think you are getting... so if you don't really understand it, then yes, don't use it 🙂

     

    Leo is correct though, if you are expecting v11 on all server calls, reviewing your tracking to make sure this is actually happening would be a good place to start... same with where you are firing "Custom Page Views", as there seems to be a mismatch with Page Views there...

     

    Do you have mobile apps? Are they rolled into the same suite? Are the dimensions and events being properly set in processing rules for those apps? This could be causing some of the discrepancies....

    Terms & ConditionsAccessibility statement

    Loading footer...