- 26 Nov 2024
- 1 Minute to read
- DarkLight
Call Verification Workflow
- Updated on 26 Nov 2024
- 1 Minute to read
- DarkLight
Summary
Standardized LeadiD implementations are critical for ensuring that the data being evaluated is consistent across the entire creator network. This article addresses the implementation for leads created in a web form experience and call verified in a call center before being provided to the call buyer.
Standard Implementation
In a call verification implementation, the LeadiD token for the event will be created on the website where the consumer provides their information.
This LeadiD should be propagated through each page of the user experience on the site.
Once the lead is submitted, the same LeadiD should be passed into the call center form and should be set in the leadid_token hidden input field within the call center form prior to firing the LeadiD campaign javascript on that page.
The LeadiD should then be propagated through each page of the call center verification form.
The entire lead event will have one LeadiD associated and will be posted to the buyer with the lead data.
Once implemented, follow the steps in the Campaign Implementation Self Test to verify the implementation is working as expected.