This help doc gives a good overview of when/how to use multiple audiences

One option would be for you to create all the combinations yourself.So you would select the containing div as location 1, edit the html to change the background image, h1, body copy & CTA; if you have control + 2 variations of each element then that would be 12 in total. It is a more manual option, ...

Yes, you can do that, I just wanted to make you aware that there are different latency considerations, depending on how you have implemented Target, when you are using AEP Segments.Have you seen this example that describes how to integrate Visitor ID (ECID) & Customer ID (Integration Code)?

Yes, exactly, the Metric configuration would look like this 

You could use the following if you've implemented Web SDK with XDM alloy("sendEvent", { "type": "decisioning.propositionDisplay", "xdm": { "_experience": { "decisioning": { "propositions": [{ "scope": "xdmClick" // Or any mbox/location ...

This document gives a good overview of how at.js functionality translates to Web SDK, including event tracking

I’ve raised this with one of our Technical Writing team who will submit the update request to the relevant team, as well as flag the issue internally to ensure we avoid further occurrences. Should expect updates in a matter of hours but can't guarantee exactly when that will be.

If you're passing thirdPartyId then the visitor profile attached to that thirdPartyId is what is qualifying for the activity. This means that, even after clearing cookies, cache etc, if the same thirdPartyId is present in the request to Target then those qualified activities will be served again.So,...

I don't believe Activity URL is available anywhere via API - in case you're open to alternatives, you could configure an event listener based on the Content Rendering Failed event (more info here) and then send an event/notification to alert that the failure happened

At a high-level, if your activity URL is www.foostg.com then it of course should not qualify a visitor on www.foo.com. However, the devil is in the detail with these scenarios i.e., you will need to provide the full configuration with actual URLs etc, so I would recommend creating a ticket with Cust...