Same segment, different numbers in Warehouse and Workspace... | Community
Skip to main content
M
MattBlake
Level 2
November 24, 2021
Solved

Same segment, different numbers in Warehouse and Workspace...

  • November 24, 2021
  • 1 reply
  • 1205 views

Hi, I have a Data Warehouse headscratcher... Hoping someone might be able to help me explain something...

 

The situation is this:

 

We have two props, one for 'full URL' (containing domain name, parameter strings) and one for 'path' (url excluding domain name and parameter strings).

 

We have a segment (let's call it Segment X) which is based around an assortment of 'full URL' starts with / contains values.

However, if I then create a wokspace table broken down by day, and compare it to a Data Warehouse table (just with visits, all visits, granularity day, therefore minimal scope for duplication) the numbers come back with quite substantial differences. Same metrics, same segment, same dimensions... different numbers.

 

If I then create a duplicate segment (let's call it segment Y) which is based around the same pages, but uses 'path' starts with / contains values instead of 'full URL', then the numbers in workspace and Data Warehouse match up.

 

Does anyone have any ideas about ways in which Workspace and Data Warehouse process data that means the same segment could work in a slightly different fashion? So essentially the same report gives different figures? I was thinking about stuff like character limits having an impact (as URLs are longer than paths)?

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 VaniBhemarasetty

@mattblake Yes, you are right in your understanding, In workspace there is a limitation to the size of values , since you are referring to prop here, the maximum size of the prop is 100 bytes, if the value is greater than 100 bytes , it strips the value to 100 and rest is ignored and hence if the url has query string parameters and character size exceeds 100, those extra values after 100 will be ignored.

However, in data warehouse that is not the case, you will be able to report the whole value,with out the size limit 

 

Now, when you are creating a segment with "Full URL" and you conditions says contains "query string parameter"

 

There are higher chances the population of segment will be less, because this "query string parameter" is stripped during processing and is longer there in analytics.

However, when the same segment is used in datawarhouse, it will have higher population because the "query string parameter" is there

 

Hope this explains

1 reply

VaniBhemarasetty
Adobe Employee
VaniBhemarasettyAdobe EmployeeAccepted solution
Adobe Employee
November 27, 2021

@mattblake Yes, you are right in your understanding, In workspace there is a limitation to the size of values , since you are referring to prop here, the maximum size of the prop is 100 bytes, if the value is greater than 100 bytes , it strips the value to 100 and rest is ignored and hence if the url has query string parameters and character size exceeds 100, those extra values after 100 will be ignored.

However, in data warehouse that is not the case, you will be able to report the whole value,with out the size limit 

 

Now, when you are creating a segment with "Full URL" and you conditions says contains "query string parameter"

 

There are higher chances the population of segment will be less, because this "query string parameter" is stripped during processing and is longer there in analytics.

However, when the same segment is used in datawarhouse, it will have higher population because the "query string parameter" is there

 

Hope this explains

M
MattBlakeAuthor
Level 2
November 29, 2021

Perfect, thanks!

Terms & ConditionsAccessibility statement

Loading footer...