|
|
 |
 |
|
|
 |
|
 |
|
|
|
| |
|
LeadQ Tracker SDK |
|
|
|
|
LeadQ Tracking principals
The LeadQ - leadtracking software is a client –server application. The LeadTracker SDK is consists of a set lightweight libraries which can easily be implemented at any website. This client takes care of logging the campaign and user information and the passing on to the SOAP service endpoint.
There are several implementations of this client: PHP, Java and .not, so 99% of the webhosting platforms is supported. The client SDK’s are open sourced, just to give our users the insurance no malicious code is implemented on their servers.
Being open sourced, it is easy to customize the client SDK, just as long as you use the proper SOAP SDK endpoint to post the leads.
LeadQ Tracking SDK explained
Every SDK has two objects that can be posted into the SOAP endpoint: Session and Lead.
The soap endpoint contains two methods:
- UpdateSessions (Session session);
- UpdateLead(Lead lead);
Both classes, Lead and Sessions are lightweight property holders (plain old objects).
Coming up next is a definition of the classes and their properties.
| |
|
|
Session Object
The Session object is used to keep track of basic sessiondata. A Session object will be stored in LeadQ, regardless the fact whether the session results in a lead or not. In this way its possible to keep track of a web-form visitor count.
New Session
The first hit on a webpage results in a new Session object to be posted in the Leadtrackers endpoint. The sessionId = left blank, the response will contain the sessionId to be used for updateinformation.
Existing Session
If this SessionId is known to LeadQ, and is in line with the campaign and formId, the post is used to update the existing data, and the response will contain information about the excising Session.
Lead Object
The lead object holds the basic “NAWT” properties of a lead, some extra fields and 2 ntext properties for additional data; the leadMemo field is used to add information about the lead in a human readable manner, like “Has male dog named goofy”. The leadXmlData property is able to store software-readable data in the form of xml like “goofy”. The xml-schema should be discussed with the party responsible for contacting the leads, in order to keep the string compatible with their software.
Lead info update
Whenever a leads fills out at least his or her leadLastName, the lead can be posted into the LeadTracker. To be sure that the lead - information is linked to the associated session -information, a sessionId is obliged when posting a lead in the sessions endpoint.
Return Object
The return object is either a Session object or a Lead object, depending on the posted object.
The return object is acomplished with extra data like:
- posting result code
- posting result message
- updated lead or session data
- supplier strings (like supplier pixels)
|
|
|
|
|
|
|
|
|
 |
 |
|
|
 |
|
|
|
|
|