# Connect Userlist

You'll save visitors' answers to Userlist properties and use what you know about each user to choose their next question or offer.

Available on the Scale and Pro plans.

Connecting Userlist lets you save website answers as user properties, ready for your follow-up. You can also use those properties to choose the next question or offer someone sees on your website.

## Connect Userlist

You'll need permission to manage your RightMessage project's integration and access to the intended Userlist account's Push API settings. Get its **Push Key** and **Push ID** there. Each RightMessage project connects to one email platform or CRM at a time, so check what uses an existing connection before replacing it.

1. Open your RightMessage project settings and select **Integration**.
2. Under **Email platforms & CRMs**, choose **Userlist**.
3. Enter the credentials in **Push Key** and **Push ID**.
4. Click **Connect** and open **Overview**.

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

Keep both values private. To replace them later, update the fields and click **Save Changes**.

> **Why you see a write-canary message**
>
> When both credentials are present, the connection check reports **Userlist requires an authorized write canary**. A write canary is a small test write you've deliberately approved. This check doesn't perform one or validate your credentials with Userlist. Test a property update on a user you control instead. The message can remain after a successful update, and repeatedly saving the credentials won't turn it green.

If you see **Userlist credentials are incomplete**, check that you've entered both values.

## Choose what to sync

Save answers to the user property your Userlist follow-up reads. Prepare a harmless test property, such as `content_interest`, and check any workflows that creating or updating your test user could trigger.

1. Open **Questions** and choose a multiple-choice question.
2. Open **Sync with Userlist**.
3. Under **Destination**, enter the exact property name in **Save answers to Userlist**, such as `content_interest`.
4. Under **Answer → value**, enter the value for each answer, such as `workshops` or `templates`.
5. Review your changes and click **Publish** before testing the live question.

Userlist's **User Properties** let you enter a property name rather than choose from a list. Keep the name consistent with your Userlist workflow. Multiple-selection questions save comma-separated strings, not arrays. Choice questions don't sync to tags or lists.

There isn't a separate native-field list for names, phone numbers, or addresses. Save those answers to the properties your Userlist setup uses. The identifying email is handled separately.

After identification, matching property values can place someone in the corresponding RightMessage segment without asking again. RightMessage reads user properties, not company records, relationships, segment membership, purchase history, or event history.

To create users, open an Email question's **Setup**, keep **Identify the visitor** enabled, and choose **Create/Update contact** under **Contact action**. You don't need a list, tag, or form destination. Review consent before publishing. An anonymous answer doesn't sign someone up, and mapping a property doesn't set up a Userlist email workflow for you.

For other question types, see [Map answers to contact fields and tags](https://rightmessage.com/help/synchronizing-contact-data-with-your-email-platform-or-crm).

### Send an event from a form

You can also send configured Userlist events and their properties. This is a form action, separate from answer mapping and an Email question's **Contact action**. It doesn't import event history.

1. Open the form's action settings and choose **Trigger an event** under **Action**.
2. Under **Events**, enter the exact event name your Userlist workflow expects. Use commas only if you intend to send multiple events.
3. To send extra data, choose **Add metadata** under **Event metadata** and enter each **Key** and **Value**. Values support Liquid template variables.
4. Review and publish the form and flow changes, then submit once with a test address you control.
5. Check the event name and properties on the intended user in Userlist.

Each accepted submission event is a separate occurrence. Don't repeatedly submit a live form to try to change the health indicator. That indicator doesn't check event delivery.

## Recognize subscribers from email links

Install the [RightMessage snippet](https://rightmessage.com/help/everything-you-need-to-know-about-your-rightmessage-tracking-script) on the page you'll link to. In your Userlist message, add `u_id` with the recipient's email to a link to one of your own pages.

Here's an example for [WorkForge](https://workforge.rightmessage.com):

```text
https://workforge.rightmessage.com/pricing.html?u_id={{ user.email }}
```

Userlist replaces `{{ user.email }}` with the recipient's email. Its [Liquid personalization reference](https://userlist.com/docs/messages/liquid/) explains using these tags in links. If the URL already has a query string, append `&u_id={{ user.email }}` instead.

Use the email for `u_id`, not Userlist's internal numeric user ID or an ID from your application's database. RightMessage uses its own scoped identity to resolve Userlist records. If your app also supplies Userlist users, check that this method reaches the record you expect.

> **Identification can change a Userlist record**
>
> The connector looks up users with Userlist's `PUT /users` operation, not a read-only `GET`. Even opening an identifying link can change a record. Use a test user you control, and check which record receives the update.

RightMessage also reads a `userlist_id` cookie when it's present and accessible on the site. You don't need to create that cookie for the email-link method.

## Check the connection

1. Send a Userlist message to your test user. Check that the delivered link contains their email, not an unresolved Liquid expression.
2. Open it in a fresh browser session on a page with RightMessage installed.
3. Follow [Verify an integration change](https://rightmessage.com/help/verify-an-integration-change) to check that RightMessage identifies the intended user.
4. Revisit without the parameter to check that the browser remembers them.
5. Answer your mapped question, then open the user in Userlist. Check that your property contains the exact answer value on the record you expected.
6. If you plan to create users, test a signup separately with a fresh address you control and check the new user in Userlist.

RightMessage removes `u_id` from the displayed URL after reading it. The original link still contains an email address, so don't share it publicly. A new browser or device needs to identify the user again. Connecting Userlist doesn't identify every visitor.

If an update fails, check the Push Key and Push ID pair, connected account, delivered email-link value, and exact property name. Use **History** to inspect failed requests. For an identity mismatch you can't resolve, contact RightMessage support with the failure time and a redacted description of the expected and actual records. Don't send credentials or links containing someone else's email.

When the intended user's property contains the answer you submitted, the update is working, even if health doesn't say **OK**. Next, use that property in your Userlist follow-up.