Voluum
AdvertisingPull Voluum performance reports grouped by campaign, offer, country, or device, and manage the tracking entities behind them: agents create campaigns, offers, landers, and flows, log offline conversions via server-to-server postbacks, and reconcile traffic sources and affiliate networks.
What This Integration Enables
Voluum is the ledger of record for paid traffic: every visit, click, cost, and conversion reconciled across traffic sources and affiliate networks. Media buying punishes slow readers of that ledger, and FlowRunner's position is that reading it should never depend on a human refreshing a dashboard. Agents run the report engine on a schedule, backfill the conversions pixels cannot see, and assemble campaigns, offers, and flow changes for a buyer to approve, because in this account, changing an entity changes what gets tracked. - Scheduled Get Report pulls grouped by campaign, offer, country, or device feed dashboards and threshold alerts - Server-to-server postbacks via Log Manual Conversion attribute offline and delayed revenue to the originating click - Campaign and offer creation resolves traffic source and network IDs first, so new entities are born wired correctly - Update operations change only supplied fields, keeping automated adjustments surgical - Structural changes route through [human-in-the-loop](/concepts/human-in-the-loop) approval before the ledger's shape changes
Without FlowRunner
With FlowRunner
Use Case Scenarios
The ROI watchdog that never sleeps through a bad night
An agent runs Get Report grouped by campaign every hour, appending each pull to [Google Sheets](/integrations/google-sheets) and checking ROI against per-campaign thresholds. When a campaign crosses the line, the agent drills in: Get Report grouped by lander and by country isolates where the loss concentrates, and Get Campaign attaches the current cost model. The buyer wakes to a [Slack](/integrations/slack) message that already contains the diagnosis, decides the fix, and the agent applies it with Update Campaign.
The revenue the pixel never saw
A checkout captures the Voluum click ID into the order's metadata. When the payment succeeds in [Stripe](/integrations/stripe), the agent calls Log Manual Conversion with that click ID, the transaction ID, and the payout amount. Refunds post as status updates using the same transaction ID, so nothing double-counts. Phone sales logged in the CRM follow the same path nightly. The ROI column in every subsequent Get Report now includes the revenue that used to leak, which changes which campaigns look worth scaling.
Campaign launches as an assembly line
A launch brief lands. The agent calls List Traffic Sources and List Affiliate Networks to resolve IDs, then Create Offer with the destination URL, payout, and the {clickid} token preserved. Create Campaign links the offer to the source with the cost model from the brief and returns the generated tracking URL. The buyer receives the finished structure with the tracking URL ready to arm at the traffic source. Setup that used to be an afternoon of clicking becomes a review of finished work.
Human-in-Loop Highlight
Delete Campaign archives a campaign so it stops tracking. The report history survives, but the tracking does not, and that is the trap: if the traffic source is still live, paid clicks keep arriving at a URL that no longer records them. Spend continues, attribution stops, and the buyer discovers the gap days later as a hole in the ledger. So the cleanup agent never archives on its own read of "inactive." It assembles the case: "Campaign PUSH-MX-Feb: zero visits in 30 days per Get Report, traffic source shows the zone paused, no active flow references. Archive it and the two offers only it uses?" The buyer confirms what dies, the agent calls Delete Campaign and Delete Offer, and the log records the approval. The same discipline applies to Log Manual Conversion, because writing revenue into the ledger changes every ROI decision made after it.
Agent Capabilities
20 actionsReporting
3- Get Report Runs the flagship performance report over a date range, grouped by dimensions like campaign, offer, lander, traffic source, country, device, day, or hour, with metrics from visits and clicks through revenue, cost, profit, ROI, CTR, CV, EPV, and CPV. Supports column selection, filtering, timezone, currency conversion, sorting, and pagination. The engine behind every watchdog and dashboard on this page.
- List Report Columns Returns the catalog of every dimension and metric the report engine accepts, with internal names, labels, and types. Used to build and validate report configurations dynamically.
- Log Manual Conversion Records a server-to-server postback against a tracked click ID, with optional transaction ID, revenue, and conversion status. The write that attributes offline, phone, and delayed revenue to the click that earned it.
Campaigns
5- List Campaigns Retrieves all tracking campaigns with name, ID, traffic source, cost model, tracking URLs, and deleted status. The enumeration step behind dashboards and hygiene sweeps.
- Get Campaign Fetches one campaign's full configuration, including flow, paths, and cost settings. The inspection step before any update or archive decision.
- Create Campaign Creates a campaign linked to a traffic source with a cost model and either a flow or a direct offer, returning the generated tracking URL. The launch step of the assembly line.
- Update Campaign Updates a campaign's editable fields, changing only what is supplied. The lever buyers pull through agents for cost and flow adjustments.
- Delete Campaign Archives a campaign so it stops tracking while report history is retained. The operation this page's human gate exists for.
Offers
5- List Offers Retrieves all offers with destination URL, payout, currency, country targeting, and network association.
- Get Offer Fetches one offer's full configuration before an update or a flow decision.
- Create Offer Creates an offer with destination URL and default payout, preserving Voluum tracking tokens like {clickid} in the URL.
- Update Offer Updates an offer's editable fields, changing only what is supplied. Used for payout corrections and URL swaps.
- Delete Offer Archives an offer while retaining its report history. Gated alongside campaign archives in cleanup workflows.
Landers
2- List Landers Retrieves all landing pages with URL and offer click-through counts. Used to enumerate what flows can route to.
- Get Lander Fetches one lander's configuration before it is referenced in a flow or a report drill-down.
Flows
2- List Flows Retrieves the reusable path and rule configurations shared across campaigns.
- Get Flow Fetches one flow's default and rule-based paths and the landers and offers each path routes to. The inspection step before attaching a flow to a campaign.
Traffic Sources
2- List Traffic Sources Retrieves all configured traffic sources with tracking tokens and postback settings. The ID-resolution step before campaign creation.
- Get Traffic Source Fetches one source's tokens, cost settings, and custom variables before campaigns are created against it.
Affiliate Networks
1- List Affiliate Networks Retrieves all configured affiliate networks with default payouts. The ID-resolution step before offer creation.
Frequently Asked Questions
What can FlowRunner do with Voluum?
FlowRunner agents can run Get Report, List Report Columns, and Log Manual Conversion in Voluum, plus 17 more actions.
Does connecting Voluum to FlowRunner require OAuth?
No. Voluum connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Voluum trigger a FlowRunner workflow automatically?
Voluum doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Voluum
$100 in credits. No card required. Connect in minutes.