Based on the details provided, a common root cause is a redirect. When
this happens the original referrer is often dropped, resulting in an
internal or blank referrer (direct). Have any tests been run to look at
the image request of the landing page? Check the referrer information.
Hi, I was reviewing some older posts/questions. I assume you have
already found the answer that the "splitting up" and persistence of list
var values will come after any edits made via processing rules.
One point of clarification: Andrey's suggestion is spot on for finding
users that have every been to your tracked property before. If the
question is return visitors *during* the selected date range, you'll
need to create a sequential segment to look for visitors that had more
than 1 visit.
Hi! While I am not sure I fully understand your use case, I don't think
you are missing anything. This kind of analysis / segmentation /
calculate metric is not really possible with the product variable. This
is because the product string is a 'list Variable'. A segment pulls back
the whole product string when at least one product matches the segment.
So, there is not really a way to say 'THIS, but NOT THIS' in a product
string. For example, if you had a product string of: "ProdA, B-Product"
Since the product string is a "List Variable" (a variable that can hold
more than one value at a time), such a segment will return the full
product string for any production string that had at least one product
with more than 10 units. So, there is not a way to create such a segment
and ONLY get units over 10 back, unless the product string ONLY
contained that single product with more than 10 units, and had no other
I am not aware of any sandboxes (unfortunately).One thought is to ask
your future opportunity for an Analytics use login before you start. I
also might suggest reviewing the Adobe Analytics Youtube channel:
https://www.youtube.com/channel/UC8I6bqCk7gO6YdoMz6W5fvw .There are also
paid trainings here:
some of which might come with short-term sandbox usage.
Adobe Analytics needs at least two image requests in a visit to
calculate time spent. Time spent will continue to count event when a tab
is in the background, *only if* the user comes back to the tab with 30
minutes and causes another image request. Another way to think about
this is, the last page/hit of a visit will not have time spend