Without getting into Launch or viewing the behavior first hand, it's tough to say exactly what the issue is. My assumption is that you have more than one rule executing, and that is redefining your variables; including s.linkTrackVars.I would start with the following troubleshooting approaches:When ...
@vivek091195 - You're probably best converting the array to a delimited string ("Reading,Skating,Dancing") when you add it to the contextData object. Then, in your Processing Rules, you'll just assign the variable to the appropriate eVar/prop.
No. The cookies are mostly used to help with visitor and session identification, so even without them, you'd still be able to collect data. The usability/quality of that data would suffer, but you'd still be able to collect it. My recommendation for privacy implementations would be to simply block/n...
@CM128 - Different cookies serve different purposes, so removing some will have more or less impact than removing others. At a minimum, I'm assuming you'll want to keep the visitor ID-related cookies. The following articles may help you make the decision that is best for your use case: Analytics Coo...
"One edge in using dynamic variables is, you can see the variables where data is copied in your network calls. In processing rules this is not possible." Exactly. I spend much of my days implementing analytics and marketing solutions, and the ability to see exactly what is being passed/collected as ...
"If the marketing channel applies to the visit and my segment is to return visits of direct > PPC then surely the entry URL shouldn't contain a query parameter?" Assuming that your segment uses a visit container, I would agree with that statement/question. Have you double-checked that the segment is...
@vivek091195 - First, I want to make sure we're all defining "occurrences" according to how Adobe defines the metric: The ‘Occurrences’ metric shows the number of hits where a given dimension was set or persisted. [link] As it relates to conversion variables (eVars), this means that once a value is ...
@vivek091195 - Have you tried using the "minute" dimension? "Dimension items include a given minute within a report’s date range alongside its date. It is formatted as HH:MM YYYY-MM-DD. Dimension items starting with 00:00 equate to midnight on that day, while values starting with 23:59 equate to 11:...