If the data type is a string, you can't do math with it in CJA.  You can cast as an integer using data prep, but that's only for new data after you add that mapping. Alternatively, you can use Report Builder to get the numeric "string" into Excel.  There you can use it as a number.  Hope this helps!

Description - For all datasets, allow the ability to force lowercase all or certain fields. Why is this feature important to you - Currently, if the casing in matching keys doesn't match exactly, enhancement data from lookup and profile datasets isn't available in CJA. How would you like the featur...

Ah, good point on that. Are you limiting your date range to after your rules were updated?  I'd try to use visits as a metric also to see how that compares.

Hi @robinl39529461  - the occurrences in yellow include persistence.  But when you filter for just instances (hits where the marketing channel is set vs. where it persisted), you've got a perfect match!  (The delta between the two would be the impact of persistence.)

Have you made any recent changes to your marketing channel processing rules?  It's hard to tell but it looks like the sparkline on the organic search has dropped off recently.  In AA, updates to the rules aren't retroactive.

I agree with what @abhinavpuri suggested.  With some clients, we've also built out specific criteria (for example if a visit has 2+ page views or includes a certain engagement event it's not a bounce).

hi @Abhishek_10  - see Claravine's documentation on setting up the AA integration.  It's easy to set up and works well once in place.  However, note that Claravine doesn't currently have a similar CJA integration, so you'll need to set an export from Claravine to a cloud service & set up your own in...

The components might be metrics and/or dimensions.  If you're getting that error with less than 5 components (metrics + dimensions) based on derived fields, I'd open a ticket with Adobe support.

I agree @JohannaAc - as a note, you can create a calculated metric version of the per person and per session metrics.  Just updated the formatting to display hh:mm:ss. These can be shared with everyone if desired.

Hi @Kim_Reynolds - I tried this in a sandbox and it worked.  Set the top rule to RegExp ^[^\|]*\|[^\|]*\|([1])\| v99 as set classification and "Native" (if the 3rd element contains only 1, then it's true and Native will be set) Set the next rule to RexExp ^[^\|]*\|[^\|]*\|([^1]) v99 as set classific...