It sounds like this example of how to use getOffers, applyOffers & triggerView in sequence might be what you need

If the data in both Analytics & Target match, then it could be a problem with Target not loading in certain situations. A few things that might be worth checking:i) If you compare the 500k that visited the page vs the 100k that saw the Target activity, do you see any obvious differences? i.e., 30% o...

Ok, so if you take the CSS selector that's being used in the modification in Visual Editor, visit one of the pages where the change doesn't work, and usedocument.querySelector('your-css-selector')Does that return an element? I.e., it doesn't return null

A template rule of, for example, "URL contains /content/a/b/c/" should work fine.There are two things that might be happening:i) You're not qualifying for the activityWhen you visit, for example, /content/a/b/c/d.html are you entered into the activity?-You can check this in the response from Target....

That kind of personalisation/decision management with ranking/prioritisation is very much what Offer Decisioning is designed for, with capability to support across multiple channels. Web & app are two of those channels, which is where the integration between Offer Decisioning & Target comes into pla...

Yes you can do this, but you would pass the value as an mbox parameter and then use a profile script, which would create a profile attribute which each new value would be appended to. In the example below, there is an mbox parameter called "append"; if it's not the first value my appendScript profil...

I'd suggest applying a QA segment to the activity (e.g. URL query param contains qa=true), activating the test, and then going to the URL (e.g. www.mytest.com/testpage?qa=true) to see if the issue still persists. The QA URLs work very well most of the time but occasionally can throw up issues that o...

In that case I would consider tracking that promo pop-up click in an eVar, as this will then persist from pop-up click -> booking screen -> summary/payment page -> success page. Then you could create a funnel to understand initial engagement effectiveness (i.e. how many click the pop-up) as a micro-...

I've seen this problem caused by one of two things:i) If you were using mbox.js and then migrated to at.js, this can result in 2 mbox cookies being set, one of which has the correct structure that at.js is expecting, the other which has the old structure that mbox.js expects-one solution is to add s...

I originally thought you wanted a single metric that could represent "clicked button and reached success page", so that's why I'd suggest the other approach, but what you suggested makes perfect sense. If you don't necessarily need it to be a 2 step funnel, another option would be to add an internal...