You can wait here with on document loaded - there is certainly also more elegant way.
function yourFunction () {
console.log("document loaded");
}
(document.readyState != 'complete') ? document.addEventListener('DOMContentLoaded', function() { yourFunction() }) : yourFunction();
You'll probably d...
I rather recommend a tool to evaluate the data. You can also access the reports via the Adobe Target API - but only raw data is stored here - no calculations. A tool can be e.g. Adobe Analytics (is of course recommended, because that is pretty smooth with A4T and is very good to evaluate). But basic...
Could you take a screenshot of the network tab - and search for "delivery" (or if you still have at.js 1.x search for "mbox") - and take a screenshot of that?
To me it just sounds like something is wrong with the timing. Especially if it works from the console - but not from target. Wait for document loaded or similar - and then execute your code.
You can simply write utm_source=google and in the next line google. You don't need to write an or - each new line is like an or.
However, I'm not sure if traffic sources is the right thing to do here. If you always get a utm_source=google parameter in the URL - I would use "Site Pages" instead of "T...
You can count indirectly via ProfileScripts. For example, you can count how many users have clicked between 0-10 times, how many between 10-50 times, and so on. Maybe this will help.
I am not sure if I have already understood your problem correctly.
In what order is Adobe Target loaded and when is Adobe Analytics loaded? Is it loaded synchronously or asynchronously?
Is the problem only the timing, that after the click - too fast is switched to another page? If yes or there i...