Integration

Zembula + BigCommerce

BigCommerce passes an abandoned cart token to the storefront when a person clicks an abandoned cart email link, and Zembula can use that token to find the cart. Zembula reads your store’s product catalog through a connection that your team sets up with store credentials.

It's our business to grow yours

Book a demo

Zembula has built this integration.

What Zembula can read from BigCommerce

BigCommerce is a SaaS ecommerce platform with REST and GraphQL APIs for catalog, customers and orders. Zembula reads the store’s product catalog through a connection that your team sets up by pasting store credentials. Zembula can read three kinds of data. A Product is a catalog item, and Zembula finds it by its product ID.

A Customer is a person’s record, with addresses, attributes, form field values, stored instruments and consent settings. Zembula can find it by customer ID or email address. An abandoned cart is a cart that a person left behind. Zembula can find it by the token that BigCommerce passes to the storefront when the person clicks the abandoned cart email link.

Your team creates a store API account, which gives an access token for the X-Auth-Token header. Sandbox stores are for testing and cannot process transactions. BigCommerce also sends real-time store event notifications by webhook, and Zembula can use them. Several email service providers connect to BigCommerce.

The lookup value can arrive as a merge tag, or you can place the product ID in the email HTML.

DataDetailLooked up by
ProductsA catalog item of your store.product ID
Customer recordsA person’s record, with addresses, attributes and consent settings.customer id or email
Abandoned cartsA cart that a person left behind.abandoned cart token

How the data arrives

  • API: Zembula reads the product catalog with your store credentials, and can read customer records and abandoned carts with a store access token.
  • Webhook: BigCommerce sends real-time store event notifications, and Zembula can use them.
  • ESP merge tags: The lookup value reaches Zembula in the image URL, from a merge tag.
  • Product ID in the email HTML: Place the product ID in the email HTML, and Zembula reads the product.

What you need

  • A store API account in BigCommerce, which gives an access token for the X-Auth-Token header.
  • Your store credentials, which your team pastes in Zembula to set up the connection.
  • A product ID, customer ID or cart token, sent as a merge tag in the image URL.

Ideas for email

  • Recommend products from the catalog in a browse-abandon email.
  • Link an abandoned cart email back to the cart, using the cart token.
  • Use the consent settings of a customer record to decide who gets a promotion.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.