Creating test leads with affiliate partners
Before an affiliate partner or publisher starts sending live leads, you should send test leads through the connection to confirm it works. This guide explains how Driftrock handles test leads, the ways to send one, and what to check once it arrives.
How Driftrock handles test leads
Driftrock processes a test lead in the same way as any other lead. It is validated, checked for duplicates, checked against your Acceptance Rules, sent to your Destinations and included in your reporting.
This means a test lead shows you exactly what will happen to a live lead. It also means that, unless you set things up otherwise, a test lead reaches your CRM and any other Destinations, and triggers any automations on the Capture, such as autoresponders or internal notifications.
Ways to send a test lead
Ask the partner to send one. This is the most complete test, because it uses the partner's own system, their API key and their Affiliate ID. It confirms that the partner's integration and your Capture work together.
Send one yourself with an API tool. You can send a request to the API endpoint yourself, using a tool such as Postman. Use the API endpoint URL, include an API key in the request header and use the example payload from the Capture's setup as the request body. This is useful for checking your Capture's mapping and rules before the partner's integration is ready.
Send one from a Driftrock account. If the partner sends leads from their own Driftrock account through a Send to Driftrock automation, they can send a test lead through that automation once it is set up.
Keeping test leads away from live systems
If your account uses Lead Types, you can set up a Capture in the Testing automation group. A Capture in the Testing group only triggers the automations in the Testing group for its Lead Type, not the ones in the Live group. This lets you check mapping and routing with test leads without sending them through the automations your live Captures use.
A Capture's Lead Type is chosen when the Capture is created and cannot be changed afterwards.
Getting started
Before you send a test lead:
Finish setting up the Capture, including the fields, the partner under Affiliates, any Acceptance Rules and deduplication rules, and your Destinations.
Tell anyone who works from your CRM or receives notifications that test leads are coming, if they will reach those systems.
To test the connection:
Prepare test data that is clearly identifiable as a test, for example "Test" as the first name.
Use an email address that has not been used in a lead before. If the email has been seen recently, Driftrock may treat the lead as a duplicate.
Include every field marked as Required on the Capture, and use values the Capture accepts, such as vehicle model names from your vehicle list.
Send the test lead using one of the methods above.
If you sent it through the API, check the response. A 422 response means a required field was missing or a value was not accepted, and the message explains which one.
Go to Your Captures, open the Capture and confirm the lead has arrived.
Check that each field has been mapped correctly and that the lead is tagged with the partner's name as the Source or Campaign value.
Check your CRM or other Destination to confirm the lead arrived with the correct fields.
If the lead does not appear as expected, open the Rejected tab in Your Captures to see the reason.
What to test
A lead that should be accepted. Confirms the full journey from the partner to your Destination.
A lead for each type of enquiry. If the partner sends more than one kind of lead, such as test drive requests and brochure requests, send a test lead for each.
A lead that should be rejected. For example, one missing a required field or failing an Acceptance Rule. This confirms your rules are working and shows the partner what a rejection looks like.
Tips
Use a new email address for each test lead, so earlier test leads are not counted as duplicates of later ones.
Make test leads easy to recognise in your CRM and reporting, so they can be found and excluded later.
If you change the Capture's mapping or rules, send another test lead to check the change.
Ask the partner to send their test leads from the same system they will use for live leads, rather than a separate test tool, so you are testing the real integration.
Send a test lead from each partner, not just the first one, as each partner uses their own API key and Affiliate ID.t leads
