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 Post Example
HTTP GET Example
XML Post Example
Please provide your XML schema along with the Lead Post Integration Form, if you are sending an XML post.
Our goal is to provide a fully functioning posting URL. This posting URL is triggered at the lead source (e.g. webform, 3rd party CRM). Once we have received the completed ‘Lead Post Integration Form’ 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 LeadManager in real‐time, and we want that information to populate specific fields in LeadManager.
Here, information submitted in the ‘First Name’ field on our webform should drop into the field called ‘First Name’ within the lead record in LeadManager. The ‘Last Name’ should drop into the LeadManager 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 LeadManager, and so on.
The Lead Post Integration Form allows us to list the specificvariablenamesthat will be posted, along with the corresponding LeadManager field the data should populate. This is called the MappingDefinitions.
Notice the actual variablenames(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 fieldtitleson our form are:
- First Name
- Last Name
- Phone Number
- Your Goal?
- Additional Info
In the example provided, the variablenameswould be:
Finally, the poststringsent to LeadManager would appear like this:
In LeadManager, 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”. LeadManager clients have complete control over creating and titling these campaigns.
If necessary, LeadManager clients may provide a list of these campaigns includingthecorrespondingCampaignId,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: