Skip to content

Clarify Debounce Middleware behavior in public docs #7132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 16, 2024
Merged

Clarify Debounce Middleware behavior in public docs #7132

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5e07f37
Update index.md
joeynmq Oct 10, 2024
87eea7c
Apply suggestions from code review
forstisabella Oct 16, 2024
8f231be
Apply suggestions from code review
forstisabella Oct 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions src/connections/destinations/catalog/actions-braze-web/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,3 +172,14 @@ When "Enable SDK Authentication" is enabled, Segment will set Braze's `enableSdk

Keep the following in mind if you plan to move to Braze (Actions) from the classic Braze destination.
{% include components/actions-map-table.html name="braze-web" %}


## FAQ

### How Debounce Middleware works?

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:

- 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).

- 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.