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...
There are a couple of different ways you could do this:i) Wrap the template code in some conditional logicif(typeof sessionStorage.displayed === "undefined"){
sessionStorage.displayed = "true"
//add your template code
}ii) If you want more control (i.e. a certain number of minutes, hours) th...
Did a bit more digging - you can actually access user.endpoint.lastViewedEntity (including all historical last viewed entities) via profile script. So a simple example would be:var lastViewedEntity= user.get('endpoint.lastViewedEntity')+"";
if(lastViewedEntity != 'null'){
return lastViewedEntity;
...
Ok, one thing to be aware of is that same/next page personalisation isn't supported when you're not interacting with Target via the Web SDK/Edge Network. So even if the implementation is correct, it would be supporting next-session use cases due to audience qualification latency (more info here).If ...
That user.endpoint.lastViewedEntity parameter isn't available "out of the box" in the audience creation workflow. However, you can access it quite easily via a Profile Script. If it's only the single most recent entity, your profile script could just be something likevar lastViewed = mbox.param("ent...
Sounds like the Target implementation might need reviewing. Is the checkout flow a Single Page Application or a "traditional" website where clicking through each step involves the page fully reloading?
Based on your description, you're not qualifying for the Audience you have applied. It might be that you need to pass some additional parameters but that depends on your audience. What is the Audience definition? If you do need to pass some additional parameters then you can refer to the Delivery AP...
Yes it is normal, both options are displayed to all customers in that Implementation section. The reason being that some customers will still be using v1 and there are certain functions, for example, that were deprecated in v2.When you're using Launch, the methods/versions in the Admin > Implementat...