Integration

Zembula + GetResponse

GetResponse stores the products and brands that a contact bought, with the order count and the spend. Zembula can show that purchase data in an email image.

It's our business to grow yours

Book a demo

Zembula has built this integration.

What Zembula can read from GetResponse

GetResponse sorts people into campaigns, which are contact lists. Zembula can read a contact from a campaign by email address, with the name and every custom field value. The custom fields are the place where you store extra facts about a person, and each field has an ID that Zembula can read too. For contacts with ecommerce data, GetResponse also keeps the products and brands bought, the order count and the spend.

Zembula can read those figures for one contact. GetResponse can also send subscribe, unsubscribe and link click events to Zembula. You supply an API key from the API page of your account. A MAX account also sends an X-Domain header.

GetResponse limits the calls that each user can make, and it caps the requests that run at the same time. The email address reaches Zembula in the image URL, from a merge tag. The figures belong to one contact, so each person sees their own spend and brands.

DataDetailLooked up byHow fresh
ContactA person in a campaign, with name and email address.email addressopen time
Custom field valuesThe values of the custom fields stored on a contact.email addressopen time
Ecommerce purchase dataProducts and brands bought, order count and spend for a contact.contactset at setup
Custom field definitionA contact field definition with an ID.custom field IDopen time
CampaignA contact list with a name and an ID.campaign IDopen time

How the data arrives

  • API: Zembula can read contacts, custom fields and campaigns with your GetResponse API key.
  • Webhook: GetResponse can send subscribe, unsubscribe and link click events to Zembula.
  • ESP API: Zembula lists GetResponse as a connected email service provider and can read contact data from it.

What you need

  • A GetResponse API key, from the API page of your account.
  • For a MAX account, your domain in an X-Domain header.
  • The contact email address, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
30,000 API calls per 10 minutes and 80 per second, for each user.A burst of opens above this rate can fail.
Up to 10 simultaneous requests.Many opens at the same moment can fail.

Ideas for email

  • Use the ecommerce purchase data of a contact to feature a brand that the person bought.
  • Show a custom field value of a contact in a personalized block.
  • Show the order count of a contact in a loyalty block.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.