# Broadcast Records Broadcast Records let you track which users have received from your broadcasts, including the receipt status for every single user who has received it.

Every time you publish a broadcast, BotDistrikt tracks a **receipt** - also known as a Broadcast Record, for each user. For each record, BotDistrikt tracks * The identity of the user who received it * The date and time that the user received it * The status of the receipt, whether it was **completed** or an **error** * If the broadcast status is **error** * The accompanying error message explaining why there was an error * Latency - the difference between the time the broadcast was scheduled and the time the user received it ### Receipt of what a user received

Hover over a record to see what a user received during the broadcast. Each user receives a unique personalized message based on the variables you use in the message. Use the Broadcast Records page to: * Filter Broadcast Records * Export to CSV ### Filtering Broadcast Records Use the Filters on the top of the page to filter records based on several fields. Each field has a specific filter use case.

Field	Use Case
ID	Finds all records from a specific ID
Broadcast ID	Find all records a specific broadcast ID
User ID	Finds all records from a specific user ID
Story ID	Find all records publishing a broadcast of a specific story ID
Story Name	Find all records publishing a broadcast of a specific story, filterable by the story's name
User Name	Find all broadcast sent to a specific user, filterable by the user's name
Status	Find all broadcast records of a status completed or error
Message	Find all broadcast records of status error with a specific of filterable error message
Recorded At	Find all records received before or after a specific date and time
Number of Responses	Sometimes when a broadcast publishes a story that uses only 1 webhook to get a dynamically generated response, the webhook might return no responses for a specific user. Filter by Number of Responses greater than 0, to filter only those users who received a message

### Exporting as CSV Filter broadcast records by clicking on add filter and selecting the appropriate attribute and function for the search parameter. To export filtered records, click on Select Action and Export rows to CSV.

**Export to CSV** will generate a .csv file with the following fields:

Field	Description
ID	An identifier based on the unique Broadcast ID.
User ID	A unique identifier assigned to the user.
User	The display name or alias of the user.
Received Broadcast ID	The unique identifier of the broadcast received by the user.
Broadcast Time	The timestamp of when the broadcast was sent.
Story ID	A unique identifier for the story associated with the interaction.
Story Name	The name or title of the story.
Status	Indicates the current state of the interaction.
Message	The content of the message exchanged during the interaction.
Created At	The timestamp of the interaction.

{% hint style="warning" %} BotDistrikt's broadcast functionality has a default push configuration of * 5 Maximum Retries * 0.1s Backoff View up to 5 Broadcast Records with errors for the same user because the platform attempted to retry a failed broadcast to the user 5 times {% endhint %} {% hint style="info" %} For **Enterprise** customers, the push configuration is customizable. {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.botdistrikt.com/features/inbox/broadcast-records.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.