@Dsantoro If you are looking to A/b test during the time period, then create the a/b experience and when you get to the "Targeting" step in the three step workflow, the step where you change the traffic split for the activity, click the three dots and select replace audience. You can then create an ...

I would add an additional parameter to Page A if the user lands on it organically to pass into the global mbox a parameter like "notReferred=true" then in the experience set the condition to be referred from Google and notReferred is not present. This means you need to have logic on the page that pa...

@Roxie423 have you tried in the same browser as where you are authoring the Target experience to open a separate tab(in same browswer) and logging into the page? The same cookies should be used in the Target tab when you attempt to edit the activity and as a result not ask you to log in. This is ass...

@Kishore_Kumar_ You have to set a specific URL if you are going to use the VEC editor, i.e www.example.com/shop/laptop. Then under Page Delivery for the activity you have to set the contain rule and set it to the domain, i.e www.example.com. Make sure to set the condition to OR and also make sure th...

You are correct, you will get an error if you attempt to do so. A possible alternative is firing another rule in Adobe Launch if you are using it. For some reason you can fire multiple Target global mboxes using Launch but not using getOffer/applyOffer. I asked Adobe for information on how this work...

Sounds good!

@rrrrrraul Install and initialize the Node.js or Java SDK with decisioningMethod = on-device. https://adobetarget-sdks.gitbook.io/docs/getting-started/java

@ambikaTewari_ATCI I see what you are doing here but I dont believe there is enough documentation on how this will work and how reliable it can be long term. The function "trackEvent" is meant for reporting so if Adobe scraps it and uses sendNotification instead you will need to pivot. It's a big "i...

You can also use "adobe.target.getOffers(options)" available with at.js 2.x. Create separate experiences for each of the offers, fetch them all and then only fire the adobe.target.sendNotifications(options) function when you figure out in your code within the page which offer to show.

That makes sense but then your metrics will show high impressions and unless you have something else tracking what offer was actually displayed your analytics will all be bunched up. I would recommend that if you are going to go this route that you still create the "child activity" but only use it f...