Skip to content

Commit 16d1d21

Browse files
Merge pull request #7132 from segmentio/joeynmq-patch-7
Clarify Debounce Middleware behavior in public docs
2 parents ec9ab73 + 8f231be commit 16d1d21

File tree

1 file changed

+12
-0
lines changed
  • src/connections/destinations/catalog/actions-braze-web

1 file changed

+12
-0
lines changed

src/connections/destinations/catalog/actions-braze-web/index.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,3 +172,15 @@ When "Enable SDK Authentication" is enabled, Segment will set Braze's `enableSdk
172172
173173
Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
174174
{% include components/actions-map-table.html name="braze-web" %}
175+
176+
177+
## FAQ
178+
179+
### How does the Debounce Middleware Action work?
180+
181+
The following [Debounce Middleware](/docs/connections/destinations/catalog/actions-braze-web/#debounce-middleware) logic is executed at the source-level:
182+
183+
When an Identify call is fired on a website, Segment first caches and compares the user traits object.
184+
185+
- If the user traits differ from what was previously cached, the data flows through destination filters, insert functions, and then through destination mappings.
186+
- If user traits are the same as what's cached, Segment assumes that that data was already sent to Braze and a does not make a new request to Braze.

0 commit comments

Comments
 (0)