Iterable
Overview
AFI sends users and events to Iterable, the cross-channel growth marketing platform. Use form submissions and order events to trigger Iterable Journeys and personalised campaigns.
Supported actions
- Update User — upsert a user by email or userId, populating any data fields.
- Track Custom Event — fire a named event with payload for journey targeting.
- Subscribe to List — add the user to one of your subscribed lists.
Authentication
- Log in to Iterable.
- Go to Integrations > API Keys.
- Create a Server-side API key (Standard or Java key).
- In AFI go to Settings > Iterable and paste the key.
How to create the integration
- In WordPress admin, go to AFI > New Integration.
- Pick your Sender (Contact Form 7, WPForms, WooCommerce, etc.) and the form / event to listen on.
- Pick Iterable as the Receiver, then pick the Task you want to run.
- Map sender fields onto Iterable’s fields. Email (or userId) is required. Iterable accepts arbitrary data fields with no schema upfront.
- Optional: add Conditional Logic so the action only fires on matching submissions.
- Save and run a test submission. Check AFI > Log if anything looks off.
Notes & caveats
- Server-side key required. Use a server-side API key with permission for the relevant endpoints; JS-SDK keys won’t work.
- Region. Iterable has US and EU regions; the API host differs. Confirm yours before saving credentials.
- Event names become trigger names in Journeys — pick stable, lowercased names like
form_submitted.