We created a custom unsubscribe page for a email template that encodes subscriber information when clicked. The unsub page URL contains a
? - normally, not a problem. However, the account has web analytics connector turned on. Normally also not a problem, as any URL that contains a
? the analytics connector will know to start the string with a
& instead. However, the
<a href tag in the email template doesn't point a subscriber to the direct URL (due to the subscriber info encoding), but rather the CloudPages URL string. For example:
<a href="%%=CloudPagesURL(6)=%%" alias="unsubscribe">.
So, when a subscriber clicks on the Unsubscribe link from an actual email deployment, it redirects to a 500 Error page.
Without the WAC appending to the URL, the URL looks something like this:
With the WAC appending to the URL (causing the 500 error), we see this:
You'll notice that after the
qs= value there's a second question mark - if we manually change it to an ampersand, it fixes the 500 error and the custom unsub page loads as it should.
So, the question is - how do we fix this to become an ampersand instead of a question mark, as we cannot remove the WAC? Or, is there a workaround solution to this?