Andrew S.

to my knowledge the solution to this is to create two separate insights. Filter the insight by the campaign(s) that have that same conversion window. Then insert both insights onto a board together. They won't be on "one" insight but will be next to each other on one board.

e.g.,

I do not do it by size but by OS.

User properties are not reflective of history. If free becomes tier1 then everything you look at for that user will reflect tier1. UNLESS you write the user_type as a property into an event when tracking that event. Then you can query the event property and see what was a free user doing something vs a tier1 user

Yeah. So I have a property that I capture at the user level. that property updates with a track as their property value updates (e.g., "ratings count"). But I also have a property that I attach to an event to capture what existed at the time of the event. So when a user gives a rating, I attach "ratings count" to that event so I know for that rating, how many ratings did that user have. So. if they rated an 11th time, the user property would have 11 for the ratings count, but the event would have 10, because it was at 10 prior to that rating.

If you are relying upon the user property than anything having to do with that, User will reflect the new value of that property. If you add that property to the event, programmatically, grabbing it from the User and submitting it with the event track, then that property would reflect the company value at the time of the event

You will notice that I have "rosé" and "Rosé" bc (so 2x) but separate actual data values. Otherwise each is only showing 1x.

I get: