Ahh, yes.. easy mistake to make.. I thought the same thing years ago when I first started trying to use it... but when you think about it, since it's basically a value associated to the visit, that it only changes with the new visit.   Glad I could help, and I'm glad the plugin is working as intende...

I am not sure how the getNewRepeat has been updated for WebSDK, but for quite a while, I didn't find that it work well on AppMeasurement.js.   With AppMeasurement, client side cookies were created... but even though they are first party, they are JS set which lowers the authority on them, and with S...

I should add... when it comes to CJA, basically you can just configure your variables with the properties and attributes as needed... they basically have done away with the specific naming conventions of "prop" or "eVar"..    The most important aspect is ensuring that you are using the correct attri...

I second this... eVars with Hit expiry act just like a prop.. I have many such eVars, I also still have props.   Here are some of the biggest considerations that I follow:   Props These are hit based, with a max character count of 100.Props can be made into "lists", so long as the overall count does...

The "within 7 days" should be exactly as you described... you are pulling back sessions with E1, where the visitor did E1 then E2 within a 7 day time frame.   Now, I don't have CJA, but the principal should be the same as in AA.   The segment itself is looking at a Session scope (which should be the...

As @Harveer_SinghGi1 mentioned, in the Post Product List, you will see the backend Event ID (rather than the "readable name".   You should also be aware that all merchandising eVars will be listed, even if they aren't used in that context.   Empty eVars will show ::hash::0

The problem in your segment is that you are looking at the "Within 7 Days" inside the same session... Which isn't the case, a session is not going to extend for days.   You will need to stack containers within the segment to accomodate that within logic at a Visitor or Person level.     So, if you w...

Hi,   1. Yes, if you see data associated to the bot, that counts against your server calls, but they will not be counted in any of your standard reports.   2. Yes, though most dimensions are not available with Bot Page views, the Page dimension is available to correlate with the Bot Page Views metri...

A Hit is a Hit... it doesn't matter if it's a Page View or an Action... unless you are using the Page View metric... but if you use the Occurrence metric  it will capture any hit that is the first of a visit.

The Operating System Type should be included... but it's possible that there some User Agents that aren't mapped, but more likely, some bots don't get mapped...   Can you share a few examples of what you are seeing in the OS data?