.png)
Acoustic Campaign Integration Guide
Integrate Acoustic Campaign with enterprise systems through REST APIs, legacy XML APIs, batch imports and exports, and selected event or callback mechanisms.
Acoustic Campaign integration options at a glance
Acoustic Campaign supports REST APIs for current campaign and audience operations, while older XML-based APIs may remain necessary for selected contact, database, import, export, or administration functions. Bulk and asynchronous processing is available through contact imports, exports, and other long-running operations. File-based exchange can support scheduled or high-volume audience movement, including tenant-dependent managed file transfer or SFTP patterns. Selected campaign capabilities may provide event notifications or outbound callbacks, but broad webhook coverage is not confirmed. Martini can securely authenticate, orchestrate API and file workflows, poll asynchronous jobs, map contact and campaign data, and schedule reconciliation when events are unavailable.
| Integration point | Supported by Acoustic Campaign? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Read and update Contacts, Contact databases, Contact lists, Mailings, and selected campaign or delivery data where the tenant API exposes the required resource. | Martini can consume the documented HTTPS APIs, manage authentication, paginate responses, transform payloads, and orchestrate retries and downstream writes. |
| XML or legacy APIs | Legacy | Support selected contact, database, import, export, and campaign administration operations that may not be available in the current REST API. | Martini can call documented XML endpoints and transform XML payloads, while isolating legacy logic in reusable workflows. |
| Bulk and asynchronous processing | Yes | Process large contact populations through imports, exports, and long-running audience or campaign operations. | Martini can submit a job, persist its operation identifier, poll status, process rejected rows, and reconcile the source batch. |
| File import and export | Limited | Exchange scheduled contact and audience files when batch processing is preferable or an API resource is unavailable; tenant-dependent managed transfer or SFTP may apply. | Martini can prepare, validate, route, and process files, then invoke or monitor the corresponding Acoustic Campaign operation where supported. |
| Webhooks and outbound callbacks | Limited | Selected campaign capabilities may provide event notifications or outbound callbacks, but general-purpose coverage for all Contacts, Mailings, Programs, and reporting events is not confirmed. | Martini can receive supported callbacks and combine them with API enrichment, validation, deduplication, and scheduled reconciliation. |
| Reporting and analytics APIs | Limited | Retrieve available campaign results, delivery metrics, status information, and reporting data exposed by the tenant’s enabled product APIs. | Martini can normalize reporting windows, apply watermarks, and write results to CRMs, databases, or reporting platforms. |
| Authentication | Yes | Modern REST APIs use OAuth-based authentication; older interfaces may use API keys, API users, organization identifiers, or other tenant-specific credentials. | Martini can keep credentials and tokens in environment-specific secrets and use authenticated API workflows without embedding secrets in logic. |
| Database access | Not applicable | Direct customer-accessible relational database access is not the normal Acoustic Campaign integration method. | Martini should use documented APIs, reporting resources, legacy APIs, or file exchange rather than assuming direct database connectivity. |
How Acoustic Campaign exposes data and business events
Acoustic Campaign REST APIs
Acoustic Campaign provides REST APIs for supported audience and campaign operations. Resources and permissions vary by API version, tenant, and account configuration.
Martini implementation pattern
Martini implementation pattern: Martini authenticates to the tenant, calls the required REST resource, follows pagination, maps the response to a canonical model, and writes or routes the result through a workflow.
Implementation sequence
Acoustic Campaign XML APIs
Older XML-based APIs remain relevant for selected contacts, databases, imports, exports, and campaign administration operations where an equivalent REST resource is unavailable.
Martini implementation pattern
Martini implementation pattern: Martini sends authenticated XML requests, validates XML responses, transforms legacy terminology into canonical objects, and isolates compatibility logic from current REST workflows.
Implementation sequence
Acoustic Campaign batch processing
Contact imports, exports, and other long-running operations support high-volume processing without issuing one request per Contact. Completion and rejected rows may be available asynchronously.
Martini implementation pattern
Martini implementation pattern: Martini prepares a validated batch, starts the operation, persists the job identifier, polls at a controlled interval, and reconciles accepted and rejected rows.
Implementation sequence
Acoustic Campaign file exchange
File-oriented contact and audience exchange can support scheduled loads, large populations, or operations not exposed by the tenant’s current API. Transfer details depend on account configuration.
Martini implementation pattern
Martini implementation pattern: Martini generates or receives the file, validates its structure and business fields, transfers it through the supported mechanism, and tracks processing and rejection outcomes.
Implementation sequence
Selected events and callbacks
Acoustic Campaign has event-triggered marketing capabilities, but broad outbound webhook coverage for every Contact, Mailing, Program, or reporting event is not confirmed.
Martini implementation pattern
Martini implementation pattern: Where a tenant-supported callback exists, Martini receives and validates it, enriches the notification through the API, and uses scheduled polling as a reconciliation fallback.
Implementation sequence
Common Acoustic Campaign integration patterns
Pattern 1: Synchronize CRM contacts to Acoustic Campaign
When to use this pattern
Use this pattern when Salesforce or Microsoft Dynamics 365 is the system of record for contact identity, consent, and customer attributes, while Acoustic Campaign manages audience activation and email campaigns.
Integration direction
Example Mapping
| Acoustic Campaign Field | Canonical Field | Target Field |
|---|---|---|
| emailAddress | ||
| contactId | sourceContactId | External contact identifier |
| optInStatus | marketingConsent | Subscription or opt-in status |
| lastModifiedDate | sourceUpdatedAt | Contact update timestamp |
Martini implementation pattern
A Martini workflow retrieves changed CRM Contacts or Leads, validates email and consent, applies suppression and eligibility rules, then upserts Contacts or submits a batch import to the selected Contact database and Contact lists. It records source identifiers, throttles API calls, retries transient failures, and routes rejected rows for correction.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- batch orchestration
- error handling
Pattern 2: Activate a warehouse audience
When to use this pattern
Use this pattern when a data warehouse or customer data platform calculates a qualified audience and Acoustic Campaign is the activation destination.
Integration direction
Example Mapping
| Acoustic Campaign Field | Canonical Field | Target Field |
|---|---|---|
| customer_id | customerId | External contact identifier |
| audience_code | segmentId | Contact list membership |
| consent_status | marketingConsent | Subscription status |
Martini implementation pattern
A scheduled Martini workflow queries the qualified population, transforms it to tenant-defined Contact database fields, validates required values, and submits a bulk import. Martini polls the asynchronous operation, captures accepted and rejected rows, prevents duplicate batch submissions, and preserves Acoustic-managed attributes rather than replacing them indiscriminately.
Martini capabilities used
- scheduled workflows
- database connectivity
- data mapping
- file processing
- asynchronous orchestration
- reconciliation
Pattern 3: Synchronize campaign performance to analytics
When to use this pattern
Use this pattern when campaign and delivery results must be consolidated in Snowflake, Salesforce, or another reporting platform for operational and executive analysis.
Integration direction
Example Mapping
| Acoustic Campaign Field | Canonical Field | Target Field |
|---|---|---|
| mailingId | campaignMessageId | mailing_id |
| deliveryDate | eventDateTime | delivery_timestamp |
| deliveredCount | delivered | delivered_count |
| clickCount | clicks | click_count |
Martini implementation pattern
Martini periodically retrieves available Mailing, Program, and delivery data through the supported API or export mechanism, normalizes account time zones and reporting windows, and writes idempotent records downstream. A watermark and repeatable reporting window allow late metrics to be reconciled without duplicating results.
Martini capabilities used
- scheduled workflows
- API consumption
- data transformation
- watermark management
- database writes
- retry handling
Pattern 4: Route campaign events to a business workflow
When to use this pattern
Use this pattern when a supported Acoustic Campaign event or callback should initiate an internal process, while recognizing that scheduled polling may be required for events not covered by the tenant.
Integration direction
Example Mapping
| Acoustic Campaign Field | Canonical Field | Target Field |
|---|---|---|
| contactId | customerReference | Customer reference |
| mailingId | campaignMessageId | Campaign reference |
| eventType | marketingEventType | Request classification |
| eventTimestamp | occurredAt | Activity timestamp |
Martini implementation pattern
Martini receives a supported callback or discovers a status change through scheduled polling, validates and deduplicates the event, enriches it with current Acoustic Campaign data, and routes it to ServiceNow or another internal API. Business rules determine whether to create, update, or ignore a downstream action; failures are retried and unresolved events are placed in a reconciliation queue or report.
Martini capabilities used
- webhook consumption
- workflow orchestration
- API enrichment
- business rules
- idempotency
- error handling
Applications commonly integrated with Acoustic Campaign
Acoustic Campaign can be integrated with CRM, commerce, finance, service, and data platforms to activate audiences, synchronize consent and customer attributes, and consolidate campaign performance. The exact scope should be confirmed against the tenant’s enabled APIs, permissions, and data model.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize CRM contacts, consent attributes, campaign audiences, and engagement results. | Salesforce → Martini → Acoustic Campaign | Martini retrieves changed Salesforce Contacts or Leads, validates consent and identifiers, maps them to Acoustic Campaign Contacts and Contact databases, and uses REST or batch imports with retry and reconciliation handling. |
| Microsoft Dynamics 365 | Use CRM contact and customer attributes to create or update marketing audiences. | Microsoft Dynamics 365 → Martini → Acoustic Campaign | A scheduled or event-driven workflow retrieves changed Dynamics records, applies audience eligibility rules, transforms fields, and submits idempotent Acoustic Campaign updates or imports. |
| NetSuite | Use customer and transaction attributes for segmentation and marketing eligibility. | NetSuite → Martini → Acoustic Campaign | Martini retrieves eligible NetSuite customers or transaction-derived segments, normalizes identifiers and consent fields, and publishes them to an Acoustic Campaign Contact database through a controlled batch workflow. |
| Shopify | Build audiences from customer, order, and product activity for email campaigns. | Shopify → Martini → Acoustic Campaign | Martini consumes available Shopify data, filters customers according to consent and business rules, maps customer attributes, and sends incremental updates or prepared audience files to Acoustic Campaign. |
| ServiceNow | Coordinate requester or customer data with campaign audiences and selected campaign outcomes. | ServiceNow → Martini → Acoustic Campaign | Martini exposes or consumes APIs for ServiceNow data, validates eligibility, synchronizes approved Contacts or lists with Acoustic Campaign, and can route selected campaign outcomes back to ServiceNow. |
| Snowflake | Prepare unified audiences and store campaign performance data for analytics. | Snowflake → Martini → Acoustic Campaign | A scheduled Martini workflow reads a qualified Snowflake result, transforms it into the tenant’s Contact database schema, starts an Acoustic Campaign batch import, polls completion, and writes normalized campaign results back to Snowflake. |
| Oracle Responsys | Support marketing-platform coexistence, migration, or controlled exchange of audience and campaign data. | Oracle Responsys → Martini → Acoustic Campaign | Martini mediates API or file-based exchange, applies canonical audience mappings and consent rules, and records batch identifiers and rejected rows for reconciliation. |
How to build a Acoustic Campaign integration in Martini
Objective
Identify the tenant API generation, base URL, organization identifier, permissions, and supported authentication flow before implementing business logic.
Instructions in Martini
- Confirm whether REST, legacy XML, file exchange, or a combination is required
- Store OAuth credentials, API keys, organization identifiers, and tokens in Martini secrets
- Use HTTPS and environment-specific configuration
- Validate access with a low-risk authenticated request
Objective
Select an event, callback, schedule, or upstream API request that matches the required synchronization latency and Acoustic Campaign event coverage.
Instructions in Martini
- Use a supported callback only for verified tenant events
- Use a scheduler for reconciliation and reporting workflows
- Use an API-triggered Martini workflow when an upstream system initiates activation
- Define the polling interval and stopping conditions for asynchronous jobs
Objective
Acquire current Contacts, Contact databases, Mailings, Programs, Queries, or reporting data using the appropriate current or legacy mechanism.
Instructions in Martini
- Follow pagination and continuation information
- Prefer bulk operations for large populations
- Retrieve current resource details after a notification when the payload is incomplete
- Persist source and operation identifiers
Objective
Coordinate validation, enrichment, transformation, business rules, target writes, and asynchronous status checks in a maintainable Martini workflow.
Instructions in Martini
- Separate ingestion, transformation, delivery, and reconciliation stages
- Apply consent, suppression, eligibility, and ownership rules
- Use bounded concurrency and throttling
- Branch accepted, rejected, and retryable outcomes
Objective
Convert source fields into Acoustic Campaign’s tenant-defined Contact, list, mailing, or reporting structures without losing identifiers or consent meaning.
Instructions in Martini
- Map stable identifiers and email fields explicitly
- Normalize dates and account time zones
- Transform JSON, XML, or delimited files as required
- Validate required fields and data types before submission
Objective
Send individual updates, batch imports, file-based loads, or normalized campaign results to the appropriate destination.
Instructions in Martini
- Use idempotent matching for Contacts
- Record Acoustic Campaign job identifiers
- Poll asynchronous imports until completion or timeout
- Persist accepted and rejected row results
Common Acoustic Campaign data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Contacts | Recipients, subscribers, and marketing contacts with identity, consent, and subscription attributes. | Salesforce, Microsoft Dynamics 365, Shopify, NetSuite, Snowflake | Martini validates identifiers and consent, maps fields, and performs individual or batch updates with idempotent matching. |
| Contact databases | Stores contact attributes, subscription information, and related audience data. | Salesforce, Snowflake, reporting platforms | Martini maps source data to tenant-defined fields, preserves managed attributes, and reconciles import results. |
| Contact lists | Organizes or targets Contacts for campaign audiences. | Salesforce, Shopify, Microsoft Dynamics 365 | Martini applies segmentation rules and updates list membership through available REST, legacy, or batch mechanisms. |
| Mailings | Email campaign messages, scheduling, delivery, and performance information. | Salesforce, Snowflake, reporting platforms | Martini retrieves available status and performance data, normalizes timestamps, and uses stable mailing identifiers for repeatable writes. |
| Programs | Automated marketing workflows coordinating campaign activities and audience actions. | Salesforce, ServiceNow, reporting platforms | Martini can initiate or inspect supported program operations and route selected status information through business rules. |
| Queries | Saved audience-selection definitions used to segment or identify Contacts. | Snowflake, Salesforce, reporting platforms | Martini can use available query operations or exported results as input to audience activation and reconciliation workflows. |
Authentication and security considerations
Authentication and security
Modern Acoustic Campaign REST APIs use OAuth-based authentication, while older interfaces may use API keys, API users, organization identifiers, or other tenant-specific credentials. Confirm the API generation, scopes, permissions, regional endpoint, and account configuration before implementation.
- Store OAuth client credentials, API keys, usernames, organization identifiers, and tokens in Martini secrets.
- Use HTTPS and environment-specific configuration.
- Rotate credentials without embedding them in workflow logic.
- Limit access to the Acoustic Campaign resources required by the integration.
Operational considerations for Acoustic Campaign integrations
Design for reliable operations
- Confirm the current API base URL, version, hostname, resources, permissions, and account time zone.
- Follow pagination and use throttling, bounded concurrency, and retry backoff for rate limits and transient failures.
- Prefer batch imports for large populations and persist asynchronous job identifiers.
- Use stable Contact identifiers and deterministic matching to prevent duplicates.
- Validate consent, suppression, required fields, and tenant-defined attributes before submission.
- Handle partial imports, rejected rows, schema changes, token expiration, and late-arriving reporting metrics.
- Use event notifications only where the tenant confirms coverage, and schedule reconciliation for missed or unsupported events.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable integration delivery
Scripts and point-to-point integrations often duplicate authentication, pagination, transformation, retry, and reconciliation logic. Martini provides a workflow and API layer for coordinating Acoustic Campaign with CRM, database, file, and internal systems while keeping business rules and mappings visible and reusable.
- Combine real-time requests, scheduled synchronization, callbacks, and batch processing in governed workflows.
- Separate vendor-specific REST or XML handling from canonical data mappings and target-system logic.
- Centralize secrets, validation, error handling, monitoring, and deployment configuration.
- Expose controlled APIs for upstream applications instead of coupling them directly to Acoustic Campaign details.
- Use reusable integration assets for audience activation, campaign reporting, and reconciliation.
Frequently asked questions
Acoustic Campaign can be integrated through its REST APIs, selected legacy XML APIs, bulk and asynchronous import or export operations, file exchange, and tenant-dependent event or callback features. Scheduled workflows are useful for reconciliation and campaign reporting when event coverage is limited.
Yes. Martini can integrate with Acoustic Campaign by consuming its REST APIs, calling legacy XML endpoints where necessary, processing supported file imports and exports, receiving selected callbacks, and orchestrating scheduled synchronization workflows.
No. A dedicated Acoustic Campaign connector is not required. Martini can use Acoustic Campaign’s confirmed native APIs, authentication methods, file exchange capabilities, and selected event mechanisms through workflows and APIs.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Acoustic Campaign. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Acoustic, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.
REST APIs are the preferred starting point where the required Contacts, Contact databases, lists, Mailings, Programs, or reporting resources are available. Use bulk or asynchronous operations for large populations, file exchange when appropriate, and legacy XML APIs only when the required operation is not available through REST.
Selected campaign capabilities may provide event notifications or outbound callbacks, but broad webhook coverage for every Contact, Mailing, Program, or reporting event is not confirmed. Martini can receive supported callbacks and supplement them with scheduled polling and reconciliation.
Martini can prepare a validated audience, submit an Acoustic Campaign import or other batch operation, persist the operation identifier, poll for completion, and reconcile accepted and rejected rows. Bulk processing is generally preferable to issuing one request per Contact.
Martini maps tenant-specific fields to canonical models, validates consent and required values, applies business rules, and supports retry and error-handling workflows. Implementations should use stable identifiers, bounded backoff, idempotent writes, duplicate prevention, and explicit handling of partial import failures.
Related Martini documentation
APIs
Data
Plan your Acoustic Campaign integration
Use Martini to design a secure, observable integration between Acoustic Campaign and your enterprise systems using the APIs, batch operations, files, and event mechanisms supported by your tenant.