To reduce unnecessary traffic to third-party platforms, Invoca now checks that a call contains the specific identifiers a given integration needs before sending data to it.Applies to: Webhooks, Deliveries, third-party API integrations
How conditional firing works
Previously, Invoca attempted to send data for every call to each configured third-party integration, regardless of whether the necessary identifying information was present. Now, Invoca inspects each call record first and only sends it to an integration if at least one of that integration’s required identifiers is present. This makes the data in your third-party platforms more actionable, and reduces the volume of requests that would otherwise be rejected or left unprocessed by the receiving system.Impact on your delivery data
Because delivery is more targeted, you may see a reduction in the volume of data shown in the “Delivery” charts for the affected integrations in Invoca. This reflects a more precise, efficient transfer — quality over raw quantity — and the data delivered will be more complete and relevant to your integrated platforms.Affected integrations and required identifiers
If you have questions about these changes, contact your Invoca account team or support@invoca.com.