Skip to content

Commit 87eea7c

Browse files
Apply suggestions from code review
1 parent 5e07f37 commit 87eea7c

File tree

1 file changed

+6
-4
lines changed
  • src/connections/destinations/catalog/actions-braze-web

1 file changed

+6
-4
lines changed

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

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -176,10 +176,12 @@ Keep the following in mind if you plan to move to Braze (Actions) from the class
176176
177177
## FAQ
178178
179-
### How Debounce Middleware works?
179+
### How does the Debounce Middleware Action work?
180180
181-
The [Debounce Middleware](/docs/connections/destinations/catalog/actions-braze-web/#debounce-middleware) action is unique and behaves differently from the other actions. Debounce Middleware logic is executed at the source-level:
181+
The following [Debounce Middleware](/docs/connections/destinations/catalog/actions-braze-web/#debounce-middleware) logic is executed at the source-level:
182182
183-
- When an Identify call is fired on a website, we will first cache and compare the user traits. If the user traits object differs from what has been cached previously, the data will be passed on to the destination flow (Destination Filters → Insert Functions → Destination Mappings).
183+
When an Identify call is fired on a website, Segment first caches and compares the user traits object.
184184
185-
- Otherwise, if user traits are the same as what's cached, we assume that that data was already sent to Braze and a new request is not made to their system.
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+
187+
- 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)