-> Having "filtered at destination" events, with the integrations object, in destinations linked to Engage is expected. Engage will use its sources for multiple reasons, not only to send events to a particular destination. Engage uses the integrations object to route events to the destinations you have added to your audiences, traits and journey steps, so events that were filtered due to the integrations object are simply events that are not meant to be delivered by this destination, and hence, are filtered.
0 commit comments