If verification code emails aren't reaching your inbox, contact Support with your Acoustic ID. We'll review the logs and check if your email address is on the bounce list.

This error appears when your browser settings block the resources needed to load templates in Acoustic Campaign.

How to fix it:

For Safari users: Disable "Prevent cross-site tracking" in your privacy settings.

For all browsers: Make sure third-party cookies are allowed. In Chrome, go to chrome://settings/cookies and select "Allow all cookies."

Refresh the page after making these changes. You'll then be able to access templates and build emails normally.

By default, standard users in Acoustic Campaign can create databases. If you want to restrict database creation while still allowing access to queries, there are some limitations to be aware of. This guide explains your options.

Review user roles and permissions

Go to Settings → User Management → Roles & Permissions.

Standard users can:

• Create databases, contact lists, queries, and relational tables
• Create and send emails, push, and mobile messages
• Build web forms, landing pages, and surveys
• Access reports

Apply folder limits to restrict database access

If you need to limit a user's ability to view or use databases:

1. Go to Settings → User Management → Select the username with Standard User Role → Folder Limits
2. Under Data Access, check "Limit shared Database access to this folder and its subfolders"
3. Assign a subfolder (this can be an empty one)
4. Save your changes

The user will only see databases in that specific folder, effectively hiding all others.

Additional folder limit options

• Limit Contact List Access — Restrict access to certain contact list folders
• Restrict Shared Folder Access — Prevent access to shared resources

What to keep in mind

Acoustic doesn't currently offer a way to block database creation while keeping query access. The best workaround is to hide database visibility using Folder Limits. For stricter controls, consider reviewing and adjusting roles at the organization level.

If you're an Org Admin, go to Settings → Administration → Security Settings → Access Restrictions.

You can add IP addresses and select from three options:

• Allow User Access — Only users logging in from this IP can access the Campaign UI
• Allow API Access — Only API calls coming from this IP will be accepted
• Allow FTP Access — Only FTP connections from this IP are allowed

If IPs are listed but none of these options are checked, no restrictions are enforced.

User-level restrictions override Org-level restrictions.

• Allow UI Access — That user can log in only from the listed IP(s)
• Allow API Access — That user's API calls must come from the listed IP(s)

If neither box is checked, no restrictions apply for that user.

The Approval button only appears if the user is correctly set up in approval groups. To fix this:

Check approval group membership

Go to Settings → Administration → Approval Groups. Select the relevant group and add the user's email if it's missing.

Verify user email in approval settings

Go to Settings → User Management → [User] → Email and Landing Page Settings. Make sure the correct approval group is selected.

Confirm visibility

Refresh the page, clear your cache and cookies, or try another browser.

If the Approval button still doesn't show after these steps, contact Acoustic Support for further assistance.

How do IP restrictions work in Transact?

Transact has stricter IP requirements than other Campaign features. Your IP address must be listed at the organization level for Transact API requests to be processed.

Important limitation

IP ranges (like 10.120.252.0–255) aren't supported. You need to list individual IP addresses.

IP restriction options

When you add an IP address, you can control what it's allowed to access:

• Allow UI Access — Permits UI login from the listed IP address
• Allow API Access — Restricts all API calls (including Transact API calls) to the listed IP address
• Allow FTP Access — Restricts FTP access to the listed IP address

How do user-level IP restrictions work in Transact?

User-level IP restrictions in Transact work similarly to marketing organizations, with a few key differences.

Allow UI Access works the same way as it does in Marketing organizations—it restricts logins by IP address.

Allow API Access only affects authenticated API calls, like RawRecipientDataExport.

Transact API calls are different

Transact API calls don't use authentication, but the IP address still must be listed in your organization-level security settings to be accepted.

Phishing occurs when malicious actors impersonate your trusted domain to deceive recipients into clicking harmful links or sharing sensitive information. These attacks typically aim for financial gain and can damage your domain's reputation if not addressed.

How do you detect phishing activity?

We monitor two key indicators:

• Spam trap reports
• Spikes in unauthenticated mail

These signals help us identify potential phishing attempts targeting your domain.

What prevention measures are available?

Two primary tools help protect your domain:

DMARC Policies
Set your policy to quarantine or reject to control how unauthenticated mail is handled.

DLL Whitelisting
Restrict email links to approved domains only, blocking malicious redirects before they reach recipients.

Together, these measures protect your recipients and maintain your domain's email reputation.

Category: System Administration > Network Configuration > Whitelisting | Source: Article 60

To make sure all features in Acoustic Campaign work as expected, you may need to whitelist these host names on your internal network:

• *.shutterstock.com — Needed for the image editing feature
• *.content-cms.com — Needed for forms and content

Do I still need to whitelist these domains if they're not in the latest documentation?

Yes. These domains are still required even if they're not mentioned in the most recent documentation.

What if my organization doesn't use these features?

If you don't use image editing, forms, or content features in Acoustic Campaign, you may not need to whitelist these domains.

Where can I find the complete list of host names to whitelist?

For the full list, refer to Acoustic Campaign's official guide: Whitelisting Acoustic Campaign by host name