Hello Adobe Analytics Community! Welcome back to the Tuesday Tech Bytes Series!  We had an excellent learning and engagements in Tuesday Tech Bytes series 2023. We are happy to continue the series this year as well! Tune in every Tuesday for a new discussion with our community advisors! Week 1 - Gol...

CJA doesn't yet support summary level data sources.  They've announced that support is planned - stay tuned.  

Thanks for sharing the cause!  That's always helpful for the next person who runs into a similar issue!  

Thanks Ankit. This particular use case was a bit different.  The client wanted to deduplicate metrics based on a couple of other dimensions (not at the person or session level).  I ended up using a concatenation derived field that is set only on the desired event.  For example, when cart add happens...

In CJA, I'm trying to replicate a report a client has in another Analytics tool.  I'd like to be able to turn off total deduplication for certain freeform tables.  I thought there was a setting to do that, but I can't seem to find it.  I know when you only display certain rows, remove a row, etc. de...

Adobe's definition is a visit with only 1 hit.  In many cases, the first page view by a customer can send multiple hits.  For example, perhaps a page view hit fires.  Then another hit fires shortly after when an automated element appears.  By Adobe's definition, this wouldn't be a bounce since there...

I think you could do something similar to this with a fallout.  Here's an example from sandbox demo data. First bar is all visitors (can be removed if desired) 2nd bar is those that had a page view on any category 1 page 3rd bar is those that had a 2nd page view on a category 1 page 4th bar is those...

Derived fields look at the row level data in the connection.  Persistence and other settings are applied at the data view level.  At Summit I believed they announced some new functions were coming to derived fields, including looking at changes from previous/next hit.  Not sure if this will solve fo...

Differing attribution models will yield different results. Your list variable is set to full attribution and to never expire.  This will result in full credit being given to each value that's ever been recorded for that visitor.   In workspace, you can use Attribution IQ to compare different models....

Hi @VidhyaAk1, Thank you for sharing those dimension settings.   With your current settings, for eVar80, all credit for the click will go to the last touch. For the list var, full credit will go to each touch that's been seen for the lifetime of this Unique Visitor.  For example, if someone has had ...