Skip to content

Commit f11cdfb

Browse files
Update insert-functions.md
1 parent 697cab7 commit f11cdfb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/functions/insert-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ You can also use this page to [enable destination insert functions](#enable-the-
5555
Segment invokes a separate part of the function (called a "handler") for each event type that you send to your destination insert function.
5656

5757
> info ""
58-
> If you’ve configured a [destination filter](/docs/connections/destinations/destination-filters/), and the event doesn’t pass the filter, then your function isn’t invoked for that event as destination filters are applied before insert functions.
58+
> If you’ve configured a [destination filter](/docs/connections/destinations/destination-filters/), and the event doesn’t pass the filter, then your function isn’t invoked for that event as destination filters are applied before insert functions. The same is true for the [integrations object]([url](https://segment.com/docs/guides/filtering-data/#filtering-with-the-integrations-object)). If an event is configured with the integrations object not to go to a particular destination then the Insert Function connected to that destination won't be invoked.
5959
6060
The default source code template includes handlers for all event types. You don't need to implement all of them - just use the ones you need, and skip the ones you don't. For event types that you want to send through the destination, return the event in the respective event handlers.
6161

0 commit comments

Comments
 (0)