Sync trusted traits and product events
Connect
SPIRITT
Customer.ioCustomer.io
Signals to messages
SPIRITT maintains Customer.io profiles and events, checks segment membership, and triggers existing broadcasts. Give it ownership of the data and operations that keep your messaging relevant.
What you can do with Customer.io.
Profiles that reflect reality
Carry verified traits, account relationships, and product activity into Customer.io so existing journeys work from current customer context.
Controlled broadcast runs
Check existing segment membership, trigger the right broadcast, and reconcile trigger records with available message delivery metrics.
Systems beyond the send
Build audience review tools, event collection workflows, and delivery dashboards that connect Customer.io activity to your business records.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for lifecycle messaging, customer data quality, or broadcast operations.
02
Connect Customer.io
Connect Customer.io with an API key for the intended workspace and the access your mission needs.
03
Delegate an outcome
Give SPIRITT a concrete mission, such as syncing activation events or operating an existing broadcast with audience checks.
Hand over a mission.
Choose a mission. Make it yours.
Put Customer.io to work.
Put your lifecycle messaging to work
Questions
Customer.io, with SPIRITT.
01What can SPIRITT change in Customer.io?+
SPIRITT can identify people and assign traits, add people to groups, create profile aliases, and record events, page views, and screen views. It can also trigger existing broadcasts, report device-side push events, handle delivery unsubscribe requests, and suppress explicitly designated profiles.
02What access does a Customer.io mission need?+
Customer.io connects using an API key. Use access for the intended workspace and mission, then provide the relevant campaign or segment IDs, customer identifier rules, and authoritative source for profile traits. Those inputs keep updates and sends tied to the right records.
03Can SPIRITT create campaigns or edit message templates?+
The available actions support triggering existing broadcasts and inspecting trigger records, not creating campaigns or editing templates. SPIRITT can list newsletters, transactional template IDs and names, and snippets to inventory messaging assets, then operate the surrounding audience, event, and delivery workflows.
04How can it connect product and billing data to messaging?+
SPIRITT can use connected product or billing records to update Customer.io profile traits and submit verified customer events. Existing Customer.io journeys can respond according to their configured rules. Segment membership checks and message records help reconcile who qualified and what was sent.
05What custom systems can it build around Customer.io?+
Useful builds include a broadcast run console, validated event intake service, custom email unsubscribe endpoint, and audience reconciliation dashboard. These systems can retain execution history and exception queues while Customer.io remains the destination for profiles, activity, and broadcast execution.
06How are unsubscribe, suppression, and aliases different?+
A delivery unsubscribe action handles an email unsubscribe request. Suppression permanently deletes a profile and prevents re-adding the same identifier, so it needs an explicitly authorized target. An alias joins identifiers for the same person and requires a verified identity match; it is not an unsubscribe or deletion action.