Engagement signals are trapped in Customer.io
Your reps live in Salesforce. The data they need lives somewhere else — and reaches them as a weekly campaign export, if at all.
Real-time email engagement and website activity for every Contact, right where your team works. Two-way integration with Customer.io's Pipelines CDP and App API — no middleware, no external hosting.
| Subject | State |
|---|---|
| Q4 Pricing Recap | Clicked |
| Enterprise plans walkthrough | Opened |
| Customer story · Northwind | Clicked |
| ROI calculator update | Opened |
| New case studies | Opened |
Marketing has the signal. The team in Salesforce doesn't see it until it's too late.
Your reps live in Salesforce. The data they need lives somewhere else — and reaches them as a weekly campaign export, if at all.
A prospect opens your campaign, clicks through, views three key pages — and signs with a competitor before anyone notices.
Stage changes, status flips, ownership transfers — operational truth that should personalize messaging is stuck in SOQL, never reaching the marketing tool.
CIO Pipelines reads from Customer.io and writes to Customer.io — natively, inside Salesforce.
A Lightning record-page panel showing email events, page views, KPI cards, and an engagement banner that updates the moment Customer.io reports new signal.
Read the deep-diveThree list widgets (My / Team / Pipeline) plus four aggregate engagement banners. Drop them on any App, Home, or Tab page — scoped automatically by ownership and team.
Read the deep-diveConfigurable Apex triggers turn Salesforce DML into Customer.io identify, track, and group events. Field mappings, transformations, and filters are admin-controlled.
Read the deep-diveA Lightning record-page panel that shows the email events, page views, and KPIs that matter — driven by a colored banner that grades the strongest available signal.
Marcus Chen is browsing your site — 4 key pages today.
My shows what you own. Team uses your manager hierarchy, group, queue, or a custom strategy. Pipeline covers everything you can see via Salesforce sharing — with an optional unassigned pool.
Four aggregate banners (Contact, My, Team, Pipeline) render a one-line headline and a count. Drop them above any Lightning page or the App Home — your team sees signal without opening anything.
{name}, {minutes}, {pageTitle} placeholders.Apex triggers send Pipelines CDP events the moment Salesforce records change. Field mappings, filters, and transformations are configured in the admin UI — no Apex required.
CIO Pipelines ships with sensible defaults. Every label, message, KPI, URL pattern, and team scope is rewritable from the admin UI — without a deploy and without code.
OwnerId by default, or any user-lookup like Account_Manager__c or Recruiter__c.Native Apex on the platform, native LWCs in the UI, the public Customer.io APIs at the edges. Nothing else in the data path.
Install the managed package, drop in your Customer.io API keys, pick your region. Five minutes.
Pick which Salesforce events become CDP identify / track / group events. Map fields. Add filters.
Open Lightning App Builder. Drag the Contact Activity panel and the dashboard widgets onto the canvas. Save and activate.
Same Apex, same LWCs, same security model. The only thing that changes is the words.
A 30-account named territory is a lot to keep tabs on. The Pipeline widget surfaces the buyers re-engaging with pricing, demo, and trial pages — the moment they do.
CFO at Northwind — viewed /pricing twice this week.
A candidate opens your latest campaign, clicks through, views three job postings — and the recruiter sees a HOT row light up before the moment passes.
Sarah Johnson is actively job-shopping — viewed /jobs/senior-engineer.
Place the Contact Activity panel on the Case record page. Support sees whether the customer is a high-engagement repeat buyer or a one-time browser — before they reply.
Repeat customer — 6 product views today, 4 orders this year.
CIO Pipelines surfaces Customer.io data inside the Salesforce UI and ships Salesforce events into the Pipelines CDP — a two-way integration built natively on the public Customer.io APIs as designed.
The package complements Customer.io rather than competing with it: every rep watching the dashboard sees Customer.io's signal in real time, every day, inside the system of record.
Native Apex + Lightning Web Components. The integration is not a JavaScript shim — it's a managed package built to enterprise Salesforce standards.
B2B sales, staffing & recruiting, freight, real estate, financial services — verticals where Salesforce is the system of record and Customer.io is the engagement engine.
Outbound via the Pipelines CDP API. Inbound via the App API. Public endpoints, documented patterns, no reverse-engineering.
"Built for Customer.io" branding visible across the product. Shared collateral, joint case studies, and aligned go-to-market for shared accounts.
Strict sharing, FLS-enforced SOQL, encrypted credentials, constant-time HMAC, no dynamic SOQL injection surface. The package is auditable end-to-end and deployable to security-sensitive enterprise orgs.
Read the security architectureWITH SECURITY_ENFORCED on all @AuraEnabled SOQL. isCreateable() / isUpdateable() gates on every DML.
EncryptedText for both API keys. Subscriber admins see masked values; the unmasked key never reaches the browser.
Inbound webhook verification is timing-safe. Per-config secrets, no parser leaks, generic error responses.
The only outbound HTTP traffic is to cdp.customer.io and api.customer.io (or their EU equivalents). No telemetry leaves the org.
Activity log bodies retained 30 days by default (admin-tunable, 7-day floor). Daily purge batch ships in the package.
Every controller is with sharing. No class is without sharing. Service classes use inherited sharing.
Three tiers. Pick by event volume and support level. No per-user fees.
Single-workspace teams getting started.
Billed annually
Multi-workspace teams with higher event volume.
Billed annually
Custom deployments, compliance, dedicated support.
Annual or multi-year
All tiers include the full Lightning UI, the outbound CDP integration, every per-widget admin setting, and free sandbox installs.
Install in your sandbox in five minutes. Configure your first event trigger in another five. Drop the widgets on your Lightning pages, and watch the engagement signal show up.