Kit
Subscribe people to a Kit form or tag when they submit your form, or when their lead reaches a stage.
The Kit destination adds the people who fill in your form to your Kit account (formerly ConvertKit), so your newsletter and email sequences start without any manual exporting.
Kit is a destination, which is part of the Pro plan. See Basic and Pro plans.
What you need from Kit
Two things: an API key, and the number of the form or tag people should be added to.
The API key
- In Kit, open Settings and go to Developer.
- Copy the API Key from the v3 section.
Use the API Key, not the API Secret. PageFork only adds subscribers, and the key is all Kit needs for that. PageFork never asks for your secret. Newer “v4” keys won’t work here.
A form id or a tag id
Kit puts subscribers on a form or gives them a tag. You choose which when you create the destination.
To find a form id: in Kit, go to Grow → Landing Pages &
Forms and open the form. The address bar shows something like
app.kit.com/forms/designers/1234567/edit. The number is the form id.
The form doesn’t need to be placed on any website, but do save and
publish it in Kit.
To find a tag id: in Kit, open Subscribers, click the tag in the side list, and read the number in the address bar.
Form or tag: which should I use?
| Form | Tag | |
|---|---|---|
| Meaning in Kit | ”This person signed up here" | "This person is one of these” |
| Best trigger | New submission | A stage, such as → Won |
Rule of thumb: a form for newsletter signups as they happen, a tag for labelling people later, such as “customer” when a deal is won.
Setting it up
- Open your site in the editor, open Settings and go to the Forms tab.
- Under Destinations, click Add and choose Kit.
- Give it a Name and choose the Form scope (which of your PageFork forms feeds it).
- Choose the Triggers.
- Paste the Kit API key. PageFork checks it with Kit straight away and tells you if Kit rejects it.
- Choose the Target (Form or Tag) and enter its id.
- Set Email field to the field in your form that holds the
visitor’s email address. It’s usually
email. - Optionally set First name field, so Kit can greet people by name.
- Click Create Kit destination.
Your API key is stored encrypted. Afterwards PageFork only ever shows its last few characters.
A note on the first name
Kit has a single first-name box. If your form has one name field
where people type their full name, the whole thing (“Ada Lovelace”)
lands in Kit’s first name, and your emails would open with “Hi Ada
Lovelace”. If that matters, give your form a separate first-name field
and map that one, or leave First name field empty.
Confirmation emails (double opt-in)
Kit decides whether people get a confirmation email, not PageFork.
In Kit, open the form, then Settings → Confirmation email:
- With Send confirmation email on, new subscribers arrive as Unconfirmed and Kit emails them a link. They become confirmed when they click it.
- With Auto-confirm new subscribers on, they are confirmed immediately.
PageFork respects whatever you chose there and never overrides it. If confirmation emails aren’t arriving, the cause is in Kit: check that the form is published and that your Kit account’s own email address is confirmed.
Using stage triggers
You can subscribe or tag someone when their lead reaches a stage rather than when they submit. A common setup is a second Kit destination with New submission off, → Won on, and a customer tag.
When you pick a stage, PageFork switches the target to Tag for you, because a Kit form would send its confirmation email days later, when you move the lead, which reads oddly to the person receiving it. You can still choose Form if that’s really what you want.
Think about consent. A stage trigger adds someone to your mailing list when you move their lead, not when they asked to join. Only use it for people who agreed to marketing emails, for example through a consent checkbox on your form. PageFork shows a reminder when you select a stage.
Stage triggers only fire for leads that came from a form. See what fires a destination.
Testing it
There is no Send test button for Kit, deliberately: a test would subscribe a made-up person to your real list.
Instead, submit your live form once with your own email address. Then:
- In PageFork, open the destination. Recent deliveries should show
success. - In Kit, open Subscribers. Look under Unconfirmed too if your form uses a confirmation email.
What is and isn’t sent
- PageFork sends the email address and, if you mapped one, the first name. Nothing else from the form goes to Kit.
- People already in your Kit account are simply added to the form or given the tag. Their existing details aren’t overwritten.
- If a submission has no email address in the mapped field, the
delivery is marked
skipped. Nothing is sent and nothing counts as a failure.
Limits
- 3 enabled Kit destinations per site.
Troubleshooting
“Kit rejected this API key” when saving. You pasted the API Secret, a v4 key, or a key with a typo. Copy the v3 API Key again.
The destination was disabled with “invalid API key”. The key was regenerated or removed in Kit. Delete the destination and create it again with the current key.
Deliveries say success but I don’t see the subscriber. Look in
Kit’s Unconfirmed list. With a confirmation email on, that’s where
new people wait.
The subscriber is unconfirmed and no email came. That email is sent by Kit. Check the form is published and that Kit shows “Emails sent” above zero on the subscriber.
Deliveries say skipped. The Email field you mapped is empty
or missing on those submissions. Check the field name matches your
form.
A delivery failed with a 4xx. Kit refused that one request, usually because the form or tag id doesn’t exist. Check the id.