Blueshift

Estimated reading: 2 minutes Updated July 31, 2026

Overview

AFI identifies customers and tracks events in Blueshift, the customer data platform (CDP) for cross-channel marketing, from WordPress form submissions and order events. Feed the CDP with first-party data automatically.

Supported actions

Identify Customer
Track Event
Update Custom Attributes

Authentication

Log in to Blueshift.
Open Account Settings > API Keys.
Copy the Site ID and Event API Key.
In AFI go to Settings > Blueshift and paste both.

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 Blueshift as the Receiver, then pick the Task you want to run.
Map sender fields onto Blueshift’s fields. Customer ID (or email) is required. Event names and custom attributes can be any string.
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

Identity model: Blueshift supports both anonymous and identified — for AFI flows, you typically have an email so identify directly.
Reserved events (purchase, view, add_to_cart, etc.) feed Blueshift’s predictive models — use them when they fit instead of inventing custom names.
Rate limits: generous but bursty events should use AFI’s background queue.