Salesmanago
The Sesamy Salesmanago integration syncs contact data, custom properties, and tags to your SALESmanago account, keeping segments accurate by removing stale Sesamy tags when subscriptions end.
Overview
SALESmanago is a marketing automation platform. Once connected, Sesamy automatically creates or updates a contact in your SALESmanago account (keyed by email) whenever a user registers, purchases a subscription, or updates their profile. Each contact receives identity data, a set of Sesamy_-prefixed custom properties for campaign personalisation, typed date fields for date-range conditions, and sesamy_* tags for segmentation.
Setup
To connect Salesmanago, provide the following credentials to Sesamy support.
| Field | Type | Description |
|---|---|---|
endpoint | string | API host from the key screen, e.g. app3.salesmanago.com |
clientId | string | Client identifier from the key screen |
apiKey | string | API key from the key screen |
sha | string | Precomputed SHA-1 hash from the key screen (40 hex characters) |
owner | string | Email of an active SALESmanago user account that should own the synced contacts |
1. API v2 Credentials
Log in to SALESmanago and open Settings → Integration Center → API → API v2. Copy the endpoint, clientId, apiKey, and sha exactly as shown on the key screen.
The sha is precomputed by SALESmanago as sha1(apiKey + clientId + apiSecret), so your API secret is never entered into Sesamy or transmitted anywhere.
2. Owner
The owner is not shown on the key screen. Provide the email address of any active SALESmanago user account in your organisation — this account will own the contacts Sesamy syncs.
3. Create the Sesamy Dictionary Details
Required setup — typed date fields must be created manually
SALESmanago does not auto-create dictionary details, and there is no API to create them — values sent for a detail that doesn't exist are silently ignored. Before the subscription date fields will appear, you must create each of the following manually under Settings → Other → Dictionary Details, with the exact name and type DATE:
Sesamy_SubscriptionStartAtSesamy_SubscriptionNextPaymentAtSesamy_SubscriptionLastPaymentAtSesamy_SubscriptionExpiresAtSesamy_SubscriptionWillCancelAtSesamy_SubscriptionEndedAt
Until these exist, contacts, tags, and text properties still sync normally — only the typed dates are skipped.
4. Complete the Setup
Send the five credential values to Sesamy support to finalise the integration.
What Gets Synced
Contact Data
| Field | Type | Description |
|---|---|---|
email | string | Always synced. Contact identifier |
name | string | First and last name in a single field |
phone | string | Phone number from the Sesamy profile |
externalId | string | The user's unique Sesamy ID |
| Billing address | object | Street, zip, city, country — only when a billing address is set |
Phone number priority
When multiple phone numbers exist on the Sesamy user profile, the integration uses this priority chain: mobile, default, work, home.
Properties
Sesamy maintains two kinds of custom properties on each contact.
Text properties
These are flat string properties under the Sesamy_ prefix, refreshed on every sync. List values are comma-joined.
| Property | Description |
|---|---|
Sesamy_User.FirstName / Sesamy_User.LastName / Sesamy_User.ID / Sesamy_User.Created | User profile data |
Sesamy_BillingAddress.* | Billing address fields, only when a billing address is set |
Sesamy_ActiveProducts.SKU / Sesamy_ActiveProducts.SKUAndPO / Sesamy_ActiveProducts.Titles / Sesamy_ActiveProducts.OptionTitles | Comma-joined lists of the user's active products |
Sesamy_ArticlePurchase.Count / Sesamy_ArticlePurchase.Latest / Sesamy_ArticlePurchase.SKU | Article purchase summary |
Sesamy_IssuesRemaining.Count | Issues remaining — publication subscriptions only |
Sesamy_Subscriptions.HasActive / Sesamy_Subscriptions.Active / Sesamy_Subscriptions.Canceled / Sesamy_Subscriptions.Expired / Sesamy_Subscriptions.Ended | Aggregate subscription counts |
Sesamy_Subscription.ContractType | Contract type of the primary active contract |
Per-product detail lives in tags
The integration does not create per-product property blocks. Which products, SKUs, and purchase options a contact has is carried by sesamy_* tags — SALESmanago's segmentation primitive — while properties carry the bounded fields a campaign personalises on. This mirrors the Mailchimp integration.
Typed date properties
These are sent as typed DATE dictionary details, so you can build date-range conditions on them in campaigns. They require the one-time manual setup described in Setup. Each date is set only when applicable.
| Detail | Description |
|---|---|
Sesamy_SubscriptionStartAt | When the subscription started (survives renewals) — tenure and anniversary campaigns |
Sesamy_SubscriptionNextPaymentAt | Next scheduled payment — renewal reminders for recurring subscriptions |
Sesamy_SubscriptionLastPaymentAt | When the user was last billed |
Sesamy_SubscriptionExpiresAt | When the contract expires — fixed-term (RENEWABLE) contracts only |
Sesamy_SubscriptionWillCancelAt | Scheduled cancellation date, while the subscription is still active — pre-churn win-back |
Sesamy_SubscriptionEndedAt | When the subscription actually ended — post-churn win-back |
Sesamy_SubscriptionWillCancelAt and Sesamy_SubscriptionEndedAt are mutually exclusive in time: the first is set while the contact is still a subscriber (about to leave), the second after they have churned.
Tags
Standard Sesamy tags plus a base sesamy tag are synced to contact records. See Integration Concepts for the complete tag reference.
SALESmanago tags allow only letters, digits, and underscores, so tags are sanitised by replacing any other character with _ (for example premium-magazine becomes premium_magazine).
Tags are merged on every sync:
- New
sesamy_*tags are added - Outdated
sesamy_*tags are removed, so segments stay accurate when a subscription ends - External tags (those not starting with
sesamy_) are preserved
This means your manually added tags and tags from other tools are never affected.
Events
The Salesmanago integration responds to all eight standard Sesamy events. Every event triggers a sync of the contact's data, properties, and tags.
See Event Types for the full list of events.
Using This Data for Campaigns
Segmentation Ideas
- Active Subscribers -- segment on the
sesamy_active_subscribertag orSesamy_Subscriptions.HasActive - Renewal Reminders -- date-range condition on
Sesamy_SubscriptionNextPaymentAt(recurring) orSesamy_SubscriptionExpiresAt(fixed-term) - Pre-churn Win-back --
Sesamy_SubscriptionWillCancelAtis set: the contact has scheduled a cancellation but is still a subscriber - Post-churn Win-back -- date-range condition on
Sesamy_SubscriptionEndedAt - Anniversary Campaigns -- date-range condition on
Sesamy_SubscriptionStartAt - Engaged Readers -- segment on the
sesamy_made_single_purchasetag orSesamy_ArticlePurchase.Count
Personalisation
Drop property values into your SALESmanago templates to personalise content -- for example referencing Sesamy_IssuesRemaining.Count in renewal nudges, or Sesamy_ActiveProducts.Titles in product-specific messaging.
Important Notes
- Dictionary details require manual setup -- the typed date fields only appear after you create them in SALESmanago (see Setup). They are synced best-effort and never block the main contact sync.
- Subscription counts are text -- SALESmanago number fields cannot hold
0, so theSesamy_Subscriptions.*counts are synced as text properties. Segment "has an active subscription" via thesesamy_active_subscribertag orSesamy_Subscriptions.HasActiveinstead. - Guest users are not supported -- temporary guest accounts created during checkout are excluded from sync.
- Users without email are skipped -- the integration requires an email address to create or update a contact. Users without one are silently skipped.
- Tag safety -- only
sesamy_*tags are modified. External tags are never removed. - No consent flags are sent -- marketing opt-in is governed by your SALESmanago account defaults, not by Sesamy.
Alternative Integration Method
For more advanced integrations, you can use both APIs directly:
- Use Sesamy Webhooks to receive subscription events
- Call the SALESmanago API to manage contacts
Next Steps
- Integration Concepts -- shared concepts, event types, and tag reference
- Mailchimp -- email marketing with merge fields and activity tracking
- Rule -- Nordic marketing automation with 50+ custom fields
- Mailmojo -- contact and tag sync with conditional field updates
- Handling Webhooks -- build your own webhook endpoint