Braze Analytics icon

Braze Analytics

Get analytics data from Braze campaigns and sends

Actions6

Session Analytics

AI-generated

Overview

This node, named "Braze Analytics," retrieves various types of time-series analytics data from the Braze platform. It supports multiple operations to fetch campaign performance, send analytics, custom event data, purchase and revenue analytics, and session analytics related to mobile or web apps.

A common use case is to integrate Braze analytics into automated workflows for marketing or product teams who want to analyze user engagement, campaign effectiveness, purchase behavior, or app session trends without manually exporting data. For example, a marketer could automatically pull campaign analytics daily to update dashboards or trigger alerts if performance drops.

Specifically, the Session Analytics operation fetches time-series data about app sessions, such as counts of sessions over specified time intervals, optionally filtered by app ID or user segment.

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.
Time Unit Granularity of the time series data; options are "Day" or "Hour".
App ID Optional filter to restrict results to a specific application identifier.
Segment ID Optional filter to restrict results to a specific user segment identifier.

These properties configure the parameters for the Session Analytics API call, controlling the time range, granularity, and filtering scope.

Output

The node outputs JSON data representing the time-series session analytics retrieved from Braze. The structure corresponds directly to the Braze API response for session data series, typically including timestamps and associated session metrics (e.g., session counts).

Each item in the output array contains a json field with the raw API response data. There is no binary data output.

Example output snippet (conceptual):

{
  "data": [
    {
      "time": "2024-05-01T00:00:00Z",
      "sessions": 1234
    },
    {
      "time": "2024-05-02T00:00:00Z",
      "sessions": 1500
    }
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the Braze API.
  • Needs the Braze instance endpoint URL configured via credentials.
  • Uses HTTP GET requests to Braze's REST API endpoints.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Incorrect or expired "Ending At" date format may result in request failures.
    • Specifying non-existent app or segment IDs will return empty or error responses.
    • Exceeding the maximum allowed length (over 100 days) will be rejected.

  • Error messages:

    • Errors returned from Braze API are captured and surfaced with details including HTTP status code and Braze-specific error codes.
    • If "Continue On Fail" is enabled, errors are included in the output JSON under an error field instead of stopping execution.
    • Common resolution steps include verifying credentials, checking parameter formats, and ensuring resource identifiers exist in Braze.

Links and References

Discussion