Well, yes and no.... A 301 redirect with a long TTL, depending on how long it was in the wild, definitely wouldn't be good! It won't cure itself for those people who are affected, and you can't force it to. (Same with a long-lived but broken HSTS policy that was user-facing for more than a few minutes.)   Of course, as you say, if it truly only affects a couple of people that's fine. But hard to measure the impact in a martech context — you won't have people calling the Help Desk if an LP doesn't work! ... View more

The only solution which on my mind is to use tokens, but I hope, we have another solution.  Actually, tokens aren't a solution, because when the visitor hits the Thank You page, they can still be anonymous (the association of the underlying cookie from anonymous → known doesn't happen immediately but later; even if it's one second later that's too late).   Don't know why you wouldn't use tokens if you could, though. What would be wrong with tokens, if they were guaranteed to be available?   In any case, this logic requires JavaScript. You would calculate the appropriate show/hide logic on the LP (not the TY) since it has direct access to the just-submitted values. Then append the show/hide info to the URL of the Thank You page (i.e. in the query string). On the Thank You page, transform those query params into CSS classes.  CSS handles the show/hide (display: none;).   ... View more

Hi Hanna, Thank you for the answer, I know it should happen like this but I did not understand why I cannot see the opportunities. But since then I found the answer - I can see only the open opportunities. (and I checked the closed) Thanks again ... View more