To request an increase in your Relational Table limits, open a support case and include the following details:

Data validation

• Have you run a Data Validation check on all databases connected to your Relational Tables within the past week?
• If validation issues were found, have you corrected them?

Current usage

• Do you currently use Child Relational Tables?
• If yes, how frequently do you use them and for what purpose?

Your request

• How many additional Relational Tables do you need?
• Will these be standard Relational Tables or Child Relational Tables?
• How do you plan to use the new tables? (For example: running queries, building programs, or inserting table data into emails)

Volume and growth

• Will the number of rows in your tables stay fixed or grow over time?
• About how many rows do you expect each new table to handle?

Database mapping

• How many databases will the new tables connect to?
• What are the sizes of those databases?

Query behavior

• Do you create queries that reference multiple Relational Tables, including subqueries?
• If yes, what's the maximum number of tables you typically reference in a single query?

Including these details helps us process your request quickly and ensure your account is configured to support your needs.

Every database in Acoustic includes a system field called "Opt Out Details." This field automatically captures the most recent reason a contact opted out, regardless of their current subscription status.

How the field gets populated

The system populates this field with one of the following values:

Abuse null
The contact filed an abuse complaint with their ISP (such as Gmail, Yahoo, or Hotmail) using the "this is spam" button.

Opt out via one click opt out
The contact clicked a one-click opt-out link or button (built with the "Opt-out One Click" hyperlink type).

Opt out via list unsubscribe direct
The contact clicked the unsubscribe link or button in the email preheader. This is a default feature, but ISPs like Gmail decide whether to display it in the email client.

Opt out via list unsubscribe form submit
The contact clicked an unsubscribe button shown by Gmail or another ISP, which requires them to confirm their opt-out.

Opt out via email opt out
The contact replied to an email with keywords like "opt out," "remove me," or "unsubscribe." This also applies when a contact uses the compose window that appears after clicking an unsubscribe button or link (with the "Opt-out email" link type).

Opt out by webform
The contact submitted an opt-out webform by clicking an "Opt-out to page" link in an email, or by visiting the webform URL directly without coming from an email.

Manually opt out by (campaign username)
A user in your Acoustic Campaign account manually opted out the contact through the interface.

Opt out via API
The contact was opted out through an OptOutRecipient API call.

Opt out via list import
The contact was opted out during a list import with the opt-out option selected, either through the interface or API.

You can export opt-out contacts manually through the interface or automatically using the XML API.

Export through the interface

1. Log in to Acoustic Campaign and go to the Data tab.
2. Select your database.
3. Click Exports and choose one of the following options:
   • Export Opt-Outs Only (for opted-out contacts)
   • Export Contacts Only
   • Export Undeliverables Only
   • Export Contacts, Opt-Outs, Snoozes, and Undeliverables
   • Export Snoozes Only
4. Optionally, set a date range and select the fields you want to include.
5. Choose your file format and submit the export job.
6. Download the file from Content > Stored Files > Private.

Export using the XML API

Use the ExportList API to export opt-out data programmatically. This option works well for scheduled or automated exports.

Which method should I use?

Use the interface for one-time exports. Use the API for automation. Proper opt-out configuration ensures accurate results and helps maintain compliance.

The "Disable deduplication" option is only available for flexible databases. Restricted databases don't include this feature.

How to use this option

Make sure your database is set up as a flexible database. For step-by-step instructions on enabling or managing duplicate contacts, see the Help Center article: Find duplicate contacts

When importing a CSV file into a Relational Table, the timestamp field may fail to import if your data includes a timezone abbreviation (such as EST). Acoustic's Relational Tables expect the Timestamp field to follow this format:

mm/dd/yyyy hh:mm:ss

For example: 03/15/2025 14:30:00

Including EST or any other timezone suffix can cause the import to fail.

How to fix this

1. Open your CSV file in Excel or a text editor.
2. Remove the timezone abbreviation (EST, PST, etc.) from the timestamp column. Make sure all timestamps follow the mm/dd/yyyy hh:mm:ss format.
3. Save the CSV file.
4. Re-import the file into your Relational Table.

This ensures your Timestamp column is compatible with Acoustic's Relational Table requirements.

Category: System Administration > Data Retention > Email Campaigns | Source: Article 62

Acoustic Campaign retains sent email campaigns for 450 days by default (about 15 months). After that, campaigns may be archived or deleted.

Example

A campaign sent on January 1, 2025 will be retained until March 2026.

Category: System Administration > Data Retention > Email Content | Source: Article 63

Email content is kept for 450 days after the last send. This includes the message itself, open rates, and click data.

Databases (contact lists) are kept for 450 days of inactivity. If a database isn't used during that time, it's automatically purged.

Example

If a subscriber list is unused for 450 days, it will be deleted.

This setting lets you automatically purge contacts after a set time, defined as "Number of Days to Keep Contacts." It only appears if Database Contact Expiration is enabled in Archive settings.

Example

If set to 30 days, inactive contacts are removed after 30 days.

This feature automates cleanup of static contact lists. It's enabled at the org level but must be configured per database. You can set the number of days to keep static lists.

The "Last Modified" field is updated whenever a contact record is changed. This includes:

User actions

• Importing new data (through the interface or List Import API)
• Manually editing or saving a record (even without making changes)
• Using Set List Value to update fields

Recipient actions (if they modify the record)

• Submitting a web form (submission alone counts as an update)
• Website actions that trigger AddRecipient or UpdateRecipient API calls

System processes

• Programs with Update Profile Data steps
• Set List Value operations
• Scoring models updating related fields

The "Last Modified" field is not updated by:

• Automated behavior updates (such as last open, click, or sent)
• Link clicks and web visits (unless tied to an API update)

Yes, but it's not always reliable. For example, if daily imports refresh all records, everyone appears "recently modified," making segmentation inaccurate.

This occurs when a contact has a special status that hides it from search, such as being marked as Forward-to-Friend. Even though the contact exists, it won't appear in interface searches. Trying to add it manually may produce a "duplicate contact exists" error. The contact is not in the suppression or opt-out lists.

How to resolve this

Contact support with your database ID and the email address. Make sure you have explicit opt-in consent from the user—written confirmation may be required. The support team can convert the hidden record to a regular contact, making it visible and manageable in the interface.