@RonMahoney I'm not quite clear on what your question is. You can swap out the colon with any of a number of characters, including the tilde (~) or an underscore (_), for example, but you'd be doing that in the actual tracking code that gets included in your links/URLs. Then, in the Classification R...

@LGalliers - Can you provide some sample rows? I'd be interested in seeing the key and related classification columns for a few records. I'd also be interested in any error messages you're seeing telling you that the classifications are failing. This information will be helpful/necessary to help tro...

@prahme  -It certainly is possible. You'll just have to use a regex match in the rule, then reassemble the parts to build the string you want to see in reports. Your regex may vary, but the simplest approach would be something like the following: This assumes we're looking for the "Homepage" value, ...

@Luca_Lattarini  - It depends on what you're trying to do.Do you need to capture the information when it is selected, sending a call to Adobe any/every time the selection changes? Do you need to capture the selected value when a form is submitted?Could you capture the information on a subsequent pag...

@dillonb16317612 - This has long been a challenge in Adobe Analytics, so I hope you get some traction with this request!One suggestion I'll throw out (and others will likely offer similar thoughts) is to include the variable identifier as part of the name. Most implementations I work with use schema...

@Luca_Lattarini - That's a somewhat loaded question. There are multiple factors that will impact how long it takes for data to show up in reports. I'd suggest going through this article on Current Data and this article on latency.  At a high level, though, Adobe offers the following estimates:  

Good luck. If you're still stuck after consulting takes a look, feel free to DM me a URL where the problem is and I'll poke around to see if anything stands out.

@tbaker73 - My suggestion was to only trigger the s.tl() when you knew the s.t() had already fired. One way to accomplish that would be with a simple flag and an interval as in this simple example: https://gist.github.com/hitGovernor/dc3e7120830a9feaea16c6840715d36c

Assuming you just need to fire the extra s.tl() call once after the initial page load call, you could just set a true/false flag to false before initiating the page call. Next, either with a Promise, or setInterval(), watch for the flag to become true and fire the s.tl() call when it does. (Take car...

@pwolly-cr  - Have you considered s.registerPostTrackCallback?https://docs.adobe.com/content/help/en/analytics/implementation/vars/functions/registerposttrackcallback.html