Unspecified under unspecified hits | Community
Skip to main content
N
NingLaoShi
Level 2
August 21, 2024
Question

Unspecified under unspecified hits

  • August 21, 2024
  • 2 replies
  • 707 views

how can i backtrack the origin of an unspecified hits under an unspecified hit from the page's GUID? the GUID of the page is just from the data layer. the page URL dimension is also unspecified

these comes from visits and unique visitor. but for page views, there is no unspecified data captured.

 

thank you

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

2 replies

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 21, 2024

Hi @ninglaoshi 

are you by any chance capturing the URL in one of your props or eVars? This you could use to break down the unspecified value.
As best practice, I would always recommend capturing it in an eVar since it can hold 255 instead of the 100 characters as props.

 

Hope that helps

Cheers from Switzerland!
N
NingLaoShiAuthor
Level 2
August 21, 2024

yes, i am capturing the URL in an evar. but there are also unspecified hits for the URL 

 

i just need to know where this unspecified value came from

 

thank you

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 21, 2024

Do you have any APIs pushing data into your report suite?

Also, what do you see if you break down by Referrer or Page dimensions?

Cheers from Switzerland!
Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 21, 2024

Hi,

 

What metrics are you looking at here? Are you 100% sure that the eVar will always be populated? There are lots of potential times when an eVar could be missing:

 

  • Lifecycle metrics on a mobile app
  • A value set only on the page level and expecting the action to maintain the value (but the action was triggered before the page for some users)
  • The script used to populate that eVar randomly failed (so it works in testing, but once under load you might be seeing some issues)

 

 

Since your URL value was missing, you may have to try other parameters to try and breakdown to identify the exact hits that are a problem... this is not a fun task, but only you can determine what to try, we don't know what all you are tracking and what could be leveraged to support this....

Terms & ConditionsAccessibility statement

Loading footer...