Connect Kit

Connecting Kit lets you save website answers to subscriber records, so your emails can reflect what people tell you. You can also use their existing tags and fields to personalize your website, and send new signups to a Kit form or tag.

Connect Kit

You'll need permission to manage your RightMessage project's integration and access to Kit's API credentials. Each project connects to one email platform or CRM, so check what uses an existing connection before replacing it.

1. Open Kit's Developer settings (opens in a new tab).
2. Under V3 API Key, copy the API Key and API Secret. This connection uses those two credentials, not a v4 key or OAuth approval.
3. In RightMessage, open your project settings and choose Integration.
4. Under Email platforms & CRMs, select Kit.
5. In Overview, paste the credentials into API Key and API Secret.
6. Click Connect and check the connection health.

Enlarge

Kit connection form in RightMessage with the API Key and API Secret fields and Connect button highlightedOriginalOriginal

Keep both values private. Don't put them in email links, website code, or screenshots. To update them later, change the fields and click Save Changes.

The health check uses the API secret. Form and field-list reads also need the correct API key, so test those too.

Choose what to sync

You can save choice answers and segment groups to custom fields or a tag for each answer. Typed answers can go to custom fields or Kit's native First name field.

1. Open Questions, choose your question, and open Sync with Kit.
2. For a choice question, choose custom fields or tags under Sync mode.
3. For a field, choose Destination and fill in Answer → value. For tags, select the existing Kit tag for each answer. Typed questions map directly to a field.
4. To create subscribers, open your flow's Email question in Setup and keep Identify the visitor enabled.
5. Under Contact action, choose Submit form and select a Kit form, or choose Add to tag and select a tag.
6. Review the flow and consent controls, then click Publish.

Kit requires a form or tag subscription to create a new subscriber. Don't leave the destination empty. A field mapping, email lookup, or standalone contact update can't create a subscriber. Kit forms are signup destinations, not a separate choice-answer sync mode.

Use a Kit form when you want its incentive or confirmation settings and form-based automations to apply. You don't need to display the Kit form on your website. A subscription can send the form's confirmation or incentive email, so test with an address you control.

If a displayed Email question consent checkbox is left unchecked, RightMessage keeps the response without identifying the visitor or sending their data to Kit.

Pick fields and tags

Choose the intended field or tag from Kit's list rather than relying on its label alone. First name is the only native answer destination. Use custom fields for last name, phone, address, or other details. Name and Address questions can use One field per part to save each part separately.

To create a text field from the picker, choose New Kit custom fields, enter Field Name using letters, numbers, and underscores, then click Create. Kit custom fields appear as text destinations, not typed number or date fields.

Single-answer questions default to field sync. Multiple-answer questions prefer tags when available. Keep answer tags separate from unrelated workflow tags. Save an Other write-in to a separate field under Save write-ins to Kit. See the shared answer-mapping guide for multiple-answer values, tag removal, and switching modes.

This connection doesn't offer list sync, outgoing event actions, direct automation enrollment, incoming event history, or purchase history. A Kit automation triggered by a form subscription or tag is separate from a direct RightMessage automation action.

Recognize subscribers from email links

Choose an existing subscriber you control and install the RightMessage snippet on the page you'll test.

RightMessage reads the ck_subscriber_id URL parameter and a cookie with the same name. Its value is Kit's subscriber ID, not an email or tag ID. Kit can add it to Broadcast and Sequence links for you:

1. In Kit, open your account's Settings, then Advanced.
2. Enable Add subscriber_id parameter in email links and click Save changes.
3. Send your test subscriber an email with a link to one of your pages where RightMessage is installed.

Here's what a delivered link to WorkForge (opens in a new tab) could look like:

https://workforge.rightmessage.com/pricing.html?ck_subscriber_id=123456

The number is an example. Use the ID Kit supplies for your subscriber. Kit's global advanced tracking guide (opens in a new tab) explains the setting. Its separate hashed-email tracking parameter doesn't replace ck_subscriber_id for this integration.

If you use Kit forms or landing pages

Configure the form's redirect or subscriber-data setting so the final URL on your website contains ck_subscriber_id. Install RightMessage on that destination page and check the actual redirect. A form's confirmation settings don't necessarily pass identity automatically.

A RightMessage form or identifying Email question with a valid Kit action doesn't need a separate redirect parameter to identify the submission.

You can also look up an existing subscriber with the generic ?email= parameter and a URL-encoded email address. That lookup doesn't create a subscriber or confirm their subscription.

Check the connection

Start with an existing subscriber:

1. Give your test subscriber a distinctive Kit tag or custom-field value.
2. Open their delivered Kit email link in a fresh browser session.
3. Use the on-site debugger to check the subscriber and expected Kit data, including tags, custom fields, email, and first name.
4. Exit the debugger and submit a mapped answer on the live website.
5. Open the subscriber in Kit and check the exact field value or tag.

Then test a signup:

1. Choose another email address you control that isn't already in Kit.
2. Submit the published flow or form with its selected Kit form or tag destination.
3. In Kit, check that the subscriber exists and belongs to that destination.
4. If the form uses double opt-in, complete confirmation and check the subscriber's status before testing later identification and answer updates.
5. As that identified subscriber, submit a mapped answer and check the accepted value in Kit.

An unconfirmed signup may not behave like an active subscriber. Don't assume an answer will be replayed after confirmation. Check the new record, confirmation, and later update separately. If segmentation depends on confirmation, ask those questions through the confirmed subscriber's welcome email or return visit.

After identification, RightMessage remembers the browser on later pages until its saved identity is cleared. Another browser or device needs to identify the subscriber again. Matching mapped Kit values can also place an identified visitor in RightMessage segments. This isn't a bulk import or historical-answer backfill.

If something doesn't arrive

If the visitor stays anonymous, check the delivered ck_subscriber_id, the subscriber's availability in Kit, and that RightMessage loads on the destination. If existing subscribers work but new signups don't, check the form or tag destination.

For a missing field or tag, click Clear Cache in the Kit connection's Overview and reopen the picker. For partial updates, check the subscriber's status, destination mapping, and integration history. Avoid repeated form submissions that might send another email.

Kit API throttling can delay or reject reads and writes. RightMessage uses separate request budgets for the API key and secret and honors Kit's rate-limit responses. That doesn't increase your Kit account's quota.

Kit's internal provider name remains convertkit. Keep that identifier in existing configuration and provider-specific templates.

When your existing subscriber receives their answer and your new signup reaches the intended form or tag, the setup is working. Follow Verify an integration change when you replace credentials or change destinations.