Integration

Zembula + Simon AI

Simon AI lets you choose which contact fields count as content, and Zembula can show those fields in your email. Zembula reads a contact’s profile fields from Simon by email address.

It's our business to grow yours

Book a demo

Zembula has built this integration.

What Zembula can read from Simon AI

Zembula reads a contact’s profile from Simon AI by email address and renders it in an email at the moment that a person opens it. The profile holds the fields that your team sets as content in Simon. These include first name, city, state, total lifetime value and flow variant membership. Only the fields set as content appear.

Simon also keeps lookup tables for data that does not belong to a contact, such as a product catalog. Your team stores a key with the contact, for example a SKU, and Simon reads the catalog row by that key. An organization can keep up to 10 lookup tables. Simon inserts lookup data into an email through the substitution tags of your email service provider.

Simon Mail also sends webhook events for messages, tracking and unsubscribes. Simon applies a rate limit across all requests of your organization. The Audience API is a premium add-on, and your Client Solutions Manager issues the bearer token.

DataDetailLooked up byHow fresh
Contact profile fieldsThe fields that you set as content, such as first name, city and state.emailopen time
Total lifetime valueThe lifetime value that Simon holds for one contact.emailopen time
Flow variant membershipThe flow variant that a contact belongs to.emailopen time
Lookup table rowNon-contact data, such as a product from a catalog.key such as SKUsend time
Simon Mail eventsMessage, track and unsubscribe events from Simon Mail.set at setupset at setup

How the data arrives

  • API: Zembula reads a contact’s profile fields from Simon by email address through the Audience API.
  • Webhook: Simon Mail can send message, track and unsubscribe events to Zembula.
  • ESP merge tags: Simon inserts lookup and contact data into your ESP template with substitution tags.

What you need

  • The Simon Audience API, a premium add-on, and a bearer token from your Client Solutions Manager.
  • The contact’s email address in your email service provider, sent as a merge tag in the image URL.
  • A key stored with the contact, such as a SKU, to read a lookup table row.

Limits to plan for

LimitWhat it means
50 requests per second across all requests from one organization.Open-time reads share this limit with your other Simon calls.
Simon Audience API is an optional premium add-on.Your Simon plan must include it before Zembula can read contacts.
A maximum of 10 lookup tables.Plan your catalogs to fit within 10 tables.

Ideas for email

  • Fill an email image from a contact’s total lifetime value.
  • Show the catalog product for the SKU stored on the contact.
  • Branch an email on the flow variant that the contact belongs to.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.