Paid media managers
Check spend and return by campaign every morning.
Track programmatic media spend, impressions, CTR, and conversions with campaign updates from Datapipe.
Updated November 2026
| Campaign name | Status | Channel type |
|---|---|---|
| Spring sale | active | 1,240 |
| Retargeting | Pending | 640 |
| Brand search | Refunded | 210 |
Check spend and return by campaign every morning.
See which ads actually bring orders.
Send each client a clear ad report every month, without exporting.
Read programmatic campaigns with impressions, clicks, spend and conversions using your StackAdapt API key.
Changes stay off until you allow them. Allowed changes apply to StackAdapt right away, and history keeps the values before and after.
Media spend reflects your account currency.
Refresh daily impressions, clicks, conversions, and media spend across native, display, and video channels.
A teammate pauses an underperforming campaign or resumes it later.
Limit: History records the campaign ID and the old and new state.
See the problem in your report, then make the fix in Datapipe instead of opening StackAdapt, finding the record and retyping it.
Teammates and AI tools you allow can make changes without getting edit access to StackAdapt.
Changes stay off until you allow them. Every change is recorded with who made it and the values before and after.
TodayLog in to StackAdapt DSP console, open Campaigns list, find campaign #cmp_9921, click toggle switch to pause.
With DatapipeCatch runaway CPA costs in your morning programmatic report and pause the campaign from Datapipe.
TodayOpen the campaign in StackAdapt, check the replacement creatives, and turn delivery back on.
With DatapipeAsk for the campaign to be resumed; the change is checked and recorded before StackAdapt turns delivery back on.
Pauses one StackAdapt campaign so it stops spending, or resumes it so it starts spending again. Budgets, bids and creatives are unchanged.
Supported fields: Campaign state.
| Field | Before | After |
|---|---|---|
| State | active | paused |
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 StackAdapt 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 StackAdapt account.
Read access for reports. The change action needs edit access in StackAdapt and stays off until the owner, an admin or a project manager allows it.
Line item and daily breakdowns are not included.
Programmatic advertising campaigns with impressions, clicks, spend and conversions from the StackAdapt DSP. Line item and daily breakdowns are not included.
Reporting reads campaigns and delivery stats. Optional campaign pause and resume are off until allowed for this data source, and every change is recorded in history. Budgets, creative assets and bidding are not changed.
1 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Campaigns with channel and state, plus impressions, clicks, spend, conversions, CPC and CPM totalled for the report dates.
7 metrics and 4 ways to split them.
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 StackAdapt changes. They can never widen their own access.
Which StackAdapt campaigns had the most conversions and the lowest CPC in the report dates?
Q4 Retargeting Display had 84 conversions at a $1.12 CPC, ahead of Native Prospecting with 41 at $1.85.
Create a project and choose StackAdapt in Data sources.
Pick where it goes. This one sends the numbers to Google Drive.
Pick where it goes. Choose campaign results and a destination.
Sample range Oct 1–Oct 29. Each row is one campaign.
| Campaign name | Status | Channel type | Spend | Conversions |
|---|---|---|---|---|
| Spring sale | active | 1,240 | $1,840.50 | 48 |
| Retargeting | Pending | 640 | $125.50 | 640 |
| Brand search | Refunded | 210 | $42.00 | 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 StackAdapt account. Nobody else gets a StackAdapt 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 StackAdapt received it, the request is marked Uncertain and is never retried automatically, so you can check StackAdapt first.
Yes. Datapipe reads the reports on this page and can make one kind of change: pause or resume campaign. 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 7 metrics and 4 ways to split them. You pick the columns when you build the report.
Programmatic advertising campaigns with impressions, clicks, spend and conversions from the StackAdapt DSP. Line item and daily breakdowns are not included. Account permissions and the records available from the provider determine which rows can be read.
One for each StackAdapt 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 StackAdapt when you are ready.