Skip to main content
Denada integrates with Acoustic Campaign (formerly IBM Watson Campaign Automation / Silverpop) so you can design emails in Denada and push them directly to Acoustic as shared mailing templates, ready for campaign builders to use.

​
What you need

  • A Denada project with an email ready to push
  • An Acoustic Campaign account where you can create an API application (OAuth client ID and secret) and generate a refresh token
  • The ID of the Acoustic database or contact list your mailings send to (Denada can list them for you during setup)
  • A sender name and address for your mailings
Denada handles the OAuth flow for you: you enter the client ID, client secret, and refresh token once, and Denada exchanges the refresh token for short-lived access tokens in the background. Your Acoustic data center (pod) is detected automatically from your credentials — you never have to pick one.

​
Connect Denada to Acoustic

1

Open the Integrations dialog

Click Share on any project, then under Integrations, click Configure. (You can also open your team’s Settings page and click Add integration in the Integrations panel — manager access required.)
2

Select Acoustic

Choose Acoustic from the list of platforms.
3

Enter your OAuth credentials

  • Name — optional, e.g. “Production”.
  • Client ID and Client secret — from the API application you created in Acoustic.
  • Refresh token — the long-lived token generated for that application.
4

Validate

Click Validate. Denada confirms the credentials, detects your pod, and loads your account’s databases and lists — the Database / list ID field becomes a Database / list picker so you can select one instead of pasting an ID.
5

Fill in mailing defaults

Acoustic requires a database/list and sender details to save a mailing, so Denada collects them once here rather than on every export:
  • Database / list — the Acoustic database, contact list, or query the mailing is associated with.
  • From name and From address — the sender identity.
  • Reply-to — optional; defaults to the from address.
6

Save

Click Save. Saving new credentials clears any cached access token, so the next export authenticates fresh.

​
Push an email to Acoustic

  1. Open the project and click Share.
  2. Under Integrations, select Export to Acoustic.
  3. Fill in the export dialog:
    • Template name — the name of the mailing template as it will appear in Acoustic. Defaults to your project’s name.
    • Folder — optional. A folder path like Shared/Campaigns to file the mailing template into. The folder must already exist in Acoustic and the path is case-sensitive; leave it blank to save at the top level.
  4. Click Export.
Denada renders the final HTML and saves it in Acoustic as a shared mailing template (using Acoustic’s SaveMailing API), with your project’s subject line and the sender details from your integration settings.
Acoustic’s API has no way to upload images, so your email’s images stay hosted on Denada’s CDN — the exported HTML references them by URL and they display normally in sent mail.

​
How updates work

Acoustic keeps one mailing template per name across your account, so Denada is careful about collisions:
  • Re-exporting updates in place. If you’ve pushed this project to Acoustic before, the export dialog shows a Previous export option: choose Update the existing template to update the same mailing template by ID (changing the folder moves it), or Create a separate template — which requires a different name, since Acoustic replaces by name.
  • Name collisions are checked first. For new or renamed exports, Denada looks for an existing shared mailing template with the same name. If one exists, you’ll see a Replace existing template? confirmation that also tells you which folder the existing one currently lives in — confirm to replace (and move) it, or cancel and pick a different name.

​
Troubleshooting

Acoustic’s API can’t create or list folders, so the Folder path must exactly match a folder that already exists in Acoustic (it’s case-sensitive). Create the folder in Acoustic first, then export again.
Double-check all three credentials — client ID, client secret, and refresh token — come from the same Acoustic API application, and that the refresh token hasn’t been revoked.
For general information about how integrations work, see Integrations overview.

​
Need help?

If you run into issues with the Acoustic integration, reach out to support@heydenada.com or ask in our Community Slack.