Integration

Zembula + Radar

Radar records an event each time a person enters or leaves a geofence or a place, and Zembula can use those events in your email. Zembula can read the person’s current location when the email opens.

It's our business to grow yours

Book a demo

What Zembula can read from Radar

Radar knows where a person is, and Zembula can read that location when the email opens. Radar tracks each person as a user. A user record holds the current location, the geofences that the person is inside, the current place and the country. It also holds user metadata.

Zembula can look up a user by Radar ID, user ID or device ID. Radar also records events, such as entering or leaving a geofence or a place. Each event carries its type, the geofence, the place, the location, a confidence value and a duration. Radar can post these events to a webhook as they happen.

Radar also sends location events and user attributes to Braze, Iterable, Cordial, Attentive and Salesforce Marketing Cloud. A read by API uses a Secret key from the Radar dashboard. Radar sets a default of 10 requests per second when you list users. Radar can raise that rate on request.

DataDetailLooked up by
Current locationWhere Radar last placed the person.Radar ID, user ID or device ID
Geofences the person is inThe geofences that contain the person’s location.Radar ID, user ID or device ID
Current place and countryThe place and the country for the person’s location.Radar ID, user ID or device ID
User metadataThe metadata stored on the user.Radar ID, user ID or device ID
Location eventsGeofence and place entry and exit events, with type, confidence and duration.Radar ID

How the data arrives

  • API: Zembula can read users and events with your Secret key from the Radar dashboard.
  • Webhook: Radar posts event and user data to a URL when it generates an event.
  • ESP merge tags: Radar sends location events and user attributes to Braze, Iterable, Cordial, Attentive and Salesforce Marketing Cloud.

What you need

  • A Radar Secret API key from the dashboard settings. Server reads use the Secret key.
  • The Radar ID, user ID or device ID, sent as a merge tag in the image URL.
  • An API key or a data export from Radar. Zembula sets up the connection for you.

Limits to plan for

LimitWhat it means
Listing users allows 10 requests per second by default.Radar can raise this rate on request.

Ideas for email

  • Show a store offer in the image when the person is inside a store geofence.
  • Show the current place of a person in a visit email.
  • Show a thank-you image after a store visit event.

Last checked: 19 November 2026.

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

See how we do it by booking a demo.