Segment with a temporal (Timestamp) element | Community
Skip to main content
marcod2
marcod2
New Participant
May 11, 2017
Solved

Segment with a temporal (Timestamp) element

  • May 11, 2017
  • 4 replies
  • 2022 views

Hello,

I wish to build a segment which will exclude the traffic from chrome 48.0 after mid February only. 

See attached screenshot of my attempt which is not working. I've tried to combine Timestamp > date + Chrome 48 traffic.

Thanks,

Marc

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 Løjmann

Hi Marc,

Your segment only works in Data Warehouse (as the definition also states). If you want to create something that works, you will have to define a segment same style as attached...

You will have to update it each month for the rest of the year, afterwards you can exclude all of 2018, 2019 and so forth... Not the most flexible solution, but all you can do as far as I can see... 

/Løjmann

4 replies

Løjmann
LøjmannAccepted solution
New Participant
May 15, 2017

Hi Marc,

Your segment only works in Data Warehouse (as the definition also states). If you want to create something that works, you will have to define a segment same style as attached...

You will have to update it each month for the rest of the year, afterwards you can exclude all of 2018, 2019 and so forth... Not the most flexible solution, but all you can do as far as I can see... 

/Løjmann

TanmayMathur
TanmayMathur
Employee
May 15, 2017

Hi Marc,

Not sure if this would work but you can try something like the attached definition. Also you might have to create a report starting February as it would get overwritten like you said.

marcod2
marcod2Author
New Participant
May 15, 2017

Can you suggest an alternative logic?

I tried to add a custom date range as part of the segment conditions. This however did not work as I'd wanted it just overwrote the date range for my report

TanmayMathur
TanmayMathur
Employee
May 15, 2017

Hi Marc,

The segment is not working because the logic that you used is not compatible with Analysis Workspace or Reports & Analytics. See the product compatibility above it only lists Data Warehouse. You might have to try using a different logic to achieve this. 

Terms & ConditionsAccessibility statement

Loading footer...