Hi @Luca_Lattarini , this looks like an error in some custom code (or erroneous extension).In particular it looks like someone is referencing a promise that has never declared (e.g. promiseEG.then(()=>...., by default promiseEG would be treated as a null object if not declared properly and the inter...

A lot of the issues you mention (e.g. slowness) are likely due to outdated API built around the processing rules CRUD. It may be worth supporting the requests for updating the API on the ticket, here, which would also enable easy fixes in the UI.

Hi @Brian_Kent_Watson , you mentioned that "API support is not available in API 1.4..."It is available it's just not very useful and requires inconvenient text parsing. Outside groups have had to compensate for this poorly written API.

Hi @prathap08 ,If you are setting it into prop2 with document.location.href you can use the following javascript to set the variable:s.prop2 = document.location.href.replace(/([^:])\/\/+/g,"$1/"); This will replace every instance of repeated "/" unless directly following a ":". Note: If you are use ...

Additionally, @Luca_Lattarini , you may also want to exclude the permissions that are company-wide. Even though it is less convenient for the vendors since the ability to Manage Properties means they cannot create their own properties, they also won't be able to reconfigure/delete them.

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.