Integration

Zembula + Drip

Drip keeps a lifetime value and a lead score on each subscriber, and Zembula can show them in your email. Zembula can read the subscriber by ID, email address or visitor UUID when the email opens.

It's our business to grow yours

Book a demo

What Zembula can read from Drip

Drip keeps a profile for each subscriber. The profile holds a Drip ID, an email address, a first and last name, tags, custom fields, a lifetime value and a lead score. Zembula can read that profile when a person opens your email, and it can find a subscriber by Drip ID, email address or visitor UUID. A tag or a lifetime value can decide which image a person sees.

Drip also names each custom field on its subscribers, and Zembula can read that list of custom field identifiers. Drip sends webhooks for subscriber events. These are subscriber created, custom field updated, email opened, email clicked, custom event performed and lifetime value updated. Drip accepts cart and product data written to it.

Its reference lists no endpoint to read them back, so Zembula does not read them. Drip allows 3,600 individual requests an hour on most endpoints. Zembula can connect with a Drip API key or with OAuth2. The subscriber email or ID reaches Zembula in the image URL, from a Liquid merge tag in your Drip email.

DataDetailLooked up byHow fresh
Subscriber profileDrip ID, email address, first name and last name of one subscriber.subscriber ID, email or visitor UUIDopen time
TagsThe tags that mark one subscriber.subscriber ID, email or visitor UUIDopen time
Custom fieldsCustom field values stored on one subscriber.subscriber ID, email or visitor UUIDopen time
Lifetime value and lead scoreTwo numbers that Drip keeps for one subscriber.subscriber ID, email or visitor UUIDopen time
Subscriber eventsCreated, field updated, email opened or clicked, custom event, lifetime value updated.set at setupset at setup

How the data arrives

  • API: Zembula can connect with a Drip API key or OAuth2 and read one subscriber by ID, email or visitor UUID.
  • Webhook: Drip can notify Zembula of subscriber events, such as an opened email or an updated lifetime value.

What you need

  • An API key or a data export from Drip. Zembula sets up the connection for you.
  • Your Drip account ID, which Zembula needs to address the API.
  • A subscriber ID or email from Drip, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
3,600 individual requests an hour for most endpoints.Open-time reads above that hourly rate can be refused.

Ideas for email

  • Show an image chosen by the subscriber’s lifetime value.
  • Pick an offer image by a tag on the subscriber.
  • Show a custom field value from the subscriber profile in the image.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.