Hi - the PDF linked to is giving a 404 error - do you have an updated document address?

Has anyone advice or experiences you can share around creating a shareable dashboard view of live test KPIs - ideally through native Adobe tools, but will also consider API integration? As our volume of activities grow, current methods of manually transferring into other tools for reporting is makin...

Sorry to unearth a two-year old post - but i also cannot find any documentation about these pre-built audiences.Specifically i want to know what the definition of a "test" is here, does it cover all activities types,(including XT,s and recommendations for example) or just A/B and MVT "tests".Perhaps...

Yes that should work. You can define multiple elements from different pages within a single goal so triggering any of them is a success.Only other consideration without seeing your form is if you could potentially have people clicking/tapping a submit button but then failing to proceed due to any fi...

Agree with Eric 's answer here - Unless there's something more complicated going on you have not told us about then your conversion goal is the same in both experiences, so "viewed a page" where page = abc.html will work fine.You could also use a click goal instead, by selecting the appropriate diff...

Thanks Eric, The A4T considerations were raised from here- Redirect offers - A4T FAQ but will give your method a try and see what happens in the data. We manage mbox cookies at a domain level, so i'm hoping the as we are only changing subdomains, these should persist as if it is a single website.e.g...

Thanks for the detailed response Eric. Feels like we are on the right lines.A bespoke redirect in JS would give us more flexibility, although I thought from what i'd read is that only the out of the box redirects keep the data in synch between both the Mbox and Analytics calls firing correctly at di...

Hi, Has anyone had any recent experiences, or advice to offer for configuring a multi-page redirect test between two sub-domains? The concept is fairly simple – but I am anticipating some complications in achieving a robust test. It could be thought of as a/b testing a new version of an entire eComm...

No worries - I figured it out it uses $criteria.title. Would be helpful to have this kind of specification in the documentation (unless i am just missing it) rather than through trial and error.

Hi - Did you get an answer to this issue? We are about to launch first recommendations, and can't find anywhere that explains how to define this in the design code so that this "display title" is output in the recommendations markup. We can hard-code a title for launch, but would ideally use the sam...