> For the complete documentation index, see [llms.txt](https://docs.pulseinsights.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pulseinsights.com/integrations/integrations-overview/braze.md). # Braze ## What the integration accomplishes You will be able to take responses from Pulse Insights and insert them into the appropriate user's Braze record to personalize future marketing and servicing communications and experiences. For example you might: * Capture a shopping preference and use that to personalize marketing emails * Capture data such as location or birthday to trigger or personalize offer emails * Capture feedback like satisfaction to create segments of engaged users * Capture email feedback like email relevance to suppress disinterested audiences {% hint style="info" %} Pulse Insights will get the data into Braze. From there, it will be up to you to leverage that data to provide superior service and marketing. ) {% endhint %} ## Prerequisites Email links that capture user feedback need to ingest the User ID in order to update the appropriate record in Braze. You can ingest the User ID by appending the following to the Pulse Insights links. ``` &uid={{${user_id}}} ``` Learn more about [link creation here](/implementing-pulse-insights-dev/implementing-in-email.md). ## Inputs we'll need from you * Endpoint details * API Key * REST API key permissions (e.g. Track) * Attribute name to update * Data Type (Datetime, Boolean, Number, String, Blank) * Client Key (`user_id` OR `braze_id`). Please see [here](/implementing-pulse-insights-dev/implementing-on-web-and-mobile-web/client-key.md) for more details on Client Key. * Frequency (batch or near real-time) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pulseinsights.com/integrations/integrations-overview/braze.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.