Yes, this is expected behavior. As I responded to someone else earlier today, there is no guarantee that the session cookie will be associated by the next pageview. While association typically only takes a couple of seconds at most, it happens asynchronously not interlocked in any way with the next HTTP request.
Marketo LPs can also read values from a read-your-write cache, designated by the aliId query parameter, instead of from the cookie-associated lead. The aliId would normally would take care of your concerns here, but you're stripping it out on /demo-request-2.html with this piece of code:
$(document).ready( function() {
url = "https://get.asknicely.com/demo-booking.html";
$( location ).attr("href", url);
});
(Also, $(location).attr("href",<url>) isn't really the way to do this, it's location.href = <url> -- and no, those aren't the same!)
I don't know why you're waiting until .ready (DOMContentLoaded) on the interstitial, but assuming that part is truly necessary, you want this:
$(document).ready( function() {
var redirectLoc= document.createElement("a");
redirectLoc.href = "https://get.asknicely.com/demo-booking.html";
redirectLoc.search = document.location.search;
document.location = redirectLoc;
});
Adchoices