Accessing your Lead Delivery Logs
Updated at: Created at:
This article goes over the "Lead Delivery Logs" which allow you to search for and display the API responses received when sending leads to specific deliveries. This can be used to keep track of how many specific responses were sent back from endpoints, which can be useful for various situations such as wanting to see exactly how many pings are rejected by a delivery.
To access your logs you need to head over to Delivery and select Lead Delivery Logs.
Accessing the delivery logs shows you:
- How many instances of a response were provided
- The Raw response provided by the remote system
This information can be used to fault find or other investigation work. See some examples below:
Lead delivery logs are stored for 6 months.
How can these logs be useful?
If we imagine a scenario where a delivery has been accidentally been misconfigured with the incorrect remote system response - resulting in leads being delivered to a buyer successfully but displaying as unsold on LeadByte.
You can locate which leads have been incorrectly marked as unsold through the Lead Delivery Logs:
Select the timeframe the issue occurred over, the campaign and the deliveries in question.
Make sure you tick "Raw Responses".
The output will display each lead ID and each full raw response received from the buyer API.
You can then export this data with the export to CSV button in the bottom left, then using a spreadsheet managing software, you can isolate each lead that has a success response in the raw response.
Once you have a list of lead IDs that received an success response - you can go to the search lead screen and filter by lead ID IS (PASTE LIST OF IDS).
Then, once your search lead screen only has those leads filtered, you can set the selection to "All Results" and choose the assign buyer action.
Assigning the buyer in this way does not send the lead anywhere again, it simply updates the system to show that the lead is marked as sold to the buyer you choose.
Comments