Hi Andrey:
Thank you for responding.
You are a breathe of fresh air in the smoke screen that is Adobe documentation (or lack thereof).
This is exactly the same conclusion I came to a few days after posting, despite those around me.
Everyone (including my Adobe rep) thought I was crazy- but no one could explain why it wouldn't work.
Thank you so much for the validation.
I still have to work out the details of how to send the info from the previous page events to the correct page without incrementing the PV.
Also I didn't know there was a way of capturing the exit page info using the unload event.
Have you used this method effectively in production? Can you address Itaparia's concerns?
One detail - in case anyone references this solution- is to validate local storage is available.
Do you think this is required, or is the amount (of local storage failures) incidental?
Below is some code I found to validate that local storage is available try/catch
God only knows what Apple and others will do next.
And yes I notice you reset when done, like a responsible developer
I am concerned a poor developer down road tries to troubleshoot this- and can't recreate the issue
var hasStorage = (function() {
try {
localStorage.setItem(mod, mod);
localStorage.removeItem(mod);
return true;
} catch (exception) {
return false;
}
}());
Thanks Again Andrey!
I wish I could afford your Launch Course as you clearly know what you are doing.
Glen