Business problem:
Some businesses may want to send custom conversion events (e.g., “Hot Leads”) to Meta using the Conversions API (CAPI) to optimize ad performance based on their internal lead qualification processes.
Currently, respond.io only supports two native conversion events: “Purchases” and “Leads.” This limitation prevents businesses from reporting more granular or high-intent events that are better aligned with their own sales funnel.
Desired Outcome:
Enable businesses to define and send custom conversion events (e.g., “Hot Leads,” “Qualified Lead,” etc.) natively via respond.io’s Meta Ads integration.