Integration

Zembula + Talon.One

In Talon.One you set the ID of each customer profile, and Zembula can read the profile by that ID. Zembula can show the loyalty scores on it in your email.

It's our business to grow yours

Book a demo

What Zembula can read from Talon.One

One is a promotion engine, and Zembula can read the loyalty and coupon data that it evaluates. A customer profile holds a person’s data, loyalty scores and custom attributes. You set the ID of each profile, called the integrationId, and Zembula can find the person by that ID. A loyalty member is a profile or a card that holds loyalty points.

Zembula can look it up by the profile ID or by the loyalty card ID. Coupons carry their entry, validation and redemption state, and Zembula can read them through the Management API. One also holds a catalog of cart items keyed by SKU, and stores keyed by a store ID. Zembula can read a profile through the Integration API.

Integration API keys are scoped to one environment. An admin or an Application admin makes Management API keys in the Campaign Manager. A campaign rule can also fire a webhook effect that sends a payload. Your contract can set how many webhooks you can create.

DataDetailLooked up byHow fresh
Customer profileA person’s data, loyalty scores and custom attributes.integrationId, the profile ID you setopen time
Loyalty memberA profile or a card that holds loyalty points.profile ID or loyalty card IDset at setup
CouponA coupon with its entry, validation and redemption state.set at setupopen time
Cart item catalogAn optional product catalog synced from a product information system.SKUset at setup
StoreA physical or digital sales channel.storeIntegrationIdset at setup

How the data arrives

  • API: Zembula can read profile data through the Integration API, and coupon data through the Management API.
  • Webhook: A campaign rule can fire a webhook effect that sends an HTTP request with a payload.
  • ESP merge tags: Talon.One lists integrations with Braze, Iterable, Customer.io, Bloomreach and Cordial. A merge tag carries the profile ID into the image URL.

What you need

  • An API key or a data export from Talon.One. Zembula sets up the connection for you.
  • An admin or Application admin, who creates the Management API key in the Campaign Manager.
  • The profile ID in your email service provider, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Management API: soft limit of 3 requests per second.Coupon reads through the Management API share this soft ceiling.
The maximum number of webhooks depends on the contract.Your contract can set how many webhooks you can create.

Ideas for email

  • Show a person’s loyalty points balance from the loyalty member in a loyalty email.
  • Insert a personal coupon code into a birthday email.
  • Show the loyalty score from the customer profile in a monthly email.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.