Integration permissions and sync questions

These answers help you get website answers into the right contact record. RightMessage needs to recognize the visitor, have a published mapping or contact action, and have permission to make that update in your email platform.

Is saving the connection enough?

No. Saved credentials can work for one action while another fails. A connection check may read data without testing subscriptions, form submissions, or every field update.

Test the action you plan to use. After replacing a key, try a new signup and an existing contact, then check both records in your platform. Verify a new connection or replacement API key walks you through it.

Which permissions does my provider need?

Your provider needs to allow each action you've set up in RightMessage. Looking up contacts, updating them, changing list membership, subscribing people, and creating fields can require different permissions. Check the guide for your provider and its current authorization settings.

For example, subscribing someone to a Klaviyo list requires subscriptions:write. A key that can read lists can pass a connection check but fail to subscribe someone. Replace the key with one that has the required scope, then test the signup again.

Can a field stop a form from submitting?

Yes. Your platform can reject a value that doesn't match the field's type, allowed choices, or requirements. A HubSpot form may also require properties you haven't included. Choosing a field in RightMessage doesn't change those rules.

Compare what you're sending with what the field or form accepts. Use text fields for free text, allowed choices for fields with fixed options, and compatible values for numbers and dates. Read the provider's error before changing unrelated question settings.

Does a contact have to exist first?

A contact must exist for a lookup to find it. A signup action can create or update a contact when your provider supports the destination you've chosen.

Kit needs a form or tag action for new contacts. Mailchimp needs an audience. An identifying link, an email lookup, or an answer mapping doesn't replace that signup action. An Email question's consent settings can also stop identification and provider updates, even when the answer appears in Responses.

Do I need to create custom fields in my email platform first?

Not always. If your provider supports field creation, you'll see a New field action in the picker. Other providers let you type a field name directly. If neither option is available, create a compatible field in your provider, then use Clear Cache to refresh the list.

Map answers to contact fields and tags explains the picker. You can also map several questions together.

Should I use a custom field or a tag?

Use a field when one stable value describes the answer, such as work_style=remote. Use supported tag mapping when your email workflow needs separate labels for the selected answers.

The available choices depend on your provider. Bento and Klaviyo don't offer writable tag mapping for choice answers. MailerLite groups appear as list resources, but aren't a choice-question sync mode. A tag or group in your email platform isn't always available for answer mapping in RightMessage.

How long should an update take?

There's no single wait time or retry schedule for every provider and action. Your platform may need time to process updates, and contact updates and subscriptions can use separate requests.

Open Integrations, choose your provider, then open History. Find the matching request and check the contact record in your platform. If the request failed, use its error to decide what to fix. Submitting repeatedly can repeat automation actions. Contact-sync troubleshooting helps you narrow down the cause.

Why does one form identify visitors but another doesn't?

The working form may pass the visitor's identity to RightMessage in a way the other form doesn't. Creating a subscriber on the server doesn't identify the browser that opens a thank-you page.

The snippet doesn't watch every form by default. Use the optional Email Watcher, a supported provider callback, or the form-submission trigger in Identify visitors automatically. Then check that RightMessage recognizes the browser.

Will old browser answers overwrite newer contact data?

No, not when RightMessage syncs a stored input answer without a new submission. This passive sync keeps an existing value in your provider. If the visitor submits a new answer, that active update can change the field.

Attribution works separately. Each destination has its own Overwrite? setting, covered in Map lead attribution to contact fields.