Activity QA link in Target is firing the experience twice

[andywoodrow]

When testing a page wih the Activity QA link in Target, we're seeing the experience fire twice.  We are using AEP and there is only a single window-load based rule that allows a decision to occur, so in theory there's only one page load so the experience should only really trigger once.  Does anyone know what may be happening for it to fire twice?  I've just got a console.log output being sent at the moment

Cheers

[alexbishop]

When you say "experience fire twice", do you mean that you see 2 requests to Target, and therefore the content returned from Target is rendered twice? Or a single network request to Target but still the content rendered twice? And do you see the issue if you don't use the QA link? e.g. if you apply a <URL contains "testqa"> audience to your activity, activate it and then visit it by adding testqa as a query string to the end of your activity URL: www.page.com?testqa