How integrations and answer sync work
You'll see how your website can use what you already know about a contact and save new answers back to your email platform.
Updated
View as MarkdownConnecting your email platform lets you tailor your website to known contacts and use their new answers in your follow-up. RightMessage can read what you already know about someone, then save what they tell you back to their contact record.
First, recognize the person visiting
Each project connects to one email platform or CRM at a time. The connection gives RightMessage permission to look up contacts and make supported updates. It still needs to know which contact is visiting.
A browser becomes identified through a supported email link, an identifying question or form, or another identification method. Someone visiting on another device needs to identify themselves there too. Connecting your account doesn't load your whole email list into every browser.
Anonymous visitors can still answer questions and see personalized content. Their answers stay separate from a contact record until RightMessage can identify them.
Read contact data and save new answers
RightMessage reads an identified contact's supported fields, tags, and lists. You can use those details in conditions to decide what they see. The available data depends on your platform.
Mappings tell RightMessage where to save new answers. A typed answer can go into a contact field. A choice answer can save a field value or apply a supported tag. A signup action creates a contact, while a mapping chooses where the answer goes.
Choice mappings also work in reverse. If a known contact already has a mapped value, RightMessage can match them to that segment without asking again. Your widget's Question handling setting decides whether they'll still see the question.
Follow one answer from website to email
WorkForge (opens in a new tab) asks, "How does your team work?" It saves "Remote" as work_style=remote in its email platform.
A visitor answers before giving an email address. RightMessage knows their answer in that browser, but doesn't yet know which contact to update. When they identify themselves through the configured signup, RightMessage can send their eligible mapped data to the contact record.
Later, they open an identifying email link on another device. RightMessage reads work_style=remote and matches them to the Remote segment. WorkForge can show them a relevant offer without relying on that device's previous visits.
You'll see three different records of what happened:
| If you want to know… | Look at |
|---|---|
| What someone answered in RightMessage | Their response |
| Which audience category they match, through an answer or a condition | Their segment |
| What your email platform accepted for the identified contact | Their synced field |
Check the contact record after you publish
Saving credentials connects the account. Publishing makes your mappings available to website visitors. Check the contact record in your email platform to confirm it accepted the update or subscription.
Your platform's permissions, required fields, and signup requirements still apply. For example, Kit needs a form or tag destination to create a new contact, and Mailchimp needs an audience. Looking up a contact doesn't create one.
Update timing varies by platform and action. When RightMessage sends a stored input answer without a new submission, it preserves a value already in the provider's field. A newly submitted answer can change that value. Integration sync questions explains permissions, compatible fields, and timing.
Ready to connect yours? Choose your platform in Email platforms and CRMs, then map an answer and check a new and existing contact.