Unfortunately, your options may be limited if you're trying to stay away from AEP. I recently went down this route and decided the best option was indeed to go with the AEP React Native Wrapper (despite the client not using any other part of AEP, or preparing to be on CJA); we had the developers sen...

I accidentally duplicated this- https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-data/add-the-rule-name-in-the-search-results-drop-down-in-the-tags/idi-p/439020 .

adobeDataLayer.getState() is different from just looking at the most recent event in adobeDataLayer... it can show things that aren't present in the most recent event. So if you have something like "event2:true" in your first page view event, and event2 isn't set at all in your second page view even...

If it were the plugin, I would just suggest switching to the OOB report. There didn't used to BE a built-in "visit number" dimension, so people used the plugin, but now it isn't needed. The downside with the plugin is it uses its own cookie that exists separately from (and isn't quite as reliable as...

Well, shucks. Had it been the plugin, that would have been as easy solve (the plugin is based on a cookie that doesn't last long on safari).How do you get the Visitor ID? It's (annoyingly) not generally available in reporting without folks doing something custom. 

Is this the built-in Visit Number dimension, rather than the now-not-really-needed getVisitNum plugin?And by Visitor ID, are you referring to the ECID (or MID or whatever we're calling it today), copied into a prop or eVar? 

Cookies are a key part of Analytics, so I'd push back and ask what the goal is of not having cookies. The anonymous identifiers in its cookies help Adobe keep track of the user as they go from page to page, and session to session. They are the basis for Visits and Visitors metrics, but also for any ...

I think my eventual findings are similar to where you seem to have arrived: a list var (if available) with hit expiration (if a list var is unavailable, a list prop might do). And, like @yuhuisg , I try to focus on errors that impact the user experience, and what the user sees rather than what the s...

Attached is toolkit #5. It covers a kind of random collection of useful things:The AEP Debugger (which has a lot more to do it then you might think- the "track data layer changes" feature can be very handy (though I don't think it works well with event-driven data layers)).Activity Map (this was als...

Attached is week 4's Toolkit, sorry it's a little late. This toolkit goes more deeply into Launch Tags- setting up, publishing, extensions usage, etc. Let me know if you have any questions!