@prathap08 I don't know how the page is set up, but would a rule set to execute on History Change do the trick? Another option might be to create a data element that watches for URL/parameter changes, then trigger the rule using a "Data Element Changed" event?Details on these actions, and others: ht...

@prathap08 - If this is still an issue, feel free to tag me and I'll offer up some guidance. The problem, as you know, is that it's a non-standard URL. You'll need custom code to extract the key/value.

Hi, @Hey_John Typically, geolocation details come from the visitor's IP address, which is where the existing "Countries" report gets its data.The reason "state" and "zip" are supported by Data Sources is they are commonly/typically associated with transactional data such as an online purchase. In fa...

Hi, @Saravanan_Dharmaraj -A few thoughts for you:In the event rule, have you tried adding the "Clear Variables" action (using the Adobe Analytics extension) before populating the desired props/eVars/events and sending the call? This would give you 3 actions in the rule: Clear Variables + Set Variabl...

@ng772 You can only reference event.detail properties in the direct call rule itself, and the values are specific to each time the DCR is called. (Is that what you were asking?)

~~~

With the alloy.js library, I'm looking for a way to get the imsregion. With visitorapi.js, this could be done in a couple of ways (visitor.getVisitorValues(), visitor.getLocationHint()), but I'm not finding a way to do it with alloy.js. Am I just missing it, or is it not a feature yet?

@raj_mandalapu - Assuming you have control over the implementation, you can do what @vibhatna suggested and remove it entirely from pages on the offending domain. Another option might be to leverage s.abort as part of your doPlugins logic to stop analytics calls from firing only when/if it's the off...

@ng772  - The extra information you pass should be unique to each call. If you call two DCRs in rapid succession, and each DCR has a unique payload (event.detail), the values available to each DCR will come from their respective payload, setting the correct (expected) values. For your last question,...

Hi, @Luca_Lattarini - I would suggest tracking all selected options when the form is submitted. Capturing the data in either a list-enabled prop or a listVar would make it so classifications (for breaking the data apart) wouldn't be necessary.For example, either of the following approaches would let...