Skip to main content

Adobe Campaign Classic integration

This integration renders a Campaign as HTML with Adobe Campaign's JavaScript personalization and conditions already written in, ready to paste into a delivery. It does not connect to your Campaign instance. There are no credentials, and nothing is pushed to Adobe.

If you run Adobe Campaign v8, use the Adobe Campaign v8 integration instead. It writes delivery templates through the API.

Before you start​

You will need:

  • an admin user in Better Email who can create and edit integrations
  • a delivery in Adobe Campaign Classic whose HTML content you can edit
  • the names your delivery's target mapping uses for the recipient data you want to personalize with

1. Set up the integration in Better Email​

  1. Go to Integrations.
  2. Create a new integration.
  3. Enter a clear name for the integration.
  4. Choose Adobe Campaign Classic as the type.
  5. Optional: turn on Support subject line and Support preheader (see below).
  6. Enable the integration.
  7. Save the integration.

2. Subject line and preheader​

Better Email can't fill in the delivery's subject for you, but it can keep the subject line and preheader with the Campaign so they don't get lost on the way to Adobe.

  • Support subject line adds a subject line field to Campaigns.
  • Support preheader adds a preheader field to Campaigns.

Each toggle works on its own. With one on, the value appears in the sync dialog next to the HTML with its own copy button. Leave both off if you set the subject and preheader in Adobe Campaign.

3. Sync a Campaign​

On the Campaign's Review tab, click Sync to <integration name>, then Copy HTML.

Better Email copies the rendered HTML to your clipboard and marks the Campaign as synced. In Adobe Campaign Classic, open the delivery and paste the HTML into its HTML content. Copy the subject line and preheader from the sync dialog if you turned them on.

Syncing again copies the latest version. Paste it over the old HTML in the delivery.

4. Personalization with recipient fields​

Recipient fields export as Campaign's JavaScript personalization tags, which Adobe Campaign fills in per recipient when the delivery runs:

Hi <%= recipient.firstName %>,

This integration has no field sync, so add recipient fields by hand under the integration's Recipient fields tab. See Recipient Fields / Merge Tags for the general setup.

Set each field's ESP field name to the path Adobe Campaign reads it from in the delivery's target mapping:

ESP field nameExported as
firstName<%= recipient.firstName %>
recipient.firstName<%= recipient.firstName %>
recipient.location.city<%= recipient.location.city %>
registrations.status<%= registrations.status %>

A name without a dot reads from recipient, the alias of the built-in recipient table. If your deliveries use a custom target mapping, start the path with that mapping's alias, as in registrations.status.

5. Segmentation and block variants​

Segments and block variants export as JavaScript conditions around each variant's content:

<% if (recipient.country == 'DK') { %>
  ...content for Denmark...
<% } else { %>
  ...content for everybody else...
<% } %>

The Everybody else fallback becomes the final else branch, so the first matching variant wins, as it does in preview. Conditions read the same target mapping paths as recipient fields, so the ESP field name rule above applies here too.

A field with no value only matches is not and is not set. It never counts as greater than or less than a number, which is how Better Email's preview treats it as well. Use preview profiles to check the variants before you sync.

Troubleshooting​

  • Adobe Campaign reports an error in a personalization block. A recipient field's ESP field name probably doesn't exist in the delivery's target mapping. Check the spelling, the case, and the alias at the start of the path.
  • The subject line or preheader is missing from the sync dialog. Turn on Support subject line or Support preheader on the integration.