Map Revup fields to integration fields

In the provider setup, match the Revup email field to email and review each remaining field individually. Use compatible types: text to text, dates to dates, numbers to numbers, and known choices to allowed provider values.

Do not reuse a destination field with a different meaning merely because its type accepts the value. Use stable field names across promotions when the information is genuinely the same.

Consent mappings require special care. Rules acceptance, form submission, email consent, and SMS consent are separate facts. Send only the status the participant actually provided.

After any field change, submit a test and inspect the destination. Existing destination records may keep earlier values depending on provider behavior.