Customer.io

Estimated reading: 2 minutes

Overview

AFI pushes contacts and events into Customer.io for behaviour-driven email and SMS messaging campaigns. Sync form submissions, WooCommerce orders, and user signups as Customer.io people, and fire custom events for downstream automation.

Supported actions

  • Identify / Update Person — create or update a person record using the email address as the identifier.
  • Track Event — fire a named custom event (e.g. form_submitted, order_placed) with the submission’s attributes as the event payload.
  • Add to Segment — add the person to a manual segment for campaign targeting.

Authentication

  1. Log in to Customer.io.
  2. Open Settings > Workspace Settings > API Credentials.
  3. Create a Track API key (and note your Site ID).
  4. In AFI go to Settings > Customer.io and paste the Site ID and API key.

How to create the integration

  1. In WordPress admin, go to AFI > New Integration.
  2. Pick your Sender (Contact Form 7, WPForms, WooCommerce, etc.) and the form / event to listen on.
  3. Pick Customer.io as the Receiver, then pick the Task you want to run.
  4. Map sender fields onto Customer.io’s fields. Customer.io’s email is required; custom attributes can be any name/value.
  5. Optional: add Conditional Logic so the action only fires on matching submissions.
  6. Save and run a test submission. Check AFI > Log if anything looks off.

Notes & caveats

  • Region matters. Customer.io has US and EU regions on different API hosts. Pick the right one when you save credentials.
  • Anonymous events aren’t supported — every event needs an identified person.
  • Reserved attribute names (id, email, created_at) have special meaning. Avoid mapping form fields onto them unless you mean to override.

Related

Receiver Platforms - Previous Zoho Sheet Next - Receiver Platforms FollowUpBoss