Integration

Zembula + Amperity

Amperity joins fragmented records into one unified profile for each person, and Zembula can read that profile. Zembula can read it through the Amperity Profile API when the email opens.

It's our business to grow yours

Book a demo

What Zembula can read from Amperity

Amperity connects fragmented records into unified profiles, and each profile brings history and behavior signals together for one person. Zembula can read that profile through the Amperity Profile API and render values from it in an email at the moment of an open. Amperity names three uses for a profile: segmentation, analysis and activation. Zembula can read the same profile for an email image.

Your team and Zembula agree on the lookup value at setup. The value reaches Zembula in the image URL, from a merge tag of your email service provider. A user with the Allow API key administration policy creates the API key. Keys belong to one tenant, so requests name the tenant.

Sandboxes do not receive a copy of the key. Amperity sets two rates. The Amperity API allows 10 requests per second. The Profile API allows 2000 requests per second across the whole tenant, sandboxes included.

Open-time reads count against this tenant-wide rate.

DataDetail
Unified profileOne resolved person, built from fragmented records.
Person historyThe history that Amperity joins into the profile.
Behavior signalsThe available behavior signals that sit in the profile.

How the data arrives

  • API: Zembula can read the unified profile through the Amperity Profile API with an API key from your tenant.
  • ESP merge tags: Your email service provider sends the lookup value as a merge tag in the image URL.

What you need

  • An Amperity user with the Allow API key administration policy creates the API key.
  • Your tenant name. API keys work only in the tenant that issued them.
  • An API key or a data export from Amperity. Zembula sets up the connection for you.
  • A lookup value for each person in your email service provider, sent as a merge tag.

Limits to plan for

LimitWhat it means
Amperity API: 10 requests per second.Amperity sets this rate for its general API.
Profile API: 2000 requests per second across the whole tenant, including sandboxes.Open-time reads share this rate with your sandboxes.

Ideas for email

  • Fill an email image with values from a person’s unified profile.
  • Show an image that follows the history in a person’s profile.
  • Choose an image from the behavior signals in a person’s profile.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.