Send cart and order events
Connect
SPIRITT
RetenoReteno
Engagement powered by real behavior
SPIRITT keeps Reteno fed with the data that drives engagement. It upserts contacts in real time or 3,000 at a time, sends backend events for your workflows to act on, reads each contact's email, SMS and push history, and reports on segments, workflows and remaining quotas.
What you can do with Reteno.
Contacts always current
Real-time upserts and bulk imports of up to 3,000 contacts with fields, channels, time zones and address books.
Behavior that starts journeys
Backend events from your product, store or billing system sent to Reteno with full parameters.
Every message on record
Email, SMS, push, web push and App Inbox history per contact, plus segments, workflows and quota balance.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your engagement data and describe which customer behavior should shape messaging.
02
Connect Reteno
Connect Reteno, plus the product, store and billing systems that produce that behavior.
03
Hand over the mission
Hand over the data flow. SPIRITT builds the sync, sends the events and reports on what customers received.
Hand over a mission.
Choose a mission. Make it yours.
Put Reteno to work.
Engagement powered by real behavior
Questions
Reteno, with SPIRITT.
01Can SPIRITT create Reteno contacts?+
Yes. It upserts single contacts in real time and up to 3,000 at once with a deduplication strategy.
02Can it send events?+
Yes. It sends backend events for identified contacts with any parameters your workflows use.
03Can it see what a contact received?+
It lists a contact's email, SMS, push, web push and App Inbox messages for a date range.
04Can it see segments and workflows?+
It searches segments and workflows with their IDs, status and tags.
05Can it check quotas?+
It reads the balance, credit limit and remaining prepaid email and SMS quotas.
06How do I connect Reteno?+
Open a workspace, connect Reteno and the systems that produce customer behavior, then describe the data flow.