🔄 Using Engage With WP Sync

Engage and WP Sync are separate plugins that work together with nothing to configure beyond having both active.

How the hand off works:

When a lead is captured, Engage stores it, delivers it to the campaign's own autoresponder and webhook, and also hands it to WP Sync. Inside WP Sync every Engage campaign appears as a source, so you build a bridge there in the usual way and choose where the lead should go next.

That means one opt-in can reach several destinations at once: your autoresponder, a Google Sheet, an outbound webhook, a CRM, or anything else WP Sync connects to. Engage captures the lead, WP Sync automates what happens afterwards.

This is an extra path, never a replacement. Engage still delivers to its own connections either way.

What travels with the lead:

The email, first and last name, and the full source set: campaign name, campaign type, page URL, referrer, device, phone if collected, and every UTM value present. A stable per lead key travels too, so WP Sync can deduplicate across bridges.

Turning it off:

Settings has a Send opt-ins to WP Sync toggle. Switch it off if you would rather keep the two plugins entirely separate.

Requirements:

The hand off only runs when WP Sync's own engine is loaded, which means WP Sync core has to be installed and licensed. If WP Sync is installed but not licensed, the Diagnostics health check will still detect it, but nothing is dispatched.

There is a matching integration with WP Conversion Tracker. When it is installed, campaign clicks are handed to it so Engage traffic shows up alongside the rest of your tracked links. That has its own toggle in Settings too.

Ready to stop reading and start using?

Every plugin documented here works alongside the others, managed from one ResultsAIx Hub.