Customer-facing automations
Trigger email campaigns and journey actions from your app.
IBM Watson Marketing Connector
Embed Acoustic Campaign (formerly IBM Watson Marketing) capabilities directly into your product. Build in-app flows to add or update contacts, trigger email campaigns and programmatic audience syncs, and surface campaign reporting per customer account.
Multi-tenant orchestration
Orchestrate per-customer workflows and reuse across accounts.
Faster time to value
Ship integrations faster with Cyclr’s low-code flow builder.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate your SaaS product with Acoustic Campaign (IBM Watson Marketing) to manage contacts, audiences, trigger campaign sends and read campaign reporting programmatically. Acoustic exposes both REST and XML endpoints for contact upserts, list membership, program enrollment and campaign details; Cyclr orchestration connects those calls into reusable multi-tenant workflows. (developer.goacoustic.com)
PRODUCT USE CASES
Top Use Cases for IBM Watson Marketing Integrations
Quickly build in-app automations that add or update contacts, sync audiences and trigger campaign sends. Publish integrations through Cyclr’s white-label embedded marketplace so each customer connects their own Acoustic account and credentials.
Sync leads to Acoustic contacts
Add or update recipients (AddRecipient/UpdateRecipient) so your app’s leads become Acoustic contacts and appear in lists and audiences. (developer.goacoustic.com)
Trigger email campaigns and program enrollment
Enroll contacts in programs or trigger mailings and automated message groups (AddContactToProgram, SendMailing) from in-app events. (developer.goacoustic.com)
Manage contact lists and audiences
Create and modify contact lists, add contacts to lists and sync audience segments for targeting. (developer.goacoustic.com)
ORCHESTRATION
How IBM Watson Marketing works with Cyclr
Cyclr sits between your SaaS product and IBM Watson Marketing 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
IBM Watson Marketing
IBM Watson Marketing 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 IBM Watson Marketing methods you can orchestrate through Cyclr.
Contacts3
Get Contacts
ActionGets contacts by Database ID and lookup filter.
Get Contact
ActionGet a contact by ID.
Create or Update Contact
ActionUpsert a Contact with the given data. Custom fields should be added in the format of: "customFields.<<FieldName>>"
TECHNICAL DETAILS
IBM Watson Marketing integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing IBM Watson Marketing integrations in Cyclr.
API and authentication
- API host
https://api-campaign-{pod}.goacoustic.com- Authentication
- OAuth 2.0; Legacy JSESSIONID
- Credentials
Client ID; Client Secret; Refresh Token; Pod/API host selection; Legacy: username/password.
- Method categories
Read; Create; Update; Delete; Send campaigns; Manage contacts, lists and programs; XML and REST endpoints.
Pagination and rate limits
Pagination
Method-specific behavior should be confirmed before implementation.
Rate limits
OAuth: default 10 concurrent requests per organization. Legacy sessions limited to 20 active logins. Refresh tokens every ~3 hours recommended. (developer.goacoustic.com)
IMPLEMENTATION
Authentication at a glance
Acoustic Campaign uses OAuth 2.0 (client_id, client_secret, refresh_token → access_token valid ~4 hours). A legacy JSESSIONID login remains but is deprecated for new orgs. Confirm Cyclr-enabled option in Console. (developer.goacoustic.com)
- Authentication method
- OAuth 2.0; Legacy JSESSIONID
- Credential required
Client ID; Client Secret; Refresh Token; Pod/API host selection; Legacy: username/password.
Before you begin:
View setup guideOrg Admin must create OAuth app, client credentials and refresh token; choose correct pod/API host.
COMMON QUESTIONS
Frequently asked questions
You can programmatically add or update contacts, manage lists and audiences, enroll contacts into programs and trigger campaign sends and reporting reads using Acoustic’s XML and REST APIs. (developer.goacoustic.com)
OAuth 2.0: Cyclr uses client_id, client_secret and a refresh_token to request a 4‑hour access token; legacy JSESSIONID login is supported but deprecated. Org admin must provision credentials. (developer.goacoustic.com)
Yes. Each customer connects their own Acoustic org credentials (pod + OAuth app or legacy account) so Cyclr flows run per-tenant with separate credentials. Provisioning requires Org Admin access to create app credentials. (developer.goacoustic.com)
Yes. Cyclr lets you expose selected Acoustic actions as governed, reusable MCP (marketplace) tools inside your embedded marketplace while enforcing per-tenant credentials and orchestration policies.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductHow to develop an API – Best Practices to Follow from Cyclr Developers
Read more →ProductMCP PaaS
Read more →Related connectorG2
Related Marketing connector for customer-facing integration workflows.
Related connectorGoogle Ads
Related Marketing connector for customer-facing integration workflows.
Related connectorGoogle Analytics
Related Marketing connector for customer-facing integration workflows.