# Connect Ontraport

You'll save visitors' answers to Ontraport fields or tags and use their contact data to choose what they see on your website.

Available on the Scale and Pro plans.

Connecting Ontraport lets you save website answers to contact records for your follow-up. You can also use the fields and tags you already have to choose the next message a contact sees on your website.

## Connect Ontraport

You'll need permission to manage your RightMessage project's integration and access to Ontraport's API key administration. Get the **App ID** and **API Key** for the same connection. You don't need an API URL.

Each RightMessage project connects to one email platform or CRM. Check what uses an existing connection before replacing it.

1. Open your RightMessage project settings and select **Integration**.
2. Under **Email platforms & CRMs**, choose **Ontraport**.
3. Enter the credentials in **App ID** and **API Key**.
4. Click **Connect** and check the connection status in **Overview**.

![Ontraport connection form in RightMessage with the App ID and API Key fields and Connect button highlighted](https://rightmessage.com/help/screens/integrations-ontraport-connect.light.webp)

The health check reads Ontraport's contact-field definitions. You'll check contact creation and field or tag updates below. If your credentials change, update the fields and click **Save Changes**. Keep the API key out of website code, screenshots, and email links.

## Choose what to sync

Create the fields or tags you want to use in Ontraport first. You can't create those definitions from RightMessage.

1. Open **Questions** and choose a multiple-choice question.
2. Open **Sync with Ontraport**.
3. Under **Sync mode**, choose **Custom Fields**.
4. Choose a destination in **Save answers to Ontraport**.
5. Set each **Answer → value** mapping. For an interest question, you might save `workshops` or `consulting`.
6. Review the changes and click **Publish**.

To save a tag for each answer instead, choose **Tags** and select an existing tag under **Answer → tags**. When an identified visitor changes their answers, RightMessage adds the newly selected mapped tags and removes mapped tags for answers that no longer apply. It leaves unrelated tags alone.

Multiple-selection questions default to tag mode when no mode has been saved. Check the mode before mapping. Switching modes clears the previous mappings after you confirm **Switch & Clear**.

Field sync saves multiple selections as comma-separated values. Use a text field that accepts that format, not an Ontraport multi-value field that needs its own encoded options. See [Map answers to contact fields and tags](https://rightmessage.com/help/synchronizing-contact-data-with-your-email-platform-or-crm) for other question types and mapping settings.

### Pick a writable field

Ontraport contact details appear under **Custom Fields**, without a separate native-field picker. The list includes text, email, phone, address, number, price, checkbox, date, dropdown, and multi-value fields.

Choose a writable field and use Ontraport's stored option value for choice fields. Timestamp, timezone, parent, subscription, and merge-field types are read-only. Don't choose them for answer updates even if they appear in the picker.

### Create contacts without an Ontraport form

For an Email question, open **Setup**, keep **Identify the visitor** enabled, and choose **Create/Update contact** under **Contact action**. To add a tag at signup, choose **Add to tag** and select its destination. Review consent before publishing.

An identifying submission creates or updates a contact by email. You don't need a list or a matching Ontraport hosted form for each RightMessage form. This connection doesn't offer hosted-form submission or list sync.

After identification, you can use a contact's fields and tags in conditions and segmentation. Matching mapped values can also place them in the corresponding RightMessage segment without asking again. The connection doesn't import purchase or event history or offer direct automation enrollment.

## Recognize subscribers from email links

Choose a test contact you control and [install the RightMessage snippet](https://rightmessage.com/help/everything-you-need-to-know-about-your-rightmessage-tracking-script) on the page you'll test.

RightMessage reads `rm_ontraport` as the recipient's Ontraport contact ID. It isn't your App ID, a tag ID, or the contact's email.

In an Ontraport email, append `?rm_ontraport=` to a link to one of your pages. Insert the recipient's contact-ID merge field through Ontraport's picker. If the URL already has a query string, use `&rm_ontraport=` instead.

Here's a link to [WorkForge](https://workforge.rightmessage.com) with a synthetic contact ID:

```text
https://workforge.rightmessage.com/pricing.html?rm_ontraport=12345
```

The merge field needs to supply each recipient's own ID. Don't hard-code `12345` or one person's contact ID into a campaign for everyone.

RightMessage also reads Ontraport's `contact_id` cookie when it's present and accessible on your website. Not every visitor has that cookie, so test the email-link method separately.

## Check the connection

1. Send an Ontraport email to your test contact.
2. Check that the delivered link contains their contact ID, not an unfilled merge field.
3. Open it in a fresh browser session on a page with RightMessage installed. Follow [Verify an integration change](https://rightmessage.com/help/verify-an-integration-change) to check the intended contact is identified.
4. Revisit without the parameter to check that the browser remembers them.
5. Answer your mapped question, then open the same contact in Ontraport and check the field value or tag.
6. If you'll create contacts, test a signup separately with a fresh email address you control. Check the new contact and any selected tag in Ontraport.

RightMessage removes `rm_ontraport` from the displayed URL after reading it. Keep the original personalized link private because it identifies a contact. Another device needs to identify them again.

If the answer doesn't arrive, check the browser's identity, selected destination, write permissions, and published mapping. Use **History** to investigate failed operations. If a new field or tag is missing, click **Clear Cache** in **Overview** and reopen the picker. This refreshes the available destinations. It doesn't create missing ones or replay previous answers.

When the intended contact has the field value or tag you submitted, the connection is working. Next, use that information in your Ontraport follow-up.