Skip to main content
Build, Publish & Automate

Control integration syncing with email and SMS consent

Use consent fields to control when Revup sends mapped email and phone data to connected integrations.

Revup checks for an Email Consent or SMS Consent field before sending a participant's mapped contact data to connected integrations.

  • If Email Consent is on the form, Revup sends mapped email data only when the participant checks it.
  • If SMS Consent is on the form, Revup sends mapped phone data only when the participant checks it.
  • If Email Consent is not on the form, Revup treats email as allowed and sends mapped email data according to the connected integration's configuration.
  • If SMS Consent is not on the form, Revup may still send a mapped phone number as contact data, but it does not subscribe that number to SMS marketing. Add SMS Consent to collect SMS subscribers.

When an unchecked consent field removes a contact method required by the integration, Revup skips that integration sync for the participant. If another permitted identifier is available, the integration may still receive other mapped data.

  1. Open the promotion builder and select Form.
  2. In Form Fields, select Search for a field type.
  3. Add Email Consent, SMS Consent, or both.
  4. Write clear consent language that explains what the participant agrees to receive.
  5. Add the appropriate Terms URL and Privacy URL.
  1. Keep the consent checkbox unchecked by default so the participant makes an affirmative choice.
  2. Submit one test with consent checked and another with it unchecked, then review the connected integration.

Email and SMS are separate

Email consent does not grant SMS consent, and SMS consent does not grant email consent. Add both fields when a promotion may send both email and phone data to integrations, and respect each response independently.

Submitting a form, accepting Official Rules, or providing an email address or phone number is not the same as granting marketing consent.

Provider requirements still apply

Consent fields control Revup's integration syncing, but they do not replace your legal obligations or a provider's subscription and double-opt-in requirements. Use consent language appropriate for your promotion and confirm the resulting subscription state in the destination provider before launch.

Was this helpful?

Still need help? Ask the team