Hi @a_akande,   I can replicate your example if instead of pulling the "Hour of Day" over as a whole (dynamically populated values in the breakdown), if I open "Hour of Day" to see the values, then select the list of items.       Or if after I bring in the full dimension, I use the "display only se...

I agree, this should work, since this plugin basically just stores the value as a cookie (with a 30 min expiry), then if the cookie exists track the value, if it doesn't, it assumes this is the first page in the visit and doesn't track a value.

Hi, we too sometimes have actions that fire (we used to have more), but as such, we also don't use Adobe's bounce definition because it's based on server calls.   We did a simple solution.   Adobe does have a metric called "Single Page Visit" which we use instead for our "Bounces".   And for "Bounce...

As others have mentioned, the hash is not a part of the query string... however, you don't have to encode the value in your URLs to pick it up.   This could could break the expected functionality of the hash, also known as a URL Fragment). If this was actually being used as a URL Fragment.   I can't...

Timing issues are always tricky...   I haven't switched to WebSDK, but I have had my fair share of trying to align timing between site code, third party integrations, and Adobe...   In Launch, I believe the standard timeout in most code blocks is 2 seconds (or 2000 milliseconds). In each Action, the...

For me, I need a lot of hit based variables... more than can be covered with 75 props... so shorter for values like "page type" or "asset id", I use props. For longer values, but still something I only need at the hit level, I track in eVars with Hit expiry, but make use of the longer 255 characters...

I think that is more of a "general best practice"... as in, if you are using WebSDK you don't need AppMeasurement (and you don't want to send traffic via both of these into the same suite, which would inflate your traffic and costs).... but in this case, for a short duration, you are intentionally t...

Absolutely,   Adobe does support multi-suite (different profile) tracking... I did this way back in the days before Launch was even a thing... we had to have different AppMeasurement (or was it s_code at the time) files, that made an alternate s object... so one suite used the standard "s" object, a...

I should update this answer.. with the newer Edge Server / Data Stream you can actually set values directly.   Whether you use the full XDM format, and map values in your schemas, or you use the Adobe Data model, where you can set your metrics and dimensions (props, eVars, events, etc) directly, and...

Honestly, there is very little need to pass the same value to both a prop and an eVar.. that was a popular implementation method back when we only had Reports and Analytics, and you we didn't have full correlation... with Workspaces, that barrier is gone...   However, that said, there are still a fe...