Lifecycle marketers
Track opens, clicks and list growth across every send.
Review Braze campaign delivery, Canvas performance, segments and daily KPIs, with controlled user attribute and subscription group updates from Datapipe.
Updated November 2026
| Campaign name | Channels | Messages sent |
|---|---|---|
| Spring sale | push, email | 18,400 |
| Retargeting | 640 | 410 |
| Brand search | 210 | 155 |
Track opens, clicks and list growth across every send.
See whether the newsletter is growing without logging in.
Send each client a monthly email performance report.
Read campaigns, Canvases, dynamic segments and daily engagement metrics using your Braze REST API key and endpoint.
Changes stay off until you allow them. Allowed changes apply to Braze right away, and history keeps the values before and after.
Optional user attribute and subscription group updates stay off until enabled.
Refresh sends, opens, clicks, conversions and daily KPIs across email, push and in-app channels in one report.
A teammate updates a user's loyalty tier or lifecycle attribute, and Braze applies the change to that external ID.
Limit: History records the before and after values.
See the problem in your report, then make the fix in Datapipe instead of opening Braze, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to Braze.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayOpen Braze Audience > Search Users, find the external ID, edit custom attributes, and save.
With DatapipeReview high-value accounts in your retention report and update custom attributes from Datapipe with an approval trail.
TodayLook up the user profile in Braze, edit the attribute field, and confirm.
With DatapipeSpot formatting or tier mismatches in your Braze segment report and apply the corrected attribute value directly.
Updates standard profile attributes (first name, last name, email) for one existing Braze external_id via /users/track. Custom attributes, purchases, and campaign triggers are unchanged.
Supported fields: First name, Last name, Email address.
TodayOpen the user profile in Braze, scroll to Subscription Groups, and toggle subscribed or unsubscribed.
With DatapipeProcess opt-in or opt-out updates from your compliance report in Datapipe; history records the exact before and after status.
TodayFilter bounced users, open each Braze profile, and change the subscription group status.
With DatapipeUpdate subscription group membership for flagged recipients without altering campaign setups.
Sets one user's email or SMS subscription group status in Braze via /subscription/status/set. Other subscription groups and global opt-out settings are unchanged.
Supported fields: Subscription group UUID, Subscription status.
| Field | Before | After |
|---|---|---|
| loyalty_tier | silver | gold |
Source changes are managed on the Changes page in Datapipe. Approval is optional: set it for risky changes, for every change, or for one person. AI tools such as ChatGPT can never widen their own access. Who can turn this on?
Provider permissions still apply, and automations in Braze may react to changes.
Only fields supported by an allowed action can be changed; for some actions the owner, an admin or a project manager also picks the individual writable fields.
An API key or token from your Braze account.
Read access for reports. The 2 change actions need edit access in Braze and stay off until the owner, an admin or a project manager allows them.
Anything your connected account cannot see in Braze.
Campaign delivery performance, Canvas multi-step journeys, dynamic segments, and daily engagement KPIs from your Braze workspace.
Reporting reads campaigns, Canvases, segments, and daily KPIs. Optional user attribute updates and subscription group status updates are off until allowed for this data source, and every change is recorded in history. Campaign schedules and Canvas flows are not altered.
4 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Campaign inventory from Braze (/campaigns/list and /campaigns/details) with totals over the report dates from /campaigns/data_series: messages sent, unique recipients, opens, clicks, conversions and revenue.
Canvas journeys from Braze (/canvas/list and /canvas/details) with total entries, conversions and revenue over the report dates from /canvas/data_series.
Current audience segments from Braze (/segments/list and /segments/details) with tags, creation and update dates and analytics tracking status.
Daily active users, new users and uninstalls for each day in the report dates (UTC). Daily active users are counted per day, so do not add them up to get unique users.
38 report fields across 4 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also make allowed Braze changes. They can never widen their own access.
Compare conversions and unsubscribe rates across active Braze campaigns and Canvases.
The Onboarding Welcome Canvas converted 14.8% of entered users with a 0.2% unsubscribe rate, outperforming the weekly newsletter at 3.4%.
Campaign inventory from Braze (/campaigns/list and /campaigns/details) with totals over the report dates from /campaigns/data_series: messages sent, unique recipients, opens, clicks, conversions and revenue.
Use this template →Canvas journeys from Braze (/canvas/list and /canvas/details) with total entries, conversions and revenue over the report dates from /canvas/data_series.
Use this template →Current audience segments from Braze (/segments/list and /segments/details) with tags, creation and update dates and analytics tracking status.
Use this template →Daily active users, new users and uninstalls for each day in the report dates (UTC).
Use this template →Create a project and choose Braze in Data sources.
Pick where it goes. This one sends the numbers to Amazon Redshift.
Pick where it goes: a sheet, a chart, BigQuery, Drive, a CSV file, or an AI assistant.
Sample range Oct 1–Oct 29. Each row is one campaign.
| Campaign name | Channels | Messages sent | Unique opens | Unique clicks | Conversions | Revenue | Segment name |
|---|---|---|---|---|---|---|---|
| Spring sale | push, email | 18,400 | 6,420 | 860 | 312 | $4,680.00 | 1,240 |
| Retargeting | 640 | 410 | 410 | 410 | 640 | 640 | 640 |
| Brand search | 210 | 155 | 155 | 155 | 210 | 210 | 210 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
The workspace owner, workspace admins and project managers. Changes start off. They choose which changes are allowed for each data source and who can make them: project operators and managers, selected teammates, and the AI tools those people connect. They can change this at any time.
No. Teammates make allowed changes in Datapipe, and Datapipe applies them through the connected Braze account. Nobody else gets a Braze login from this.
Yes, if that change is allowed for them. They work through Datapipe the same way a teammate does, within the same allowed changes and fields, and every change is recorded in the Changes history. AI tools can switch changes off, but they can never widen their own access. Asking for more waits for a person.
Yes, if you want. For each data source, approval can cover risky changes only (deleting, sending, publishing, refunds and price changes) or every change. You can also switch it on for one person, such as an intern. Those changes wait on the Changes page until the owner, an admin or a project manager approves them. Nobody but the owner approves their own change.
Datapipe sends each change once and records the result in the Changes history. If it cannot confirm that Braze received it, the request is marked Uncertain and is never retried automatically, so you can check Braze first.
Yes. Datapipe reads the reports on this page and can make 2 kinds of change: update user profile attributes; update subscription group status. Each one stays off until the owner, an admin or a project manager allows it for this data source. Allowed changes apply right away and are recorded in the Changes history. Provider permissions still apply.
This page lists 38 report fields across 4 datasets. You pick the columns when you build the report.
Campaign delivery performance, Canvas multi-step journeys, dynamic segments, and daily engagement KPIs from your Braze workspace. Account permissions and the records available from the provider determine which rows can be read.
One for each Braze account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add Braze when you are ready.