Transfer Data from LeadsHook to LeadByte

Follow

LeadsHook is an awesome system that enables you to build funnels using decision trees. This article outlines the steps you need to take to submit your LeadsHook registration data into LeadByte.

In this article we will cover:
> Post Lead Data From LeadsHook to LeadByte
> Leads Hook Explainer Video - How to configure your decision tree and web hook
> Key Steps / Points (MUST READ)
> How to post data to LeadByte, get the Buyer details and redirect to a custom page

Post Lead Data From LeadsHook to LeadByte

Create LeadByte REST Admin Key
Once you have created your LeadByte campaign you need to create an API Key.  In LeadByte go to Admin > Tech Hub > REST API.  Select the Administrator key, activate it and select the lead permission CREATE.  Call the key LeadsHook.


LeadsHook Webhook Node

Within LeadsHook you will be using the Webhook node to post data to LeadByte.  You should use a POST method using a JSON body.  See image below on how this should look.

leadshook_payload.jpg


Request URL

This is your Request URL: https://INSERT.leadbyte.co.uk/restapi/v1.3/leads
Replace INSERT with the name of your LeadByte account.

JSON Body

{"campid": "INSERT","sid": "INSERT","ssid": "{ssid}","First_Name": "{first_name}","phone1": "{mobile}"}

You will then need to add a Header.  The Name is x_key and the value is your REST API Key.

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.


 

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"


How to post data to LeadByte, get the Buyer details and redirect to a custom page

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 are using 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
- Your LeadByte campaign is set to Buy/Sell Leads AND is set to Pay Per Delivery Accept
- Your LeadByte campaign has Live Buyer Responses enabled, which can be found under your Campaign Settings Advanced Settings option.

 



FAQ

Q: What happens if I get an error when posting a lead?
A: 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)

 

Q: What impacts the speed of getting back a response when using Live Buyer Responses?
A: The number of Buyers on your panel, the number of rules on your Deliveries, the speed of your Buyers API to respond.

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

Comments