Connect Drip

Connect Drip to save visitors' answers to their subscriber records, ready for your follow-up. You can also use an identified subscriber's existing tags and custom fields to show them relevant content on your website.

Connect Drip

You'll need permission to edit your RightMessage project and authorize access to your Drip account. Keep the Account ID handy. It's the number in your Drip account URL.

Each RightMessage project connects to one email platform or CRM. Review where you use an existing connection before replacing it.

1. In RightMessage, open your project's settings and select Integration.
2. Under Email platforms & CRMs, select Drip.
3. Click Connect to Drip.
4. Sign in to Drip if prompted and authorize RightMessage for the account you want to use.
5. Back in RightMessage's Drip Overview, enter the account's number in Account ID.
6. Click Save Configuration.

Enlarge

Drip connection controls in RightMessage, with no credentials enteredOriginalOriginal

Check connection health after saving the account. This reads the account's tag catalog. You'll test subscriber lookup and saved answers below. Authorization and account selection are separate, so check the Account ID even if authorization succeeded.

You don't paste access or refresh tokens into this form. Use Reconnect to Drip if authorization needs renewing. Save Configuration saves the Account ID, not your question mappings.

Install the RightMessage snippet on your website and any thank-you pages you'll test.

Recognize subscribers from email links

Drip adds __s to tracked email links. RightMessage reads it as the subscriber's identifier, so you don't need another merge tag on a normally tracked link.

For example, a delivered link to WorkForge (opens in a new tab) would have this shape:

https://workforge.rightmessage.com/solutions.html?__s=DRIP_SUBSCRIBER_IDENTIFIER

Don't paste that placeholder into your email. Link to your own page and let Drip supply the identifier.

1. Send a Drip message to an existing test subscriber with a tracked link to a page containing RightMessage.
2. Inspect the delivered link and check that __s is still present after tracking redirects.
3. Open the link in a fresh browser session and check the subscriber in RightMessage's on-site debugger.

Drip lets you suppress __s and tracking (opens in a new tab). Redirects and privacy tools can also remove parameters. If the identifier doesn't reach your page, this link can't identify the subscriber.

If you also use Drip's JavaScript snippet

RightMessage can ask Drip's initialized JavaScript client for its visitor_uuid. This works when Drip knows the visitor, not when it reports an anonymous browser. RightMessage checks an explicit __s link value before asking Drip's client.

When RightMessage learns an email, it also queues an identify call with that email for Drip's client. Installing both scripts doesn't identify every visitor, and another device needs its own identification.

Recognize people after a form

A configured RightMessage Email question or form can identify and create or update a Drip subscriber. You don't need a redirect parameter for an email RightMessage just collected.

For a Drip-hosted or embedded form, configure its thank-you behavior to pass the person's data to your destination page, if your Drip form editor offers that option. Submit the form and inspect its redirect. A static thank-you URL might not include identity.

For another form tool, check both parts:

• The form creates or updates the intended Drip subscriber.
• RightMessage detects the submitted email or receives a valid identifier on a page with its snippet.

External forms need an enabled capture path, such as Email Watcher or a Popup widget's After a form is submitted trigger. Installing the snippet alone doesn't watch every form. See Identify visitors automatically.

The subscriber needs to exist in Drip before lookup can find them. If you build a redirect yourself, put Drip's subscriber identifier in __s, not an email address.

Choose what to sync

RightMessage reads an identified subscriber's custom fields and tags. You can map choice answers and segment groups to either one, and save typed answers to named custom fields.

Enter the exact custom-field name you want to use. Drip fields aren't a fixed catalog of native fields such as first name or phone. RightMessage can read existing field identifiers, but you still map answers by field name.

The connection supports adding and removing Drip tags. It doesn't provide list membership, automation enrollment, outgoing event actions, event history, or purchase history. Your Drip automations can still react to a tag or form submission you configure there.

Choose what a signup should do

For an Email question, Contact action offers Create/Update contact, Submit form, and Add to tag. You don't need a list or hosted form for direct contact creation.

If your automation starts with a form submission, choose Submit form and select that form. Creating a contact alone won't submit it. The form action sends the email and mapped custom fields to Drip's hosted submission endpoint. It doesn't necessarily run the browser behavior of an embedded form.

For a tag action, select a destination tag. Configure email identification and consent too. Connecting Drip doesn't configure these for you.

Follow Map answers to contact fields and tags, then publish your question, form, flow, or targeting changes. Connecting Drip doesn't import every subscriber or apply historical answers.

Check the connection

1. Give an existing test subscriber a distinctive tag or custom-field value in the selected Drip account.
2. Open their delivered email link in a fresh browser session. Check their identity and incoming data in RightMessage's on-site debugger.
3. Outside debugger mode, submit a mapped answer on the live site. Check that the same Drip subscriber received the new value or tag.
4. In a separate fresh session, submit a new test signup. Check the account, subscriber, and any form or tag destination you chose.

Debugger mode blocks external writes, so use a live submission to test saved answers. When Drip's data reaches your website and the submitted answer reaches the same subscriber, the connection is working. If either part fails, follow Verify an integration change.