Two fallbacks on the Opt-in tab cover any provider that does not have a native connector.
The webhook:
Put a URL in the Webhook URL field and every lead captured by that campaign is posted to it as JSON. The body contains the email, first name, last name and phone, the campaign name, a source value of Results AI Engage, and the full source set: campaign type, page URL, referrer, device and every UTM value present on the visit.
The webhook runs in addition to the autoresponder, not instead of it. You can deliver the same lead to a list and to a Zapier, Make or n8n hook at the same time. Each target is attempted independently, so a dead webhook cannot stop the autoresponder and a rejected autoresponder cannot stop the webhook.
The raw form embed:
Paste the form code your provider gives you into the Or paste your own form code box. When that box has content it replaces the built in form and the campaign renders the provider's own markup inside your bar or popup.
Which fallback should you use:
Prefer the webhook. It keeps the Engage form, so you keep the plugin's spam protection, the styling, the success message and the redirect, and the lead is still stored on your site. Use the raw embed only when a provider needs its own form to work, for example because of a required tracking script.
Raw form code has to keep its script and iframe tags to work at all, so it is stored as given, and only a WordPress user who is already allowed to publish unfiltered HTML can set it. For everyone else the paste is filtered.
Every delivery attempt writes its outcome back onto the lead row, so the Diagnostics log and a support report can both answer where a given lead actually went and what each target said about it.