Hi @tomo_xxx ,You may want to check several things before looking for the AppMeasurement.js file.1. Make sure that the implementation code is being hosted on Akamai because otherwise it may be coming from a different source altogether. You could start just by checking that there is a assets.adobedtm...

Hi @josed30633309 , There are too many things that could go wrong with the given regex. You may want to make it a bit more robust.Just as a starting point you should change how your "Or" logic works with a non-capturing group and there's a rogue period that was probably meant to be escaped:e.g. (?:....

@c1553, I forgot to mention. If you're doing click tracking, s.tl(), calls, you'll also need to set s.linkTrackVars string to include each variable to send with the beacons, ref.E.g.s.linkTrackVars = "propx,evary,evarz";

There are many benefits, flexibility, and conveniences for other projects/developers to just continue using context data and using the Analytics processing to do the mapping, as @yuhuisg suggests. However, to answer your question, it is relatively simple to set the variables directly in custom code ...

Makes sense, it's probably worth finding a permanent solution. However, if you are going the re-direction route, you'll need to do a check on each page to not fire a beacon unless the double "/" are absent. Best of luck.

Hi @prathap08 , this is also a work around, but give you better data going in. Try manually reformatting the text in custom code.E.g.  s.registerPreTrackCall(function(){ s.prop2 = s.prop2.replace("\/\/","\/"); }); Or, if you are using context data/pagename it would look similar with the correspondin...

So my team doesn't use very many counter evars either (I'd be hard pressed to find a current example, but I know they exist). As is the nature of any visit-based evar, their convenience is their ability to tie-out to events/metrics that don't necessarily happen on the same hit. So if you had a speci...

Hi @prathap08 , This is a hack, but if the bad data is already collected you could clean it up using a classification.That is, for each domain, create a Path variable and define it using classification rule builder similar to the following:\/*([^\?]*)\??.*$ Mapping $1 to the new variable.

@k26123612 , Please see other questions related to API permissions:Thorough Example In your case, it depends on auth type. For OAuth, you need to restrict the user to just the report suites they can use API on. For JWT, you can create a product profile containing only the report suites needed. Furth...

As per @MSchoenmakers-Signify mention of the bug, the workaround that I'm using is as follows: On Library Load, I'm updating the s.t() function. var tempTrack = s.t.bind({}); s.t = function(e,t,justInCaseParam,justInCaseParam2){ tempTrack(e,t,justInCaseParam,justInCaseParam2); someOtherPostB...