Integration

Zembula + Kit (ConvertKit)

Kit (ConvertKit) stores purchase records that come from a store, and Zembula can read them by purchase ID. An image can then show a follow-up product block that matches a purchase record.

It's our business to grow yours

Book a demo

What Zembula can read from Kit (ConvertKit)

Kit is an email platform for creators, built around subscribers, tags, forms, sequences and broadcasts. Its public REST API lets Zembula read a subscriber, with the state of the person and the values of custom fields. A tag is a label on subscribers, and Zembula can read the tags of one subscriber. Custom fields are attributes that you store on subscribers, such as a first name.

A purchase is a record that you import from a store, and Zembula can find it by purchase ID. Kit can also send webhooks. You choose between an API key and OAuth. An API key reaches your own account only.

Bulk endpoints and apps need OAuth. The account plan must be eligible for API use. Kit sets a rate limit for each key and each token, and the limits appear below. The subscriber ID reaches Zembula in the image URL, from a merge tag of your Kit email.

With that ID, Zembula can read the tags and custom field values of the one subscriber who opened the email.

DataDetailLooked up by
SubscriberA person on the list, with state and custom field values.subscriber ID
TagA label on subscribers.subscriber ID
Custom fieldA custom attribute stored on subscribers.set at setup
PurchaseA purchase record imported from a store.purchase ID

How the data arrives

  • API: Zembula can read subscribers, tags, custom fields and purchases through the Kit REST API.
  • Webhook: Kit supports webhooks that can send events to Zembula.

What you need

  • An API key or a data export from Kit. Zembula sets up the connection for you.
  • A Kit plan that is eligible for API use.
  • The subscriber ID, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
API key: 120 requests in 60 seconds, for each API key.A burst of opens above this rate can fail.
OAuth access token: 600 requests in 60 seconds, for each access token.A burst of opens above this rate can fail.
The account plan must be eligible for use with the API.An ineligible plan cannot connect to Zembula.

Ideas for email

  • Use the tag of a subscriber to fill a broadcast with the matching image.
  • Show a custom field value, such as first name, in a block.
  • Use a purchase record to pick a follow-up product block.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.