Hi @m_alcantara, You've already got some good answers here, but to answer the above. The reason checking that box doesn't clear it is because you are clearing an existing value for event54, which of course is not there. If you'd set event54 on a previous hit, then it would be cleared. What I think y...

Hi @alchan,If you can anonymise the data, can you send over an example? There are a few reasons why that might happen, & some of them are normal & nothing to be concerned about/change. 

Could you add an example of how the products are sent in the hit? I think I'm clear but just to be sure.  For the above segment, yes that's pretty much it. Can you try & alter it so it's "product exists" & "revenue does not exist", & see if that excludes anything? 

Hmm, I don't have access to an account I can check this right now, but I think that might make it tricky. You could try a hit-based exclusion segment where Product exists & Revenue is 0 or does not exist, but I think that will exclude the entire hit (so the 'paid for' product as well). I'm not sure ...

Hi @SamMa10, Is it all part of one product string? So something like:;prod1;1;130,;prod2;1;0Or are they in separate hits/some other setup? 

Hi @AnkitGhosh, What @bjoern__koth says is correct- you really should try & explain that working around cookie consent isn't really in the spirit of the law/regulations.  However, it is possible to add a cookieless server call that occurs on eg. One Trust interactions, cookie banner clicks, etc. tha...

Hi @bluu,You can use classification rules on the already collected data to split them out, however that would be a separate report. You can't alter the already collected data there in that specific report.To do that on future data, you can either use a List Var or List Prop as already suggested, or ...

Not quite, this worked fine for me:  So it would be the other way around of what you have there- I mapped a standard field to a custom field. That might be why mine works & yours does not.

Hi @Herder,You say 'click the CTAs', so is there a reason why you are using Enters Viewport instead of the Click/Mousedown events? 

I imagine it's not in your purview, but I'd strongly recommend using Mobile SDK for the app or pushing your team strongly to do that. It offers so many app-specific features that will enhance reporting. Failing that, depending on how your app is built, standard web tracking may not work correctly fo...