Typically I've seen customers coming up with a proxy for a bounce and sending an event with a named mbox to Target when that thing happens i.e., time spent on page or an interaction indicating engagement. You could then configure your goal as "Conversion -> Viewed an mbox -> <named-mbox>". By no mea...

If you can load the URL without the Target QA parameters, then it might be that the web server has been configured to only accept certain query string parameters. So it would be worth talking with the web app/hosting team to uncover whether that is the case or not

You might have already seen it but is this help page useful? And also the page it links to relating to the statistical calculations?

Not exactly sure how you're making the changes currently but I'd suggest using the "Layout > Rearrange" VEC action if you just need to change the order of the cards, as this should preserve any event handling logic that is attached to the elements

There are probably a couple of options:i) Specify mutually exclusive audiences e.g., Bath audience is defined as "if in bath audience but in no other" etcii) Prioritise the audiences where there is overlap e.g., Bath audience is defined as "if in bath & tool audience" or "if in bath audience any any...

If the URL works without the auth token query string then it may well be that the web server has been configured to only accept certain query string values, so you might want to check with the team responsible for hosting the website 

Quick update here that the forthcoming Target release (between 22-24 Jan depending on region) includes a fix that caused Important Attributes reports not to display (see pre-release notes here)

My understanding is that the event will only be shared downstream to the Target service if it includes a value in the decisionScopes array. So the documentation looks like it might be misleading.A code example would be: alloy("sendEvent", { "xdm": { "commerce": { "order": { "purc...

I think the first option would only work but only if you added an exclusion rule within Page Delivery settings e.g. Activity URL "www.home.com/member-portal" and URL is not "www.home.com/member-portal/". Your audience example would also work though.

It should of course work across all browsers but have you tried in another browser to see if the issue persists? If so, I'd recommend raising a ticket with Customer Care so they can troubleshoot in more detail