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...

Perhaps for this specific URL you can disable auto global mbox and fire the getOffer/applyOffer function only when you have the HTML elements in place.

Yes, I believe you are speaking of going down the parent/child activity route where you introduce js code via a VEC activity targeting everyone that hits the specific URL. This js code then grabs the value and triggers a getOffer/applyOffer call and passes in the HTML elements as parameters. Is this...

Hey I dont see a response...

@rrrrrraul you could standup your own server side framework which has or can get your user data and then passes it to Target using the Target SDK versus doing it client side. From Adobe Target in house perspective, the only user data it retrieves is from within the experience cloud.  Here is the lin...

I think I need to understand more with what you are working with but if you can fire off an AAM pixel, then technically they will be in that segment. If you have Target and AAM integrated, then you can Target them on the site using the AAM segment. If you fire the pixel though on that same page load...

@ambikaTewari_ATCI On iphone there is an app called Charles, its technically the same app you use on your desktop but for your phone. You can use this tool to listen for inbound and outbound http request from the device without needing to use your computer as a proxy. Here you will be able to view t...

@Roxie423 There is a few ways of doing this I will outline the option I think you are seeking, and some alternatives I would recommend. 1. HTML Element Scrapping(What you mentioned)-  For this option we are running a script prior to calling Target to grab the value from the css selector that holds t...

Are the Target activities being segmented based on the placement value? If so what kind of taxonomy is used for the value? Perhaps you move the logic into the page prior to calling Target and then passing an mbox parameter with the placement "friendly name".