233417 Post leads to platform in XML

Summary of Project: We send traffic to an auto site and collect auto loan leads. The leads are then sold on an auction platform known as (DTX). Objective is to capture the information entered by our users and then communicate with DTX to POST the lead to them in XML format. Additionally create an admin tool which will be an interface for us to get reporting on leads and perform various actions. Additional Documentation: Document that details the service will be provided when work begins. It includes examples for posting the lead and getting a response. It consists of only of 1 call and 1 response. The document below will explain the various elements that will need to be posted and the response received. Website: [login to view URL] Form Design – This page is designed but will need some modifications. Will give instructions on this once programmer is selected. It requires making the form friendly (AJAX - Web 2.0) and validation. Form Posting - Workflow after information is completed: 1. Save the form to mysql db. For each lead store additional info: ip address, referrer_id, timestamp, browser type, any other relevant and useful information you can add on the lead level. 2. Post the information to (DTX). For each lead you send to the platform you will get one response. The communication happens with an XML request and the specification is attached. Details below: 3. Instructions for posting the lead using SELLGX_REQUEST: Parameters for SELLGX_Request (see additional documentation): • DTX_GEN_ID - unique constant number assigned by the DTX: ***** • LEAD_GEN_METHOD - SEARCH_PAID (won't change) • LEAD_SOURCE_IP - IP Address of user • CAMPAIGN_ID* - We will be separating out campaigns by sending traffic to a different directory. The campaign id should be the directory name. We're not doing it with parameters in the URL as we'll be changing various aspects of the landing page and form to do A/B testing to optimize conversion. For example if traffic is going to: [login to view URL], campaign_id=camp1 • GEN_LEAD_ID* - Auto Generated Number starting at 1 • SELF_GENERATED_LEAD – FALSE (won't change) • GEN_DATA - none at this point – optional so don't include • MINIMUM_PRICE* - We're going to have 2 tables that dictate this price. i. Table 1 - ZIP and Price - Look up zip of lead and if found use the price value. If zip isn't there look up table 2 ii. Table 2 - State and Price - We'll have a price for each state. • Lead_Data - elements here are self explanatory. Elements within this node come from the captured form. Mostly information from the captured lead except for: • FORWARD_APPLICATION - always true • SPECIAL_OFFERS - always false *Store this information for every lead in mysql as well. 4. Wait for response, which should take 30 – 40 seconds. A lead may be resubmitted more than once (more on this later). All details of each transaction should be stored per lead. SELLGX_RESPONSE is what DTX will return in XML and is documented in the attached document as well. Elements to be stored: • DTX_LEAD_ID - unique id assigned for each post to them • SUCCESS - If true still store true for this field but mark the lead as SOLD. • CACHED_RESPONSE - if True is returned there will be an action for the REASON element (more on this below) • BUYER_DTX_ID • PRICE • RESERVATION_ID • REASON - exists only if false. Based on code returned different actions need to be taken. First phase will be to allow for manual actions to take place such as resubmit, etc. to be facilitated by the admin tool. • REASON_MESSAGE • ERROR 5. Store transaction history for each lead to be displayed later in the admin tool: • timestamp when lead is posted • timestamp when lead response takes place • each time the lead was resubmitted • all the response elements - i.e. reason it was rejected • # of times it took the lead to sell • Additional field which shows the lead as SOLD or UNSOLD. • During the exchange of information with DTX, other errors could occur which should be documented and mark the lead as UNSOLD. Errors such as timeouts, server error, code related errors that didn't allow the transaction to go through, anything else that you think is bound to happen. Admin Tool - Allow us to see every lead and filter for every available column for each lead There should be three separate pages/views that separate the way leads can be viewed: Leads Sold, Leads Unsold and Archive. Leads sold • Date – Show and allow to modify the date range at the top of the page – show today by default • Metrics to show based on date: o Total Amount of Leads sold o Total Price of leads - Add up all solds leads for the selected date • Below this we should see the listing of the leads in that date range. • Column Headings: Date Sold, FirstName, LastName, Social, Zip, State, Price, Campaign_ID, Lead_ID • All the columns should be sortable. • We should be able to filter by any column. For example I may want to see all leads where Price > 10.00. Perhaps a small form that lets you input parameters to filter the view. • Each lead should have a link on the (lastname) which should open up all the data available on that lead as well as any transaction history (popup window or layover, etc). Leads Unsold • Date – Show and allow to modify the date range at the top of the page – show today by default • Display the full listing of leads that have been marked unsold. This should be for all available leads unsold in the db unless they're archived(more below). • Column Headings: FirstName, LastName, Social, Zip, State, Price, Campaign_ID, Lead_ID, MINIMUM_PRICE(from SELLGX_REQUEST), REASON(from SELLGX_RESPONSE), REASON_MESSAGE, ERROR • All the columns should be sortable. • We should be able to filter the view by any column. For example I may want to see all leads where Price > 10.00. Perhaps a small form that lets you input parameters to filter the view. • Each lead should have a link on the (lastname) which should open up all the data available on that lead as well as any transaction history (popup window or layover, etc). • There are certain actions we would like to perform on the leads: o Modify - Bring up form that allows us to modify the form information as first collected from our lead form and save it. o Resubmit - Selecting this option will bring up a window that lets us select the # of hours and hitting "Resubmit" will resubmit this form in the time specified o Archive - This will set some flag in the db to archive and remove the lead from the "Leads Unsold" view One way this can be done: There should be a checkbox next to each lead and 3 buttons below the lead listing to perform the various actions. This should work for resubmit and archive. Throw error if Modify is requested if more than 1 is selected. This will allow me to resubmit or archive multiple leads at a time. * Allow for bulk selection with (select all/unselect all) links. *** In this phase the resubmit processs is manual. On the next revision we want to add rules to resubmit automatically based on the REASON field returned by SELLGX_RESPONSE. (I.E. IF REASON=NO_COVERAGE, resubmit in 12 hours or something similar) Keep that in mind when you program this so it's easy to add it later. This will probably happen a few weeks after this initial phase is completed. Archive • Date – Show and allow to modify the date range at the top of the page – show today by default • Display the full listing of leads that have been marked to archive • Column Headings: FirstName, LastName, Social, Zip, State, Price, Campaign_ID, Lead_ID, MINIMUM_PRICE(from SELLGX_REQUEST), REASON(from SELLGX_RESPONSE) • Each lead should have a link on the (lastname) which should open up all the data available on that lead as well as any transaction history (popup window or layover, etc). • We should be able to filter the view by any column. For example I may want to see all leads where Price > 10.00. Perhaps a small form that lets you input parameters to filter the view. • Allow selecting leads via checkboxes and button to un-archive them. If this happens, they should show up back on the Leads Unsold page. Analytics Separate view on the admin tool that we'll build up as time comes. For now we have 1 feature we'd like to see. How often people abandon the form page. Mainly if they hit submit and validation kicks in which keeps them on the form, count how many of those people leave without getting past the form. This would tell us if the form is bad.