Hi @VirginieRe2 does eVar20 have persistence? If so, you may be seeing values that have persisted and were not necessarily set on the event 50. You can click the gear icon for event 50 and modify the attribution model to Same Touch. This will only give attribution to eVar20 values that were set on t...

You may be able to mark the dataset as enabled for profile. That is set within AEP. Lookup and Profile dataset types refer to how those datasets are handled within CJA specifically.

Hi @JaniceAk, I believe only event datasets would impact stitching. Lookup and profile datasets are used to enrich event dataset with additional information.

Hi @NicoleHa7, I tested it and I'm seeing the same as you. Logic group is not available. It appears this is a bug. I'd suggest opening a ticket with the Adobe support team.

One quick note, for those on Adobe CJA this is easy to implement OOTB. Usage analytics has details of what's available once it's set up.      

Hi @brentrad I believe this is a perfect use case for the new derived field depth function. In your derived field, first use a function such as Case When to filter for only events with Page Name. Then add a depth function to capture the results of those filtered events. You can bring this derived fi...

Actually Adobe just released the typecast derived field function this week that makes it easy! It's great to see the product evolving in ways that solve painpoints.

I'm not an expert on exactly how users could block analytics from being captured. It does look like ad blockers and other technology may do so or may strip out the query string params, though I'd presume there might also be ways to block the open & clicks as well.   There could be other factors such...

Hi @tthmx9  In your first container, you have OR between your two conditions. This means it'll look for visitors to meet either condition. And I notice that the first condition (days since last visit > 30 days) contradictors your last condition (days since last visit are <=30 days). If you use a seg...

It looks like there are some classifications that are expected but missing from the report suite. Do your web & app activities use the same report suite? If not, look to see what classifications the web reports are using and verify those are in your mobile report suite as well.