Integration

Zembula + FullStory

FullStory can stream high-value behavioral events to a webhook, and Zembula can use those events in your email. Zembula can also read user and session data through the FullStory API.

It's our business to grow yours

Book a demo

What Zembula can read from FullStory

FullStory records digital experience analytics, with session replay and behavioral data, and Zembula can read three kinds of it. A user is a known or anonymous visitor, and FullStory handles anonymous users as well as identified users. A user holds a uid, a display name, an email and a set of properties, and FullStory gives each user an ID. A session is a recorded visit, and the Sessions API returns session data and summaries.

FullStory says the Sessions API combines session data with generative AI for real-time experience solutions. Streams is the third kind. Streams sends high-value behavioral events to a webhook as they happen, and Zembula can receive them. Your team starts by creating an API key in FullStory.

A user is found by uid or by the FullStory ID, and your email service provider sends the uid in the image URL. FullStory names no lookup value for a session. Streams and the Sessions API belong to Fullstory Anywhere. Freshness is set at setup for each kind of data.

DataDetailLooked up by
User propertiesuid, display name, email and properties of a known or anonymous visitor.uid or Fullstory id
Session data and summariesRecorded visits, returned by the Sessions API.set at setup
Streams behavioral eventsHigh-value behavioral user events, sent to a webhook.set at setup

How the data arrives

  • API: Zembula can connect with your FullStory API key and read user and session data.
  • Webhook: Streams can send high-value behavioral user events in real time to a webhook endpoint that Zembula sets up.
  • ESP merge tags: Your email service provider sends the uid in the image URL.

What you need

  • An API key or a data export from FullStory. Zembula sets up the connection for you.
  • Fullstory Anywhere, for session data and Streams events.
  • A uid in your email service provider, sent as a merge tag in the image URL.

Limits to plan for

LimitWhat it means
Streams and the Sessions API belong to Fullstory Anywhere.You need that plan level to use session data and Streams events.

Ideas for email

  • Send a recovery email when Streams reports a friction event for a person.
  • Use user properties to choose the offer in an email.
  • Link to a session summary in a support follow-up email.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.