-
Notifications
You must be signed in to change notification settings - Fork 378
Closed
Labels
KCScontentWhen the bug is about content that needs to get fixedWhen the bug is about content that needs to get fixedtriaged
Description
What article on segment.com/docs is affected?
What part(s) of the article would you like to see updated?
Per this Slack thread, the Debounce Middleware Action, though possible to add on the Mappings tab, is not available or applicable for destinations connected to Engage. This is because Engage hits the Tracking API directly, and thus no AJS2 to run the debounce middleware against.
This section should say something to include that this Action is not applicable to destinations within Engage.
Additional information
Liz Kane (CSE) lkane@twilio.com
I'm currently working with our customer (papier) who believed that the Debounce Middleware action was applicable to their Engage Braze destination. I've updated them with the above information and believe that adding this section into our docs will ensure that future customers aren't also confused by this.
Metadata
Metadata
Assignees
Labels
KCScontentWhen the bug is about content that needs to get fixedWhen the bug is about content that needs to get fixedtriaged