How Driftrock works with affiliate partners and publishers
This guide explains how Driftrock receives leads from affiliate partners and publishers, how those leads are checked before they are accepted, and how they reach your CRM. It covers the Affiliate Capture, Acceptance Rules, deduplication, validation responses and reporting.
Overview
Many brands run lead generation with third-party publishers and affiliates, typically on a Cost Per Lead (CPL) basis, where the partner is paid for each lead they supply. In Driftrock, these partners send leads into your account through an Affiliate Capture.
An Affiliate Capture receives lead data through the Affiliate Event API: a direct, server-to-server connection between the partner's system and Driftrock. Each partner has its own API key and Affiliate ID, so Driftrock can identify which partner sent each lead.
Every lead that arrives is checked against the rules and criteria that you set. Leads that meet your criteria are marked Accepted and sent to your Destinations. Leads that do not are marked Rejected, with the reason recorded.
The parts involved in the process
Affiliate Capture: the Capture type that receives partner leads. You define which fields you expect, which fields are required, and which partners send leads to it.
API keys: each partner is issued a unique API key. Driftrock uses the key to confirm that a lead came from that partner. Because keys are separate, you can revoke one partner's access without affecting any other partners.
Affiliate ID: a unique identifier Driftrock assigns to each partner you add to the Capture. It is used to attribute each lead to the correct partner in reporting.
Acceptance Rules: conditions a lead must meet before Driftrock accepts it. Rules can use any field on the lead, including standard fields (email, phone, postcode), custom qualification fields (for example purchase timeline or vehicle of interest) and deduplication data.
Deduplication: Driftrock can add deduplication fields to every lead, showing whether the same email address, or other form value, has been seen in the last 30, 60 or 90 days across your lead sources. For Affiliate Captures you can also set custom deduplication rules, for example rejecting a lead if the same email and vehicle model has been submitted by any partner in the last 30 days.
Destinations: the systems accepted leads are sent to, such as your CRM.
How it works
A customer submits an enquiry on a partner's platform, such as a publisher's website form or a native ad (such as The Car Expert or Carwow). The partner sends the lead to Driftrock's Affiliate Event API as a JSON request, including their API key in the request header and their Affiliate ID in the body.
Driftrock authenticates the request using the API key and identifies the partner using the Affiliate ID. It then maps the partner's fields to your Driftrock fields.
Driftrock checks the lead against your required fields, your Acceptance Rules and your deduplication rules. The API responds to the partner straight away to confirm whether the lead was accepted. If a required field is missing, or a value is not recognised (for example a vehicle name that does not match your vehicle table), Driftrock returns an error with a message describing the problem, so the partner can correct the data.
Accepted leads are sent to your Destinations in real time and tagged with the partner's name as the Source or Campaign value. Rejected leads are not sent to your Destinations. They are logged in the Rejected tab of Your Captures and in Lead Quality reporting, with the condition each lead failed.
What your partners see
When you set up an Affiliate Capture, Driftrock generates instructions for each partner. These include their API endpoint URL, Affiliate ID and an example payload showing the field names and formats to use. Driftrock also generates a documentation page that shows partners the Acceptance Rules their leads must meet.
You can created a Dashboard which can be shared with partners, allowing them to view the delivery of their campaigns, including how many of their leads were accepted.
Getting started
Prerequisites: you need Admin access to your Driftrock account to create API keys.
Go to Settings, then API Settings, and click Add New API Key. Create one key per partner and name it after that partner.
Copy each key and store it securely until you share it with the partner.
Go to the Capture Library and select Affiliate Capture.
Define the fields you expect to receive, such as Email, First Name and Phone. Toggle Required on any field that must be present.
Add the name of each partner under Affiliates. Driftrock assigns each one an Affiliate ID.
Check the Marketing Tracking section. Driftrock uses the partner name as the Source or Campaign value by default.
Add your Acceptance Rules and any custom deduplication rules in the relevant setup steps.
Go to the Destinations step, add your CRM, map your Driftrock fields to your CRM fields and activate the sync.
Send each partner their API endpoint URL, Affiliate ID, API key and example payload, along with the link to your acceptance criteria.
Ask each partner to send one live test lead, then check Your Captures and your CRM to confirm it arrived with the correct fields and partner tag.
Reporting
Each accepted lead carries the partner's name as its Source or Campaign value, so you can report on volume and outcomes by partner. The Rejected tab in Your Captures lists each rejected lead with the rule it failed, which you can use when reconciling lead counts with partners.
Tips
Issue a separate API key for every partner. This keeps reporting accurate and lets you revoke access for one partner only.
Share API keys using a secure method rather than plain email.
Mark fields as Required only where you need them, as leads missing a required field are rejected.
Share your Acceptance Rules and deduplication criteria with partners before a campaign starts.
Acceptance Rules apply only to leads that arrive after the rules are saved. If you change them during a campaign, the new criteria apply from that point onwards.
If partners use different names for vehicle models, add those names as aliases in your Vehicle Database so leads match the correct model.
If a partner's leads are not appearing, check that they are using the correct API key and endpoint, then review the Rejected tab for the reason.

