Actions6
Custom Events
AI-generatedOverview
This node, named "Braze Analytics," retrieves time-series analytics data from Braze related to campaigns, sends, custom events, purchases, revenue, and app sessions. It is useful for marketers, analysts, and developers who want to monitor user engagement, campaign performance, event tracking, purchase behavior, and session metrics over time.
For the Custom Events operation specifically, the node fetches analytics data about a specified custom event, allowing users to analyze how often an event occurred within a given timeframe and with a chosen time granularity (hourly or daily). This can help understand user interactions with specific features or actions tracked as custom events in Braze.
Practical examples:
- Tracking how many times a "ButtonClicked" event happened each day over the last two weeks.
- Analyzing hourly trends of a "VideoPlayed" event during a product launch.
- Filtering custom event data by app ID or user segment to compare behavior across different user groups.
Properties
| Name | Meaning |
|---|---|
| Length (Days) | Number of days to include in the data series (minimum 1, maximum 100). Defaults to 14 days. |
| Ending At | End date/time for the data series in ISO 8601 format. Defaults to current time if not provided. |
| Event Name | The name of the custom event to analyze. This is required. |
| Time Unit | Time granularity for the data series. Options: "Day" or "Hour". Defaults to "Day". |
| App ID | Optional filter to restrict results to a specific app identifier. |
| Segment ID | Optional filter to restrict results to a specific user segment identifier. |
Output
The node outputs JSON data containing the time-series analytics for the requested custom event. The structure typically includes timestamps and corresponding event counts or metrics aggregated by the selected time unit (day or hour).
Example output JSON structure (simplified):
{
"data": [
{
"time": "2024-05-01T00:00:00Z",
"count": 123
},
{
"time": "2024-05-02T00:00:00Z",
"count": 150
}
// ... more data points
]
}
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Braze API.
- Needs the Braze instance endpoint URL configured via credentials.
- The node makes HTTP GET requests to Braze's analytics endpoints.
- No additional external dependencies beyond the Braze API and n8n's HTTP request helper.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect event name may result in empty or error responses.
- Date/time formatting errors in the "Ending At" property can cause request failures.
- Exceeding the allowed length range (1-100 days) will likely cause validation errors.
Error messages:
- Errors returned from Braze API are captured and included in the output when "Continue On Fail" is enabled.
- Typical error messages include authorization errors, invalid parameters, or resource not found.
- To resolve, verify API credentials, ensure correct event names, and validate input parameters.