Lead Source Integration - Velocify Support Portal

advertisement
Lead Source Integration
Posting Real-Time Data to Velocify
This guide outlines the process for establishing a new data post to Velocify
Overview
Velocify is able to receive real-time, direct posts of data from sources such as custom websites, landing
pages, 3rd party systems, etc. This standard integration is done via an HTTP Post, HTTP GET or XML Post.
HTTP POST is the most common request method supported by the HTTP protocol used by the World
Wide Web. The POST request method is used when the client (computer) needs to send data to the
server as part of a request (for example, on submitting a completed form). Additional help and
resources about HTTP POST can be found online. Here are some links:
http://en.wikipedia.org/wiki/POST_(HTTP)
http://www.w3schools.com/TAGS/att_form_method.asp
http://www.w3schools.com/TAGS/tryit.asp?filename=tryhtml_form_method_post
HTTP Post Example
HTTP GET Example
<html>
<body>
<form action="https://secure.Velocify.com/Import.aspx" method="GET">
<input type="hidden" name="Provider" value="YourLeadSource">
<input type="hidden" name="Client" value="L360">
<input type="hidden" name="CampaignId" value="1027">
Fname: <input type="text" name="fname" value="John"><br>
Lname: <input type="text" name="lname" value="Smith"><br>
Phone: <input type="text" name="homephone" value="31076573703"><br>
Email: <input type="text" name="emailaddy" value="support@Velocify.com"><br>
BorrowerGoal: <input type="text" name="BorrowerGoal" value="ShortSale"><br>
AddInfo: <input type="text" name="AddInfo" value=""><br>
<input type="submit">
</form>
</body>
</html>
XML Post Example
Please provide your XML schema along with the Integration Form, if you are sending an XML post.
Getting Started
Our goal is to provide a fully functioning posting URL. This posting URL is triggered at the lead source
(e.g. webform, 3rd part CRM). Once we have received the completed ‘Velocify Lead Source Integration
Form’ (attached) we can provide you a posting URL.
Although we attempt to complete this work as quickly as possible, because of a number of factors we
can at no point guarantee that a particular posting integration can be completed by a specific date.
Please note that a fully completed and tested integration may take up to five (5) business days from
receiving the necessary information. However, most posts are live sooner.
Lead Post Integration Form
The Lead Post Integration Form is available on the Velocify Support Portal. It is designed to collect all
necessary information to create a posting URL. This includes:
1) Establishing the posting method (HTTP Post, HTTP GET or XML Post).
2) Obtaining a list of the data (variables) to be sent to Velocify, mapped to the Velocify fields that
data should populate.
Let’s work through an example:
We want information submitted on a webform posted directly to Velocify in real-time, and we want that
information to populate specific fields in Velocify.
Here, information submitted in the ‘First Name’ field on our webform should drop into the field called
‘First Name’ within the lead record in Velocify. The ‘Last Name’ should drop into the Velocify field ‘Last
Name’. Information submitted in the “Your Goal?” field on our webform should drop into the field titled
“Customer Goal’ within the lead record in Velocify, and so on.
The Lead Post Integration Form allows us to list the specific variable names that will be posted, along
with the corresponding Velocify field the data should populate. This is called the Mapping Definitions.
Notice the actual variable names (listed in the first column) will likely be different then the visible field
title on the webform. Highlighted below are both the names of the fields as they appear to a user on
the example webform and the variable names, which would appear in the HTTP post.
In the example provided, the field titles on our form are:
First Name
Last Name
Phone Number
Email
Your Goal?
Additional Info
In the example provided, the variable names would be:
FirstName
LastName
HomePhone
Email
BorrowerGoal
AddInfo
Finally, the post string sent to Velocify would appear like this:
FirstName=Velocify&LastName=Test&HomePhone=3107657370&Email=support%40Velocify.
com&BorrowerGoal=Debt+Repair&AddInfo=Please+send+me+more+info
Velocify Campaigns
In Velocify, clients create something like folders or ‘buckets’ to organize leads from various sources.
They might be thought of like folders within an email inbox – where emails from different recipients
would be routed into different folders. We call these folders “Campaigns”. Velocify clients have
complete control over creating and titling these campaigns.
If necessary, Velocify clients may provide a list of these campaigns including the corresponding
Campaign Id, along with instructions on what leads should be routed to a particular campaign:
For example, “All leads routed to our webpage via Pay-per-Click should be posted to the campaign called
‘Main Webpage – PPC, Campaign ID 1025”
Finally, lead posts can be ‘routed’ to any campaign by using the correct posting URL, for example:
https://secure.Velocify.com/Import.aspx?Provider=LSource&Client=L360&CampaignId=31  post leads to the ‘Website –
Banner 1’
https://secure.Velocify.com/Import.aspx?Provider=LSource&Client=L360&CampaignId=32  post leads to the ‘Website –
Banner 2’
https://secure.Velocify.com/Import.aspx?Provider=LSource&Client=L360&CampaignId=33  post leads to the ‘Website –
Quick App’
Tuesday, February 9, 2016
Download