Voluum

Voluum is an affiliate and media-buying attribution tracker. It issues a unique click ID when a visitor arrives through a Voluum tracking link, then records the resulting conversion through a server-to-server (S2S) postback to your Voluum tracking domain.

Datafly Signal delivers those conversions server-side. Each conversion is matched back to its originating click using the Voluum click ID (cid) that Datafly.js captures when the visitor lands, so you keep accurate attribution even when the browser pixel is blocked.

Voluum has no pageview or analytics ingestion endpoint — it only accepts conversions. Signal therefore delivers conversion events (such as a purchase or a sign-up) and drops everything else.

Prerequisites

A Voluum account with at least one campaign tracking traffic through a Voluum tracking link.
Your Voluum tracking domain — the host conversions are posted to (for example yourcompany.voluumtrk.com, or your dedicated SSL domain). You can find it in Voluum under Settings > Domains, or read it from the prefilled postback URL shown when you set up conversion tracking.
Visitors must arrive through a Voluum tracking link so a click ID is available. Without a click ID, a conversion cannot be attributed.
(Optional) If you want to bucket conversions by type, create your Custom Conversions values in Voluum first under Settings > Custom Conversions. These values are case-sensitive.

Configuration

Field	Required	Description
Tracking Domain	Yes	Your Voluum tracking domain, hostname only — no `https://`, no trailing slash, no `/postback`. Example: `yourcompany.voluumtrk.com`.

There is no API key or secret. Voluum authenticates the conversion implicitly through the unguessable click ID issued at landing time, so the only thing Signal needs is which tracking domain to post to.

Configure in Signal

In the Signal management UI, go to Integrations and add Voluum.
Enter your Tracking Domain.
Attach the integration to the pipeline that carries your conversion events.
Select the Default preset. It maps Order Completed to a purchase conversion and Signed Up to a lead conversion, both keyed on the Voluum click ID.
Save and enable the integration.

API Endpoint

Signal sends a single HTTP GET request per conversion to:

https://<your-tracking-domain>/postback?cid=...&payout=...&txid=...&et=...&currency=...

Parameter	Description
`cid`	Required. The Voluum click ID. Matches the conversion to its originating click.
`payout`	Conversion revenue / commission (for example `49.99`). Omit to use the offer-level payout.
`txid`	Unique transaction ID. Used for de-duplication and for tracking upsells / secondary conversions against the same click.
`et`	Event type. Buckets the conversion into a Custom Conversion slot (for example `purchase`, `lead`). Case-sensitive, and must be pre-created in Voluum.
`currency`	3-letter ISO-4217 currency code. Overrides the offer’s default currency.

A successful postback returns HTTP 200. There is no request body — every field travels on the query string.

Identity Signals

Voluum attribution is click-based, not identity-based. There is no hashed-PII match path on the conversion postback.

Signal	Voluum field	Notes
Voluum click ID	`cid`	The only match key. Captured by Datafly.js from the `cid` / `vlmcid` landing-page URL parameter (or Voluum’s first-party click cookie) when the visitor arrives through a Voluum link, and forwarded on every event.

Because the click ID is the sole match key, email and phone are never sent and never hashed for Voluum. Consent has no dedicated postback field; gate Voluum delivery at the pipeline level if you only want to send conversions for consented traffic.

Event Mapping

Signal uses GA4-style snake_case event names. The Default preset maps:

Signal event	Voluum `et`	Fields sent
`Order Completed`	`purchase`	`cid`, `payout` (from `total`), `txid` (from `order_id`), `currency`
`Signed Up`	`lead`	`cid`, `txid` (from `user_id`)

All other events are dropped — Voluum only ingests conversions.

Example: Order Completed

A Datafly.js call on your order-confirmation page:

datafly.track("Order Completed", {
  order_id: "ORD-10293",
  total: 49.99,
  currency: "USD"
});

Datafly.js automatically attaches the Voluum click ID it captured at landing. Signal then sends:

GET https://yourcompany.voluumtrk.com/postback?cid=5f8d...c1a&et=purchase&payout=49.99&txid=ORD-10293&currency=USD

Voluum credits the conversion and revenue against the campaign that produced the click.

Testing

Visit your site through a Voluum tracking link so a click ID is issued, then confirm the click ID is present (check the landing URL cid / vlmcid parameter or the Voluum click cookie).
Complete a test conversion (for example a test order) so an Order Completed event fires.
In Signal’s Event Debugger, confirm the Voluum delivery shows an HTTP 200 and that cid, et, payout, and txid are populated.
In Voluum, open the relevant campaign report and confirm the Conversions count and revenue incremented for that click.

Troubleshooting

Conversion not appearing in Voluum — Almost always a missing or wrong cid. Confirm the visitor arrived through a Voluum tracking link and that Datafly.js captured the click ID before the conversion event fired.
et value ignored / conversion uncategorised — The et value must be pre-created under Settings > Custom Conversions in Voluum, and values are case-sensitive (purchase and Purchase are different).
404 from the postback — The tracking domain is wrong, or it includes https://, a trailing slash, or /postback. Enter the hostname only.
Wrong currency / payout — If you omit currency, Voluum applies the offer’s default currency. Send the currency field to override it, and confirm payout is a plain decimal number.
Duplicate conversions — Ensure txid is a stable, unique value per order so Voluum can de-duplicate retried postbacks.

Adtraction Partnerize