Privacy Reassurance Next to a Form Field A/B Test

Form completion rate

Compare registrations to see whether a privacy assurance affects completion.

• Field-level abandonmentCompare visitors who leave before completing the field with the assurance.
• Form completion timeMeasure time from form start to successful submission consistently.
• Privacy complaintsTrack recorded complaints about a mismatch between the assurance and actual data use.

• MessageAdd one truthful assurance next to the predefined field.
• Keep constantKeep fields, consent requests, data use and the existing privacy-policy link unchanged.
• AccuracyVerify the promise against actual data practices before launch.
• AudienceReview predefined form types that request email or phone separately.
• Separate testsTest placement, icon or alternative wording separately.

1. 1Do not promise privacy protections the business does not provide, such as saying data is never shared when it is.
2. 2Do not change the assurance and form field count together.
3. 3Do not use the message as a replacement for the full privacy policy; keep the policy accessible.
4. 4Do not make the assurance so prominent that it overshadows the form.
5. 5Do not use an assurance in place of legally required consent or privacy information.