Yes, the rule was included as part of the library. The custom code was similar to the placeholder text, where I was re-writing the values for Analytics eVars.  I had an if statement that handled different cases, and commented out a line. I checked that the code was still valid. Also cleared cache in...

I'm finding that changes to custom code are not publishing when building a new property. I'm applying Custom Code within an Update Variable Action. Any changes from the UI are taking effect (updating the data Data Element), but any changes made in the Custom Code area are not applying. I've tried to...

You should also be using Update Variable prior to the Send Event. In that Update Variable, you can also set “viewName” in web.webPageDetails.viewName.

Adobe allows for modifications when the URL has changed. Target only knows the "page" from the view name. Are you setting the view in the XDM object via an "update variable" action? The view name should appear in your XDM request and in the decision scope. Though it sounds like you aren't seeing it ...

Yes, you are correct that the two tests will generate their own splits for their respective variants. There will be cross over / cross contamination between the two tests. Test 1 Variant A could see Test 2 Variant A/B/C. If you want the traffic to be mutually exclusive, where there is no cross over,...

You'll need to be provisioned for A4T. Details are available here:https://experienceleague.adobe.com/en/docs/target/using/integrate/a4t/a4timplementation For server-side, the A4T implementation with server side, please refer to this document:https://experienceleague.adobe.com/en/docs/target-dev/deve...

Hi, The Delivery API document has a limitation where it does not process redirect calls:https://experienceleague.adobe.com/en/docs/target-dev/developer/api/delivery-api/known-limitations If you are looking for the response from prefetch, some examples are available here:https://experienceleague.adob...