Profile sync
Keep customer profiles up to date across systems.
Adobe Campaign Connector
Build in-app integrations that create or update profiles, start Campaign workflows and send transactional messages from your SaaS product using Adobe Campaign APIs and events.
Event-driven messages
Trigger transactional or targeted deliveries from product events.
Governed marketplace
Expose vetted actions to customers with role-based controls.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Teams can integrate profile and audience management, campaign deliveries, workflows and transactional messages between Adobe Campaign and their product — and subscribe to Adobe I/O Events for webhook-driven automation. See the Adobe Campaign Standard API docs for supported resources and examples. (experienceleague.adobe.com)
PRODUCT USE CASES
Top Use Cases for Adobe Campaign Integrations
Create reusable, multi-tenant integrations: sync customer profiles, trigger transactional email from app events, start or update Campaign workflows, and subscribe to I/O Events webhooks for real-time orchestration.
Sync SaaS users to Adobe Campaign profiles
Automatically create and update Adobe Campaign profiles when customer records change in your app using the Profiles APIs. (experienceleague.adobe.com)
Send transactional messages from product events
Trigger transactional emails or SMS using Adobe Campaign’s Transactional Message API when in-app events occur. (experienceleague.adobe.com)
Start or update Campaign workflows
Start, monitor or modify Campaign workflows programmatically to automate cross-channel campaign orchestration. (experienceleague.adobe.com)
ORCHESTRATION
How Adobe Campaign works with Cyclr
Cyclr sits between your SaaS product and Adobe Campaign to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Adobe Campaign
Adobe Campaign processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Adobe Campaign methods you can orchestrate through Cyclr.
Profiles5
Update Profile
ActionUpdates a Profile.
Get Profile
ActionGets a Profile.
Delete Profile
ActionDeletes a Profile.
Create Profile
ActionCreate a Profile.
List All Profiles
ActionGets a List of All Profiles.
Subscriptions5
List Profile Subscriptions
ActionGet a Profile's Subscriptions.
Delete a Service Subscription
ActionDelete a Profile's Service Subscription.
Delete a Profile Subscription
ActionDelete a Profile's Subscription.
Add Service Subscription
ActionAdd a Subscription to a Profile for a given Service.
List All Subscribed Profiles
ActionGet a List of Profiles Subscribed to a Service.
History1
Get Profile History
ActionGet a Profile's Marketing History.
Events1
Get Profile Events
ActionGet a List of Events for a Profile.
TECHNICAL DETAILS
Adobe Campaign integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Adobe Campaign integrations in Cyclr.
API and authentication
- API host
https://mc.adobe.io- Authentication
- Service Account (JWT); OAuth 2.0 (Server-to-Server)
- Credentials
Client ID; Client Secret; Private Key (certificate); Tenant/Organization ID; API Key. (community.cyclr.com)
- Method categories
Profiles; Workflows; Deliveries; Transactional messages; Custom resources. (experienceleague.adobe.com)
Pagination and rate limits
Pagination
Default 25 items; use _lineCount and _forcePagination=true and follow the response’s next node URL for pages. (experienceleague.adobe.com)
Rate limits
Rate limits and scale limits are defined by your Adobe license and instance; check your Adobe account and docs for quotas. (experienceleague.adobe.com)
IMPLEMENTATION
Authentication at a glance
Adobe I/O server-to-server OAuth (preferred) and legacy Service Account (JWT); obtain Client ID, Client Secret, private key and Tenant/Organization ID from Adobe Developer Console. (community.cyclr.com)
- Authentication method
- Service Account (JWT); OAuth 2.0 (Server-to-Server)
- Credential required
Client ID; Client Secret; Private Key (certificate); Tenant/Organization ID; API Key. (community.cyclr.com)
Before you begin:
View setup guideTenant ID comes from your Experience Cloud URL; JWT is deprecated—migrate to OAuth Server-to-Server. (community.cyclr.com)
COMMON QUESTIONS
Frequently asked questions
It integrates profile and audience management, campaign deliveries, transactional messages and workflow orchestration; you can also subscribe to Adobe I/O Events for webhook-driven automations. (experienceleague.adobe.com)
Use Adobe I/O server-to-server OAuth (preferred) or the legacy Service Account (JWT); obtain Client ID, Client Secret, private key and Tenant/Organization ID from Adobe Developer Console. (community.cyclr.com)
Yes. Cyclr supports white-label, multi-tenant embedding so you can publish per-customer Adobe Campaign automations inside your app while keeping centralized governance. (community.cyclr.com)
Yes. Cyclr can expose vetted connector actions (for example: profile CRUD, send transactional message, start workflow) as governed MCP tools with role-based controls and versioning. (community.cyclr.com)
KEEP EXPLORING
Related resources and connectors
Documentation
Email Marketing Integrations to make your daily tasks easier
Read more →ProductWhat is iPaaS?
Read more →ProductMCP PaaS
Read more →Related connectorBird
Related Customer Experience connector for customer-facing integration workflows.
Related connectorBluecore
Related Customer Experience connector for customer-facing integration workflows.
Related connectorLeadfox
Related Customer Experience connector for customer-facing integration workflows.