Visits and Unique visitors segment

[avocadoLover2022]

hi, everybody. i've encountered an unspecified hits on my page name from visits and unique visitors segment. other parameters like page url are also unspecified.

i used the build information and shows that most of the unspecified hits are from the build date of my production deployment.

is it somehow related to my build date? because like ive said, other parameters are unspecified also. thank you

[AmanGu8]

@avocadoLover2022  It is not related to build date dimension you used for breakdown. 'Unspecified' occurs when there is no value sent in the dimension i.e. evar/prop but metric is still being collected. Here from your report screenshot, it seems that page views are quite less in which this 'Page Name' variable is sent and there seems to be more link track calls. Also, will suggest to check with developer if there was any recent change in Page Name capturing launch rule since the last production push. 

[bjoern__koth]

Can you validate if you see you prop/eVar for the launch build information is set in your page view requests?

Looks like this might only be set in some custom link track calls, hence you may see unspecified in your page view column

[avocadoLover2022]

the launch build information is a global variable hence it shows in pageviews and link clicks. tho there are unspecified values for page views, my main concern is for the visits and unique visitors. the unspecified hits are quite large

[bjoern__koth]

can you describe how exactly you have set up your custom dimensions Page Name, Build Date and Adobe Launch Information?

Meaning, are you using props or eVars? If you use eVars, how is the expiration set?

How and where do you set these values?

Just because you have defined something globally does not automatically make it appear in your tracking calls.

And also, please provide a screenshot of a page view request with the payload (either from the network tab or an extension of your choice).

Seems like we're missing something

[avocadoLover2022]

hi @bjoern__koth focusing on the page name here, we are getting the page name in the data layer of the page. we use evar for our page name

here is the screenshot of the page view

[bjoern__koth]

Hi @avocadoLover2022 

can you post a screenshot with the "web" object opened (expand recursively)?

[avocadoLover2022]

here, masking some company information

[bjoern__koth]

looks ok.

Since your screenshot contains a build date from August, is this still occurring or was it only during a specific time frame?

In other words, has a newer version fixed the issue in the meantime?

[avocadoLover2022]

hi @bjoern__koth it is still occurring until this time. we have encountered this after our web sdk migration

[avocadoLover2022]

the unspecified values for visits become large as much

[bjoern__koth]

how high are the numbers compared to the working traffic? is there any dependency in the webPageDetails.name value to data from the data layer that could potentially end up being empty if not set by the underlying page?

Or are you pulling this from e.g. a document.title that should always be set?

One idea that comes to mind to validate this would be using a data element for the webPageDetails.name that returns a default value if the to-be-tracked value is empty.

[avocadoLover2022]

here is the webPageDetails.name value and we used a data element for this

inside this data element for the page name, we are just getting the value of it from the data layer page properties using window.adobeDataLayer.getState(); so we are dependent on the value in the data layer

this is the comparison of the page views and the visits metric

[avocadoLover2022]

also the evar that we use for the page namen expires every load of the page