Actions6
Purchase Analytics
AI-generatedOverview
The Braze Analytics node fetches various types of time-series analytics data from the Braze platform, which is widely used for customer engagement and marketing automation. This node enables users to retrieve detailed performance metrics related to campaigns, sends, custom events, purchases, revenue, and app sessions.
Common scenarios where this node is beneficial include:
- Monitoring campaign effectiveness over a specified period.
- Analyzing purchase behavior and product sales trends.
- Tracking custom event occurrences to understand user interactions.
- Reviewing revenue data linked to specific products or apps.
- Evaluating app session metrics to gauge user engagement.
For example, a marketing analyst could use this node to pull purchase analytics for a particular product over the last 30 days to assess sales trends and optimize promotional strategies.
Properties
| Name | Meaning |
|---|---|
| Length (Days) | Number of days to include in the data series; valid range is 1 to 100 days. |
| Ending At | The end date/time for the data series in ISO 8601 format; defaults to current time if omitted. |
| App ID | Identifier of the app to filter analytics data by a specific application. |
| Product ID | Identifier of the product to filter purchase or revenue data related to that product. |
Output
The node outputs JSON data containing the requested time-series analytics information from Braze. The structure varies depending on the selected operation but generally includes arrays or objects representing metrics over time, such as counts, sums, or other aggregated values.
Each output item corresponds to one input item and contains the raw response from the Braze API under the json field.
If an error occurs during the request and "Continue On Fail" is enabled, the output will contain an error object with details including the error message, HTTP code, and Braze-specific error code.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the Braze API.
- Needs the Braze instance endpoint URL configured via credentials.
- Uses HTTP GET requests to Braze's REST API endpoints for fetching analytics data.
Troubleshooting
Common Issues:
- Invalid or missing API key can cause authentication failures.
- Incorrect or expired "Ending At" date formats may lead to request errors.
- Specifying non-existent campaign, send, event, app, or product IDs will result in empty or error responses.
- Exceeding the allowed length (more than 100 days) will violate parameter constraints.
Error Messages:
- Errors returned from Braze are captured and surfaced with messages describing the issue.
- HTTP status codes and Braze error codes are included in error outputs to aid diagnosis.
- To resolve errors, verify all input parameters, ensure valid credentials, and check Braze API documentation for limits and requirements.