AFI AFI

Dotdigital

Estimated reading: 2 minutes Updated August 1, 2026

Dotdigital is an enterprise customer-experience platform with email, SMS, and marketing automation. Advanced Form Integration sends form submissions to Dotdigital as new contacts in a chosen address book. the Pro version adds custom data-field support.

What you’ll need

  • An active Dotdigital account.
  • A Dotdigital API user (Settings → Access → API users → New user) with username (starts with apiuser-) and password.
  • Your Dotdigital regional API endpoint (e.g., r1, r2, r3, shown next to the API user).
  • The Advanced Form Integration plugin installed and activated.

Connect Dotdigital to AFI

  1. In WordPress, go to AFI → Settings → Dotdigital.
  2. Enter the API user username, password, and region.
  3. Click Save Changes.

Create the integration

  1. Go to AFI → Add New.
  2. Configure the trigger.
  3. In Action → Platform, select Dotdigital.
  4. In Task, choose Add Contact to Address Book.
  5. Pick the target Address Book.
  6. Map the form fields:
  • Email (required), First Name, Last Name.
  • Opt-In Type (Single, Double, VerifiedDouble).
  • Custom data fields by name.
  1. Optional: configure Conditional Logic.
  2. Click Save Integration.

Screenshot: AFI field-mapping screen with Dotdigital address book and contact fields visible

Pro features

The Pro Dotdigital integration adds full data field mapping (custom contact attributes) and the ability to enroll the contact into a Dotdigital program (automation campaign) right after creation.

Conditional logic example

Add to your “Trade-show leads” address book only when the form’s source hidden field equals “tradeshow-2026”. Other source values go to the general address book.

Troubleshooting

“Invalid credentials”

Dotdigital API users have a separate login from your account login. Make sure you’re using the API user username (the one starting with apiuser-), not your dashboard email.

Region mismatch

Dotdigital hosts accounts on regional endpoints. The region prefix (r1, r2, r3) must match your account’s region or all calls return 404.

Related docs