Connect Encharge

Connecting Encharge lets your emails reflect what people tell you on your website. You can save their answers to fields or tags, then use what you already know about a contact to choose what they see when they return.

Connect Encharge

You'll need permission to manage your RightMessage project's integration and access to your Encharge API key. Each project connects to one email platform or CRM at a time. If you're replacing a connection, check which questions, forms, or conditions use it first.

1. Open your Encharge account (opens in a new tab) and copy its API key.
2. In RightMessage, open your project settings and choose Integration.
3. Under Email platforms & CRMs, select Encharge.
4. In Overview, paste the key into API Key.
5. Click Connect and check the connection health.

Enlarge

Encharge connection controls in RightMessage, with no credentials enteredOriginalOriginal

Keep the API key private. It belongs in this connection form, not in a website URL or snippet. There's no OAuth approval step or second secret field. If authentication fails, replace the key and click Save Changes.

A healthy connection confirms account access. You'll test a contact update below. Connecting Encharge doesn't import your whole audience or identify everyone who visits.

Choose what to sync

You can save choice answers and segment groups to a custom field or a tag for each answer. Typed answers go to a writable field. RightMessage can also use an identified contact's existing fields and tags for segmentation.

1. Open Questions and choose the question you want to sync.
2. Open Sync with Encharge. For a choice question, choose a custom field or tags under Sync mode.
3. For a field, choose Destination and fill in Answer → value. For tags, select the existing tag for each answer. Typed questions map directly to a field.
4. If you need to create contacts, open your flow's Email question in Setup and keep Identify the visitor enabled.
5. Under Contact action, choose Create/Update contact, or choose Add to tag and select its tag.
6. Review the changes and click Publish before testing the live flow.

Single-answer questions default to field sync. Multiple-answer questions prefer tags when available. Keep answer tags separate from unrelated workflow tags. The shared answer-mapping guide covers multiple-answer values and tag changes.

For an Other write-in, choose a separate custom field under Save write-ins to Encharge. Don't send the choice answer and write-in text to the same field.

Pick a field that fits the answer

Choose from Encharge's field list rather than entering a free-form attribute name. Read-only system fields aren't offered as writable destinations. Writable built-in person fields appear in the same list as custom fields, without a separate Native Fields group.

To create a text field from the picker, choose New Encharge custom field, enter Field Name using letters, numbers, and underscores, then click Create. Create number, date, or boolean fields in Encharge first, then select them in RightMessage.

Incoming profiles exclude name, firstName, lastName, and userId. Don't use those fields to check that reading a profile works, or assume a name you save to Encharge will be available for website personalization. Email is used for identification.

Choose what happens at signup

Create/Update contact doesn't need a form or list destination. Add to tag needs a selected tag. Dynamic Encharge segments aren't lists you can add someone to through this connection, and there's no Encharge form-submission destination.

Email questions identify visitors by default, but their contact action and consent settings still control the submission. If a displayed consent checkbox is left unchecked, RightMessage keeps the response without identifying the visitor or sending their data to Encharge.

This connection doesn't offer outgoing event actions, direct automation enrollment, incoming event history, or purchase history. Use fields and tags for the information you want to use on your website.

Recognize subscribers from email links

Install the RightMessage snippet on the page you'll test, and choose a test contact you control.

RightMessage reads rm_en as Encharge's internal person ID, not a custom user ID or email address.

1. In your Encharge email editor, append ?rm_en= to a link to one of your pages. Use &rm_en= if the link already has a query string.
2. Insert the internal person-ID merge field from Encharge's merge-tag picker.
3. Send a test email and check that the delivered link contains the recipient's ID.

Here's a link to WorkForge (opens in a new tab) with a synthetic contact ID:

https://workforge.rightmessage.com/pricing.html?rm_en=12345

Don't hard-code one person's ID into every recipient's link. Encharge needs to replace the merge field when it sends the message. Its merge-tag guide (opens in a new tab) explains how to insert person fields.

To identify by email instead, use the generic email-lookup parameter:

https://workforge.rightmessage.com/pricing.html?email={{person.email}}

This looks up an existing Encharge contact. Check that the delivered URL encodes the email correctly, including %2B for a + in the address. Opening the link doesn't create a contact. Keep identifying links private rather than sharing one contact's link with everyone.

Check the connection

1. Give your test contact a distinctive tag or custom-field value in Encharge.
2. Send them an email with an identifying link, then open it in a fresh browser session on a page with RightMessage installed.
3. Use the on-site debugger to check that RightMessage identifies the contact and shows the expected Encharge data.
4. Visit another page without the identifying parameter to check that the same browser remembers the contact. Another browser or device needs to identify them again.
5. Submit a mapped answer on the live website as your test contact. Open that person in Encharge and check the exact field value or tag.
6. Test your contact-creation action with a new email address you control. Check that the new person appears in the intended Encharge account.

Matching Encharge values can place an identified visitor in the corresponding RightMessage segment. During passive sync, RightMessage keeps an existing nonempty Encharge field instead of replacing it with an old browser answer. Submitting a new answer can update it. This doesn't backfill every historical answer.

If identification fails, check the delivered parameter value and that the contact exists. If a field you've created is missing, open the Encharge connection's Overview, click Clear Cache, and reopen the picker.

When you can recognize the intended contact and see their submitted answer in Encharge, the connection is working. For a fuller check after changing credentials or mappings, follow Verify an integration change.