The integration synchronizes subscriber data and event streams from Sesamy directly to Rule, enabling you to create automated and personalized customer journeys throughout the entire subscription lifecycle.
With the integration, you can trigger the right communication at the right time — from onboarding and renewals to win-back and loyalty communications — without the need for custom development.
Automatically sync subscriber data and audiences from Sesamy to Rule
Activate event streams for automated campaigns and customer journeys
Personalize communication based on subscription type and behavior
Create onboarding, renewal, and win-back flows
Send transactional emails and digital receipts through Rule
Installation
To activate the integration, you need to share the following information with Sesamy.
In Rule, go to: Settings > API. Then generate an API key and share it with Sesamy.
If you are using a custom API endpoint, a separate API URL can also be provided.
Once the integration is activated, subscriber data, tags, and events will automatically be synchronized from Sesamy to Rule.
Datafields sent to Rule
The integration synchronizes Sesamy's standard tags, as well as a base tag (sesamy) that is always added.
Subscriber
Subscriber.Email
Subscriber.FirstName
Subscriber.LastName
Subscriber.Phone
User
Sesamy_User.ID
Sesamy_User.Created
Billing Address
Sesamy_BillingAddress.FirstName
Sesamy_BillingAddress.LastName
Sesamy_BillingAddress.Street
Sesamy_BillingAddress.City
Sesamy_BillingAddress.Zip
Sesamy_BillingAddress.Country
Active Products
Sesamy_ActiveProducts.SKU
Sesamy_ActiveProducts.Titles
Sesamy_ActiveProducts.OptionTitles
Subscription
Sesamy_Subscription.Status
Sesamy_Subscription.ExpiresAt
Sesamy_Subscription.CanceledAt
Sesamy_Subscription.CreatedAt
Important information
Guest users are not synchronized
Temporary guest accounts created during purchase or checkout are not synchronized to Rule. Only users with confirmed accounts are included in the synchronization.
Date format
All date fields are sent in the format YYYY-MM-DD, for example ExpiresAt, CanceledAt, and CreatedAt.
Product deduplication
If a user has multiple contracts or subscriptions for the same product, product information is deduplicated based on the product’s slugified title.
Phone number priority
If multiple phone numbers are registered, the following priority order is used:
Mobile phone number
Default phone number
Work phone number
Home phone number