Rockerbox

Rockerbox is a marketing measurement and multi-touch attribution platform. Datafly Signal delivers your conversion events to Rockerbox’s real-time conversion webhook server-to-server, so attribution no longer depends on a browser pixel that ad blockers and ITP can strip away.

Because Signal sends conversions from your own first-party endpoint with the user’s email and your internal customer ID, Rockerbox can match conversions to marketing touchpoints with higher fidelity than a client-side tag.

Why route Rockerbox through Datafly Signal

• Conversions survive ad blockers and tracking prevention. A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari’s ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Rockerbox optimises against are not filtered by the browser.
• One consent decision governs every destination. Rockerbox is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
• No vendor tag on the page. Removing it removes its page weight and its independent access to your visitors.

Prerequisites

• A Rockerbox account with measurement enabled.
• Your Advertiser ID. Rockerbox issues this per account — ask your Rockerbox account manager if you do not have it. It is the value in the advertiser query parameter on the webhook URL.
• The conversion actions you want to measure agreed with your Rockerbox account team (for example purchase, signup, lead). Each distinct action string appears as a named conversion in the Rockerbox dashboard.
• Datafly Signal deployed with a pipeline already collecting events from your site via Datafly.js.

Configuration

Rockerbox’s conversion webhook authenticates solely by the advertiser query parameter. There is no API key or bearer token for this endpoint, so keep your Advertiser ID treated as a shared secret at the deployment level.

Configure in Signal

1. In Management UI, open your pipeline and add a new destination.
2. Choose Rockerbox from the Attribution category.
3. Enter your Advertiser ID.
4. Select the Default preset. It maps the standard Signal conversion events (Order Completed, Signed Up, Lead Generated) to Rockerbox actions and forwards page views, and attaches email, phone, and your customer ID for identity matching.
5. Map any additional events or custom conversion parameters as needed, then save and enable the destination.

API Endpoint

Signal delivers each conversion as a single JSON POST:

POST https://webhooks.getrockerbox.com/webhook/data?advertiser=<ADVERTISER_ID>
Content-Type: application/json

Rockerbox accepts exactly one conversion per request. The four required fields are email, customer_id, action, and timestamp (epoch seconds, UTC). At least one of email or customer_id must be present for a conversion to attribute; Signal sends both whenever they are available.

Identity Signals

Rockerbox performs its own identity resolution and hashing server-side, so Signal sends plaintext email and phone on this first-party webhook — they are not pre-hashed (unlike vendor conversion APIs such as Meta CAPI).

Event Mapping

Signal’s GA4-style event names map to Rockerbox action values. The Default preset includes:

Example

Datafly.js call on your site:

datafly.track("Order Completed", {
  order_id: "PRCH11809871",
  revenue: 27.50,
  currency: "USD"
});

Resulting payload Signal delivers to Rockerbox:

{
  "email": "jane@example.com",
  "customer_id": "user_8842",
  "action": "purchase",
  "timestamp": 1535147451,
  "revenue": 27.50,
  "order_id": "PRCH11809871"
}

Testing

1. Trigger a conversion on your site (or use Signal’s Event Debugger to replay one).
2. In the Signal Event Debugger, confirm the Rockerbox destination shows a 2xx response and inspect the exact JSON body sent.
3. In the Rockerbox dashboard, open your conversion report and confirm the conversion appears under the matching action within Rockerbox’s processing window.

Troubleshooting

• No conversions appearing: confirm the advertiser query parameter matches the Advertiser ID issued by your Rockerbox account manager. A wrong or missing value returns a 4xx.
• Conversions not matching to touchpoints: ensure at least one of email or customer_id is populated. Conversions with neither cannot attribute.
• 400 responses: Rockerbox accepts only one conversion per request and only valid JSON. Signal sends one event per request by design, so a 400 usually means a malformed custom field — check your event mappings.
• Unexpected actions in the dashboard: every distinct action string is a separate named conversion. Keep your vendor_event_name values stable and snake_case to avoid fragmenting reports.