Filtering a Pre-Transfer Webhook by Marketing Data or Signals isn’t natively supported — use a Lookup Table to populate a dynamic filter value instead.Applies to: Pre-transfer webhooks, real-time routing
Symptoms
You want to send only calls that meet specific criteria to a third-party system through a Pre-Transfer Webhook, based on Invoca Data, Marketing Data, or Signals.Cause
Filtering a Pre-Transfer Webhook directly by Marketing Data, Signals, or other Invoca Data isn’t natively supported.Resolution
Use a Lookup Table to generate a dynamic value the webhook can reference, instead of relying on native filtering:- Add a new Marketing Data field (Short Text) to your Marketing Data Dictionary to hold the dynamic value you want to send.
- Create a Lookup Table using the Marketing Data field or Signal you want to filter on as the primary key, and your new field as the secondary key. Include the expected values for each row, and upload the table.
- Validate that the Lookup Table returns the expected value for each test case.
- Build or edit your Pre-Transfer Webhook, following the standard installation guide for the destination system.
-
In the webhook payload, replace the static destination field with a substitution token for the Marketing Data field you created in step 1, so the value populates dynamically. For example, in an XML payload:
- Validate that the webhook includes the dynamic value when the Lookup Table has a match, and omits or excludes the field when it doesn’t.
- Confirm the data flowing into the destination system matches expectations.