How to measure affiliate partner performance
This guide explains how to measure the performance of your affiliate partners and publishers in Driftrock: how many leads each partner sends, how many are accepted, how many are valid and unique, and how many lead to a sale.
What you can measure
Every lead from an Affiliate Capture carries the partner's name as its Source or Campaign value. You can use this to break down any of the following measures by partner.
Lead volume: the number of leads each partner sends. Driftrock can report this as a total count of every lead received, or as a unique count of distinct people with duplicates removed.
Accepted and rejected leads: how many leads passed or failed your required fields, Acceptance Rules and deduplication rules. Each rejected lead records the reason it was rejected.
Duplicates: how many leads were from someone already seen within your lookback period. Driftrock adds deduplication fields to every lead showing whether the same email address has been seen in the last 30, 60 or 90 days.
Validity: how many leads have a valid email address, phone number and postal address. This requires Lead Validation to be enabled. Driftrock adds valid_email, valid_phone and valid_address fields to each lead, each set to true or false.
Incomplete leads: if the Capture uses a Lead Type, leads missing any of its required fields are marked Incomplete.
Downstream outcomes: how many leads led to a test drive, finance approval, sale or other result. This requires you to send these outcomes back into Driftrock as action Events (see below).
Where to find the data
Your Captures. Open the Affiliate Capture and use the Rejected tab to see each rejected lead and the rule it failed. The Incomplete tab lists leads missing fields required by the Capture's Lead Type.
Dashboards. Build your own dashboards in Reporting, then Dashboards, to track the measures that matter to you. You can filter charts to specific Captures and by lead status, including Success, Failed, Rejected and Incomplete.
Measuring outcomes after the lead
To see which partners produce sales rather than just leads, send downstream outcomes from your CRM or other systems back into Driftrock using a Webhook Capture set up for action Events. Each action Event, such as "Test Drive Completed" or "Vehicle Sold", includes an email address. Driftrock uses it to match the action to the original lead.
Once matched, the action inherits the original lead's marketing attribution, including its source. This means you can report on outcomes by partner in the same way as leads.
Getting started
To build a partner performance dashboard:
Go to Reporting, then Dashboards, and click + New Dashboard.
Add a Table chart of leads grouped by source, to compare volume across partners.
Add a Table chart of leads by status for each partner, to compare accepted and rejected leads.
Add a Timeseries chart of leads over time, to see trends for each partner.
If you send action Events, add charts of actions by source to compare outcomes across partners.
To review rejections for a partner:
Go to Your Captures and open the Affiliate Capture.
Open the Rejected tab.
Review the reasons. A high number of rejections for the same reason usually points to a data issue on the partner's side.
Tips
Use a Table chart when you need unique counts. Table is the only chart type that shows unique as well as total counts; all other chart types show totals only.
To group a Timeseries or Table chart by a field such as source, that field must be present on every lead in the chart.
Use Driftrock's standard field names (for example
emailandphone) on your Capture. Leads mapped to custom field names cannot be validated automatically.Allow a few days after enabling Lead Validation before comparing partners, so there is enough data.
If a partner has a high duplicate or rejection rate, share the reasons with them and review your Acceptance Rules and deduplication settings.
When reconciling with a partner at the end of a billing period, use accepted lead counts rather than total leads received, so rejected and duplicate leads are excluded.
Make sure action Events include the email address used on the original lead, so they can be matched back to the partner.
