Integration guide
Sales and Marketing
Ground Agentforce in the Iterable lifecycle data behind every customer
Iterable is a growth marketing platform built for consumer and SaaS teams running multi-channel lifecycle campaigns — email, push, in-app, and SMS — across complex user journeys. Salesforce holds the commercial and service record for those same customers. When Emerge Digital connects both to Agentforce, a service or sales agent engaging a customer can read which Iterable campaigns and workflows they are in, what lifecycle stage they reflect, and what channel engagement indicates about where they are in the product or purchase journey. The conversation can start from where the customer already is rather than treating them as a blank record in a CRM.
Discuss your Iterable integrationThe opportunity
What the connection unlocks
- Campaign and lifecycle stage queryable at conversation time: an agent can read which Iterable campaigns a customer is enrolled in and what lifecycle stage their behaviour reflects before engaging — so the conversation is contextualised to their actual journey rather than a default script.
- Engagement signal context: opens, clicks, and in-app events from Iterable campaigns become inputs an agent can reference so a follow-up acknowledges what communication has already happened rather than ignoring a campaign the customer recently engaged with.
- Workflow triggers from Salesforce events: when a Salesforce case closes, a deal closes, or a contract renews, an agent can trigger the appropriate Iterable workflow — a welcome series, an onboarding sequence, or a renewal campaign — so lifecycle marketing responds to commercial events automatically.
- Churn signal routing: Iterable event data often surfaces early churn signals — reduced engagement, dropped session frequency — that a service agent can read and act on before a customer reaches out to cancel.
Illustrative workflows
Where it can make a difference
These scenarios explain possible workflows. They are not claims of delivered client results; licensing, permissions and feasibility are confirmed during discovery.
Service conversation grounded in lifecycle stage
A customer contacts support. The agent reads their Iterable lifecycle stage — trial, active, at-risk — and recent campaign engagement before responding. A trial user asking a product question gets a different response than an at-risk customer with declining engagement: the agent's approach reflects where the customer actually is, not a generic service script.
Deal close triggers the onboarding campaign
A Salesforce opportunity closes. The agent triggers the Iterable onboarding workflow for the new customer — with the correct product, tier, and assigned CSM pre-populated from the deal data — so the onboarding communication starts immediately and is personalised to what was sold rather than a generic welcome sequence.
At-risk signal surfaces before the customer churns
Iterable event data shows a customer's in-app session frequency has dropped significantly. The agent surfaces this to the owning CSM in Salesforce with the relevant engagement history attached — so proactive outreach happens before the customer submits a cancellation request rather than after.
Why not a native Iterable–Salesforce sync?
Iterable can push events and user attributes to Salesforce as activity records or contact fields, and some teams configure this to keep records broadly aligned. This is useful for CRM hygiene but is not designed to make Iterable campaign enrollment, lifecycle stage, and engagement event data queryable by an Agentforce agent in real time. An agent cannot ask the native event sync which campaigns a customer is currently in, retrieve their lifecycle stage at conversation time, or trigger a specific Iterable workflow based on a Salesforce event with dynamic field values. Emerge Digital builds the retrieval and action layer that makes Iterable genuinely available to agents as live context.
Journey fit
Connect the workflow to the outcome.
Iterable's integration value spans the Engage and Optimize stages — it is where lifecycle marketing data accumulates and where the signals it captures about customer health and engagement are most decision-relevant for service and success agents. Grounding agents in Iterable data means every customer interaction reflects the full lifecycle picture rather than just the Salesforce case or opportunity in front of the agent.
Delivery
Built around your environment.
Emerge Digital connects Iterable to Salesforce Agentforce as a consulting engagement. We map which Iterable data types agents need — campaign enrollment, lifecycle stage, engagement events, and user attributes — configure real-time retrieval so agents can query this context during customer conversations, and define the Salesforce event triggers that should fire Iterable workflows. The integration is designed around how your lifecycle marketing and customer success teams use both platforms.
Explore AI and automationPractical questions
Before we connect.
Can the agent send messages via Iterable channels directly?
Yes, when you want it to. Triggering an Iterable workflow from a Salesforce event is one of the most common use cases — the agent fires the campaign, Iterable handles channel delivery. Direct message sends via the agent are also configurable where that is appropriate.
How is this different from the ActiveCampaign or Eloqua integrations?
The retrieval pattern is similar — agents read campaign and lifecycle data to inform conversations. Iterable is typically the platform for consumer SaaS and growth companies running multi-channel lifecycle programmes across email, push, and in-app. ActiveCampaign fits SMB, and Eloqua fits large enterprise. The integration design adapts to whichever platform your marketing team operates.
Do we need an Iterable account to use this?
Yes. This integration assumes your organisation already holds an Iterable subscription. Emerge designs the connection between Iterable and Agentforce; we are not an Iterable reseller.
How long does an Iterable + Agentforce integration take?
A focused engagement typically runs three to six weeks: mapping which Iterable campaign and event data agents need, configuring retrieval for lifecycle stage and engagement context, defining the Salesforce event triggers for Iterable workflow fires, and testing service and onboarding workflows. Complexity scales with the number of lifecycle stages and campaign types in scope.
Keep exploring
Related integrations
Start with one useful connection.
Tell us which workflow needs to improve. We will map the systems, access rules and success measures with you.
Talk to Emerge