Segment Not working properly in Report Builder

Avatar

Avatar
Level 1
nk11339
Level 1

Likes

0 likes

Total Posts

7 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
nk11339
Level 1

Likes

0 likes

Total Posts

7 posts

Correct reply

0 solutions
View profile
nk11339
Level 1

29-06-2021

Hi All ,

 

Thanks for the help in advance.

 

We have created a segment in Adobe workspace and using it in Report Builder too. Segment is at HIT level for the entry pages and only restricted to HITS where Tracking code is either "NULL" or "UNSPECIFIED".

Segment is working fine in Adobe Omniture but not in Report Builder.

What could be reason for this.

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Seeker
Level 4
vibhatna
Level 4

Likes

46 likes

Total Posts

113 posts

Correct reply

24 solutions
Top badges earned
Seeker
Engage 1
Boost 25
Affirm 10
Give Back
View profile

Avatar
Seeker
Level 4
vibhatna
Level 4

Likes

46 likes

Total Posts

113 posts

Correct reply

24 solutions
Top badges earned
Seeker
Engage 1
Boost 25
Affirm 10
Give Back
View profile
vibhatna
Level 4

06-07-2021

@nk11339 ,

So instead of using Tracking code = Unspecified, we would suggest to use Tracking code does not exist or exist as per your need. 

Avatar

Avatar
Seeker
Level 4
vibhatna
Level 4

Likes

46 likes

Total Posts

113 posts

Correct reply

24 solutions
Top badges earned
Seeker
Engage 1
Boost 25
Affirm 10
Give Back
View profile

Avatar
Seeker
Level 4
vibhatna
Level 4

Likes

46 likes

Total Posts

113 posts

Correct reply

24 solutions
Top badges earned
Seeker
Engage 1
Boost 25
Affirm 10
Give Back
View profile
vibhatna
Level 4

29-06-2021

@nk11339 

Report builder works on API v1.4 and workspace works on API v2.0.

 

There is an issue with the 1.3 and 1.4 reporting API that makes it so that segments that filter by 'Unspecifed' will not work correctly. The problem lies in the fact that the API uses '::unspecified::' to reference unspecified values where the UI is using the word 'Unspecified'.

 

There is an easy work around for this issue that works in both the UI and the 1.3/1.4 APIs. If you instead check if the dimension exists in your segment filter then you will get the correct results.

 

This issue is fixed in the 2.0 API will not be a problem in the future as customers start using that new API.