Why Collect Text Marketing Opt-In on Your Landing Page
When a potential customer fills out your landing page and shares their phone number, that moment of interest is your best opportunity to open a direct line of communication. Adding a text message marketing opt-in checkbox to your landing page phone field lets you capture that permission right when engagement is highest, so you can follow up with promotions, updates, and offers the customer has explicitly agreed to receive.
Beyond the business opportunity, collecting opt-in is required. Mobile carriers and federal regulations set by the FCC and CTIA mandate that businesses obtain explicit written consent before sending marketing text messages. Collecting opt-in directly on your landing page satisfies that requirement at the point of contact, protects your business from compliance risk, and builds trust with your customers by making consent transparent and optional.
For a full overview of text messaging compliance requirements, including opt-in language, privacy policy requirements, and carrier verification, see Thryv Text and Voice Registration and Verification Requirements.
How to Add Text Message Marketing Opt-In to a Landing Page Phone Field
To edit your landing pages, click on Marketing in the left-hand navigation, and select Landing Pages from the menu. Click on the tri-dots and then edit for the landing page you wish to change.
- Click the edit icon on the phone number field
- Check the box to ask permission to send text message marketing messages
Once enabled, visitors who enter their phone number on your landing page will see a checkbox asking for their consent to receive text message marketing. The checkbox is unchecked by default, meaning consent is always the visitor's active choice.
FAQ
Can I make the marketing opt-in checkbox a requirement?
No. Cell phone carriers explicitly prohibit marking opt-in as required. It has to be an optional field.
Does enabling this opt-in satisfy all carrier compliance requirements?
No, for a full list of requirements see Thryv Text and Voice Registration and Verification Requirements.
Comments
0 comments