The Issue: Our organization is seeing a 25% opt-out rate triggered by Gmail/Mimecast pre-fetching. Presumably, the ${l://OptOutLink} processes the unsubscription on a GET request (the initial link crawl), the user is unsubscribed before they even see the 'Confirm' button on the interstitial.
The Request: Can Qualtrics update the Opt-Out workflow so that the database change only occurs via a POST request (i.e., when the 'Confirm' button is actually clicked)? This would align with modern web standards for protecting user intent against automated crawlers
