These instructions describe how leads should be posted to LL Media, LLC's shared campaign and understand what to expect in response.
Ping URL | https://llmedia.leadspediatrack.com/ping.do |
Post URL | https://llmedia.leadspediatrack.com/post.do |
Request Method | POST or GET are supported. We strongly recommend using POST. |
# | Field | Ping Required | Post Required | Data Type | Description |
---|---|---|---|---|---|
1 | lp_campaign_id | Yes | Yes | String | Provided to you by LL Media, LLC |
2 | lp_campaign_key | Yes | Yes | String | Provided to you by LL Media, LLC |
3 | lp_s1 | Yes | Yes | String | Sub Affiliate 1 |
4 | lp_s2 | No | No | String | Sub Affiliate 2 |
5 | lp_s3 | No | No | String | Sub Affiliate 3 |
6 | lp_s4 | No | No | String | Sub Affiliate 4 |
7 | lp_s5 | No | No | String | Sub Affiliate 5 |
8 | lp_test | No | No | String | 1 for Test Post |
9 | lp_response | No | No | String | Response back XML or JSON |
10 | lp_ping_id | No | Yes | String | Returned Ping ID from the Ping Post |
11 | lp_return_dd_matches | No | No | bool | true or false |
12 | lp_return_dd_hash_parameter | Yes | No | string | phone or email |
13 | lp_return_dd_hash_type | Yes | No | string | sha1 or md5 |
14 | lp_num_sold | Yes | No | Number | Number of time the lead has been sold |
15 | first_name | No | No | String | First Name |
16 | last_name | No | No | String | Last Name |
17 | phone_home | No | Yes | US Phone | Phone Home |
18 | address | No | No | US Address | Address |
19 | city | No | No | US City | City |
20 | state | Yes | Yes | US State | State |
21 | zip_code | Yes | Yes | US Zip Code | Zip Code |
22 | email_address | No | No | E-Mail Address | |
23 | ip_address | Yes | Yes | IP | IP Address |
24 | average_utility_bill | Yes | Yes | List | Average Utility Bill |
25 | residence_ownership | Yes | Yes | List | Residence Ownership |
26 | shade | Yes | Yes | List | Shade |
27 | lead_id | No | No | String | Vendor Lead ID 1 |
28 | universal_lead_id | Yes | Yes | String | Universal Lead ID |
29 | utility_company | Yes | Yes | String | Utility Company |
30 | credit_score | No | No | List | Credit Score |
31 | vendor_lead_id | Yes | Yes | String | Vendor Lead ID 2 |
32 | notes_for_installer | No | No | Text | Notes for Installer |
33 | trusted_form | No | No | String | Trusted Form |
34 | trusted_form_Y_N | Yes | No | List | Does this lead have TrustedForm? (Y for Yes and N for No) |
35 | jornaya_Y_N | Yes | No | List | Does this lead have Jornaya? (Y for Yes and N for No) |
To use the Exclusive Directory you must include the xml in the distribution_directives parameter
<distribution_directives> <excludes> <exclude> <parameter>phone</parameter> <hash>sha1</hash> <value>5bcb3745df55b139f734287d59bed53ede160e3d</value> </exclude> <exclude> <parameter>phone</parameter> <hash>sha1</hash> <value>382887879bcf7231478398d4b0bcc20fcf489aa3</value> </exclude> </excludes> <includes> <include> <parameter>phone</parameter> <hash>sha1</hash> <value>605fe0261fa3ab90d32092117c1d75ff8d7b68c3</value> </include> <include> <parameter>phone</parameter> <hash>sha1</hash> <value>4bab5a2b22cbded666d3b00595b3b27a28f287f3</value> </include> </includes> </distribution_directives>
When posting leads, make sure you post the list value.
# | Label | Value |
---|---|---|
1 | $0-99 | $0-99 |
2 | $100-150 | $100-150 |
3 | $151-200 | $151-200 |
4 | $201-300 | $201-300 |
5 | $301+ | $301+ |
6 | $400+ | $400+ |
7 | $500+ | $500+ |
8 | $600+ | $600+ |
9 | $700+ | $700+ |
10 | $800+ | $800+ |
11 | $900+ | $900+ |
# | Label | Value |
---|---|---|
1 | Own | Own |
2 | Rent | Rent |
# | Label | Value |
---|---|---|
1 | A Little Shade | A Little Shade |
2 | A Lot Of Shade | A Lot Of Shade |
3 | No Shade | No Shade |
4 | Uncertain | Uncertain |
# | Label | Value |
---|---|---|
1 | Excellent | Excellent |
2 | Good | Good |
3 | Fair | Fair |
4 | Poor | Poor |
There are multiple ways to post a test lead. You can either post:
When a ping is posted, you will get a real-time response. The default response is in XML format; You can request the response to be JSON if you pass json in lp_response field.
Success |
<response>
<result>success</result> <ping_id>0UTNS5ND</ping_id> <price>15.00</price> <distribution_directives> <includes> <include> <parameter>phone</parameter> <hash>sha1</hash> <value>b56ca1215e5bddf98ebdb88a99bc274f9d0fa1b1</value> </include> </includes> </distribution_directives> <msg>Ping Accepted</msg> </response> |
Failure |
<response>
<result>failed</result> <ping_id>YZDRPBC7</ping_id> <price>0.00</price> <msg>Ping Rejected</msg> <errors> <error>No Match</error> </errors> </response> |
When a lead is posted, you will get a real-time response. The default response is in XML format; You can request the response to be JSON if you pass json in lp_response field.
Success | <response> <result>success</result> <lead_id>0UTNS5ND</lead_id> <price>15.00</price> <redirect_url>http://www.example.com/</redirect_url> <msg>Lead Accepted</msg> </response> |
Failure | <response> <result>failed</result> <lead_id>YZDRPBC7</lead_id> <price>0.00</price> <msg>Lead Rejected</msg> <errors> <error>No Match</error> </errors> </response> |