Transfer Data from LeadsHook to LeadByte - 🎥


Leads Hooks is an awesome system that enables you to build journeys using decision trees. This article outlines the steps you need to take to submit registration data from Leads Hook to LeadByte, covering the following:

- Posting data from LeadsHook to LeadByte
- How to track what channels your leads came from
- How to post data to LeadByte, get the Buyer details and redirect to a custom page

To successfully post data to LeadByte you will need to ensure the following is done:

1. You create a REST API key in LeadByte for LeadsHook (this will allow you to create a lead)
You do this here: Admin > Tech Hub > REST API.  Below is a video showing you how


2. You have created your LeadByte campaign and added any custom fields you need to store

3. You are able to create a webhook node in LeadsHook (this is how data is sent to LeadByte)

How is data transferred from Leads Hook to LeadByte?
Lead data is transferred from LeadsHook via a webhook node.  The method is POST and the body is JSON within LeadsHook.  See image below (from leadshook).


How do I generate the posting instructions from LeadByte?

You need to generate an integration guide for the LeadByte campaign you want to submit data into from LeadsHook.  Here is a video (below) on how to do that.  


This is an example of what the POST URL will look like:

This is an example of what the payload body will look like:
"campid": "TEST",
"email": "{email}",
"firstname": "{first_name}",
"lastname": "{last_name}",
"postcode": "{postcode}",
"phone1": "{phone}"

Remember to add your REST API Key as a header:

What happens if I get an error when posting a lead?
You will need to troubleshoot this.  The most common reasons for it not working as:

1. Your LeadByte REST API key in disabled or doesn't have the CREATE permission
2. You are not using the correct Request URL or Method
3. You are not using JSON or the JSON is invalid (example below, invalid use of comma)

Key Steps / Points (MUST READ)

1. For any answer that you want to post to LeadByte, you must create this as a Custom Field in Leads Hook unless it is a standard field.  Further reading about Custom Fields here.

2. To submit data from Leads Hook to LeadByte you need to add the Web Hook node in your decision tree.  Typically this is added at the end of the journey, but before the Thank You page.  It is the Web Hook that submits the data to LeadByte.

3. The JSON payload must contain the correct Leads Hook tags to be mapped to the correct LeadByte campaign fields.  See image below.  If this is not done correctly, it will not work.

4. Use the "Test Request" function in Leads Hook to check that data is being submitted correctly to LeadByte.  If it is successful, you will get a Status Code 200 response.

5. To check the lead has been created in LeadByte you need to go to the Leads screen.  If it is not there, check the system rejections.  If it is in system rejections, you will be given a reason why it has been rejected i.e. "email address is a required field"

Leads Hook Explainer Video - How to configure your decision tree and web hook 

This shows you have to configure your Decision Tree to post leads to LeadByte using a WebHook Node in LeadsHook.

Tracking what channel my leads came from
In LeadByte we have the concept of SID (supplier ID).  This can be used to associate leads to a specific Supplier (affiliate, source, channel i.e. Facebook, Google, YouTube).  Please watch the video below on how to do this.  Alternatively you can use your default SID which is the value "1" and use SSID's to submit your channel.  This is what we would recommend for ease!

Submit a lead and redirect to a page / node based on where the lead was sold
In the below video you can see this in action.  Essentially, you are (a) making a request to LeadByte, (b) storing the response the LeadsHook custom fields then (c) using a decision node to redirect to a page / results node.

For this to work you will need ensure the following is in play:
- You have an Administrator REST API Key
- Your REST API Key has all buyer data options selected in the API queue settings
- You Authorise your REST API key in LeadByte to allow the request from LeadsHook

Processing Times - what affects the speed of a response in a Buyer Delivery Accept environment

Speed is key especially if you are keeping the customer on screen.

The speed at which a supplier gets back a response on whether a lead has been sold or not depends on two factors:

1. Whether your account is on shared LeadByte resources (as opposed to dedicated processing)
2. How long it takes to get back a sold lead from your Buyer's system

If you need dedicated processing, this will require you to upgrade. You can speak to support about your options.  Pricing is subject to volumes.

Was this article helpful?
0 out of 0 found this helpful