Your email includes a "View email in your browser" link at the top. When a recipient clicks it, Acoustic generates a browser-based version of the email they can view as a webpage. A common issue occurs where the browser view loads correctly, but CTA buttons or other links within it lead to dead pages, 404 errors, or blank pages — even though the same links work perfectly when the email is delivered to live recipients.

This is not a bug. It is expected behavior caused by how dynamic content (DC) links work, and it is almost always a data issue with your test contact.

Why this happens

Dynamic content links are URLs in your email that include personalization variables — placeholders replaced with recipient-specific data at send time. For example:

https://www.yoursite.com/account?id=%%Customer_ID%%&token=%%Auth_Token%%

When the email is delivered, %%Customer_ID%% and %%Auth_Token%% are replaced with real values from your contact database. Each recipient gets a unique, working link.

The browser version of the email uses the same contact data to resolve these variables. If the contact used to generate the browser view is missing those field values, the variables cannot be replaced and the resulting URL is broken:

https://www.yoursite.com/account?id=&token=  (broken — variables were empty)

Test contacts are often set up with only a name and email address. Without the specialized fields that production contacts have, personalization variables in link URLs are left empty, which is why links break during testing but work for real recipients.

How to fix it

Step 1: Identify which links are dynamic

Open your email in the Acoustic Campaign editor and review the URLs used in your CTA buttons and text links. Look for any URLs containing personalization variables in the format %%Field_Name%%. Make a note of every field name used across all links in the email.

Step 2: Check your test contact's data

1. In Acoustic Campaign, navigate to your contact database or contact list.
2. Find the test contact you use for previewing and sending test emails.
3. Open the contact record and confirm that every field referenced in your link URLs has a value populated.
4. If any fields are empty, add realistic test values to those fields.

Example: If your email uses %%Customer_ID%% in a link, open your test contact record and confirm the Customer_ID field has a value (e.g., 12345). Without this, the link cannot resolve.

Step 3: Create a dedicated test seed list with full data

Rather than using a minimal test contact, create a dedicated seed list where every contact has all fields fully populated. This ensures personalization variables resolve correctly during all future testing.

1. Create a new contact list in Acoustic Campaign specifically for testing.
2. Add yourself and your team members to this list.
3. For each contact in the seed list, populate every custom field your campaigns typically use — even if the values are dummy data.
4. Use this seed list for all future test sends.

Step 4: Test with a live recipient contact

If you need to verify that links work correctly for real recipients, the most reliable method is to send the email to a real contact in your production database who has all required fields populated — ideally a test account you control.

1. Identify a contact in your live database with all relevant personalization fields populated.
2. Send a test mailing to that contact's email address.
3. Open the email in the inbox, click View online, and test each CTA link.
4. Confirm all links resolve correctly for this contact.

Step 5: Escalate with a Mailing ID

If links broke for actual recipients (not just in testing), contact Acoustic Support and include the Mailing ID for the affected campaign. This allows the support team to pull the exact email configuration and investigate the link resolution process. Mailing IDs are visible in the Acoustic Campaign reporting interface when you open a specific mailing.

Key things to remember

• A link that works in a live delivery but not in a test preview is almost always a data issue with the test contact, not a platform bug.
• Dynamic personalization links require recipient data to be present in the contact database at both send time and preview time.
• The browser view is rendered using the same contact data as the delivered email — missing data means the link cannot resolve.
• Maintaining a well-populated seed list is the most effective way to prevent this issue during testing.