WebEngage

Estimated reading: 2 minutes Updated July 31, 2026

Overview

AFI pushes users and events into WebEngage, the customer-engagement platform for web and mobile apps, from any WordPress form. Use form submissions to identify users and trigger journeys.

Supported actions

Track User Attributes
Track Event

Authentication

Log in to WebEngage.
Open Settings > Account > API Credentials.
Copy the License Code and the API Key.
In AFI go to Settings > WebEngage and paste both values + your WebEngage data centre region.

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 WebEngage as the Receiver, then pick the Task you want to run.
Map sender fields onto WebEngage’s fields. User CUID (custom user ID) is required for identified users; events take a CUID + event name + properties.
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

Region-specific hosts: WebEngage has IN and US clusters with different endpoints.
CUID convention: pick a stable identifier (user ID or email hash) and use it consistently across all events.
System events like page_viewed are reserved — pick custom event names that don’t collide.