Connect Kit once and Mida can show an A/B test or a personalization only to the subscribers you choose, by tag or custom field. You paste one API key and turn on one setting in Kit. There is no code to add to your site or your emails.
It also works the other way: Mida can save a survey answer, or any other attribute you choose, onto the subscriber in Kit.
Plan: targeting by Kit audience needs a paid Mida plan.
How it works
The short version: a subscriber clicks a link in one of your Kit emails. Kit adds their subscriber ID to that link. Mida reads the ID, looks the subscriber up in your Kit account, and saves their tags and the custom fields you picked on their Mida visitor. Your targeting rules then read those values.
Kit adds a parameter called ck_subscriber_id to the links in your Broadcast and Sequence emails. It looks like this:
https://yoursite.com/pricing?ck_subscriber_id=123456
Mida leaves that parameter in the address bar, because Kit's own script reads it too.
What Mida copies
Data | What is copied | Name in Mida |
Tags | Every tag in your account, saved as true when the subscriber has it and false when they do not. Always on. |
|
Custom fields | Only the fields you tick. |
|
First name and status | Only if you tick them. Status is active, cancelled, bounced, complained or inactive. |
|
Tag names are turned into lower case with underscores, so "Lead Magnet: SEO" becomes kit_tag_lead_magnet_seo. You do not have to work these out. Mida lists the exact name next to each tag, and you can click it to copy.
Kit segments are not available. Kit does not let other tools read which segments a subscriber is in, only their tags and custom fields. If you need a segment, add a tag to its subscribers in Kit and target the tag.
When targeting applies
Targeting applies from the visitor's next page view, not the page they land on from the email. The lookup runs in the background so it never slows your page or delays a test.
Mida keeps a person's data for up to 6 hours before asking Kit again. A change you make in Kit can take that long to show up in Mida.
Mida remembers the person in that browser, so they stay recognized on later visits. Another browser or device needs its own click from an email.
Visitors who never clicked one of your Kit emails, and whom Kit's own script has not identified on your site, stay anonymous and do not match any Kit rule.
Visitors recognized without an email click
Kit can also save the subscriber's ID in the visitor's browser, in a cookie named ck_subscriber_id, for example after they subscribe through a Kit form on your site. Mida reads that ID too, so the subscriber is recognized from their next page view without clicking an email.
This needs Kit's forms or script on your site, and the Kit integration turned on in Mida.
Mida checks once per browser session. An ID Kit does not know is not asked about again for a day.
Mida keeps only Kit's contact ID in the browser, never an email address.
An ID from an email link always comes first. With Strict Consent Mode, Mida waits for consent before reading anything.
Before you start
In Kit, open Settings, then Advanced, and turn on Add subscriber_id parameter in email links. Save your changes. It only affects emails you send afterwards.
Create a V4 API key. In Kit, go to Settings, then Developer, and create a V4 API Key. Copy it. A V3 API key or API secret will not work.
Make sure the Mida tag is installed on the pages your emails link to.
Connect Kit
In Mida, open Integrations and choose Kit under Marketing & Email.
Click Enable Kit Integration.
Open the Config tab.
Paste your key into V4 API key and click Connect.
When it says Connected, tick the fields you want to use under Attributes to bring in, then click Save attributes. You can pick up to 40.
Only an Owner or Admin can connect, replace the key, or disconnect. Tags need no setup: every tag is brought in.
Target a test or a personalization
Open your test and go to Targeting.
Add a Segment rule.
In the attribute field, type the name from the Kit Config tab.
Choose a condition and a value, then save.
You want to reach | Attribute | Condition | Value |
Subscribers tagged "Customer" |
| Is true | |
Known subscribers who are not tagged "Customer" |
| Is false | |
Subscribers whose "plan" field is pro |
| Is equal to | pro |
Active subscribers only |
| Is equal to | active |
Everyone Mida has recognized from Kit |
| Exists |
A few things to know about conditions:
To target people who have something use Is true. To target known contacts who do not have it use Is false.
Anonymous visitors never match one of these rules, including "Is false" and "Does not exist". Mida knows nothing about them, so it leaves them out.
Text conditions are case sensitive. "Pro" and "pro" are different values.
All values arrive as text. Number and date conditions still work as long as the value looks like a number or a date.
For the full list of conditions, see How to use Segment & Event Filtering.
Send Mida attributes to Kit
Mida can also save attributes onto the matching subscriber in Kit. The usual case is a survey: a visitor answers "What is your team size?" on your site, and the answer is saved on their Kit subscriber, where your emails and automations can use it.
There is nothing extra to connect. Kit is written with the key you already pasted.
In Kit, create a custom field for each attribute you want to receive, if it does not exist yet. Note its key, which is lower case with underscores, for example
team_size.In Mida, open the Kit Config tab. Under Send Mida attributes to Kit, tick the attributes you want to send, then click Save. You can pick up to 20.
What you can pick from
Survey answers: every question with Save the answer to the visitor turned on, shown with the question and its survey.
Attributes on your visitors: names Mida has seen on your recent visitors, for example ones you set with
mida.identify(), with how many visitors carry each.If an attribute has not reached a visitor yet, type its name in Not listed? and click Add.
The name must be the key of a custom field that already exists in Kit. Mida does not create fields in Kit.
How it behaves
It is only sent for visitors Mida has recognized from one of your Kit emails. Anonymous visitors are never sent.
If a visitor answers first and is recognized later, the answer is sent as soon as they are recognized.
Nothing is sent until a name is on the list. Mida never sends an attribute you did not list.
Mida never creates a new subscriber in Kit. It only updates ones that already exist.
The same value for the same subscriber is sent once an hour at most.
A value overwrites whatever was there before.
To stop, untick everything and click Save.
Test that it works
Pick a tag that you have yourself as a subscriber, and create a test that targets it.
Send yourself a Kit broadcast with a link to your site.
Click the link in a normal browser window. Check that the address contains
ck_subscriber_id.Go to another page on your site, or reload. You should now be in the test.
Privacy and consent
Mida copies only what is listed above and the fields you tick. Nothing else is read into Mida.
In the other direction, Mida sends Kit only the attributes you list under Send Mida attributes, and only for recognized visitors.
The values are saved on the visitor in Mida and used for targeting only. They are not sent back to the visitor's browser.
If you use Strict Consent Mode, Mida does not read or store the contact ID until the visitor gives consent. If consent is withdrawn, the stored ID is removed from the browser.
Mida never creates a visitor from a Kit lookup, so this does not add to your monthly tracked users.
Your API key is encrypted at rest and never shown again after you paste it. Mida reads from Kit with it, and writes only if you list attributes to send.
When you disconnect, Mida deletes the stored key and stops looking people up. Values already saved on visitors stay there, but they are no longer refreshed.
One more thing to know: Kit subscriber IDs are plain numbers. Nobody can read a subscriber's data through Mida, but a person who edits the number in a link could be treated as a different subscriber for targeting. Use this to tailor what people see, not to protect content that must stay private.
Limits
Limit | Value |
Fields you can bring in | 40 per project |
Length of a field value | 200 characters. Longer values are cut. |
Tags in your account that Mida tracks | 200 |
How long a subscriber's data is reused before Mida asks Kit again | Up to 6 hours |
New subscribers Mida looks up | About 50 a minute |
Kit limits how many requests an API key can make each minute, and Mida stays under that. Right after a large broadcast, some visitors may be recognized a page view or two later than usual.
Troubleshooting
What you see | What to check |
"Kit rejected this key" | You need a V4 API key from Settings, Developer. A V3 API key or API secret will not work. |
My links have no | Turn on Add subscriber_id parameter in email links in Kit under Settings, Advanced. Emails sent before you turned it on do not have the ID. |
I clicked the email but I am not in the test | Targeting starts on the next page view. Load a second page. Also check the test's other targeting rules. |
A custom field I ticked is not being matched | Check the value in Kit for that subscriber. Empty fields are not copied. If it still does not match, contact us in the chat. |
I changed a subscriber in Kit and Mida has not noticed | Mida reuses a subscriber's data for up to 6 hours. |
The card says "Needs attention" | Kit stopped accepting the key, usually because it was deleted. Click Replace key and paste a new one. |
A survey answer is not showing up in Kit | Check that a custom field with that exact key exists in Kit, that it is ticked under Send Mida attributes, and that the visitor clicked one of your Kit emails in that browser. |
FAQ
Does this work for visitors who never opened my emails?
Only if Kit's own script identified them on your site, as described in "Visitors recognized without an email click". Everyone else is anonymous until they click a link from one of your Kit emails.
Do I need to change my emails?
No. Once the setting is on, Kit adds the ID to your links by itself.
Will it slow down my site?
No. The lookup happens in the background after your page and your tests have loaded.
Can I connect more than one email platform?
Yes. A project can connect several, for example HubSpot as your CRM and another tool for email. Each is connected and set up on its own card. A visitor recognized by more than one gets each platform's data side by side, and an attribute you send goes to every platform that lists it.
