I currently sell custom generated leads to several companies that require integration with their system using posting codes. I would like to get a couple quotes on setting up this integration.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased.
Here is how it needs to work and an example of programming script is below. (sorry if it is more info than you need)
we would generate traffic to a webpage with a form like this
<[url removed, login to view]>
when the lead fills out the form and clicks the submit button I would need to do a realtime upload using the following script.
Our custom landing page is:
[url removed, login to view]
When someone fills out their form, they will post the data to this page. This page will echo back the required information that need (in particular, the new_member_id. They will then refer to this page:
[url removed, login to view]<EnrollerId>/[url removed, login to view]<new_member_id>
One part of this custom page is <EnrollerId>. I need to know for sure if they can handle this or not (they have EnrollerId, and if not, I can echo it back). This is the sponsor, the one paying for the guaranteed tours.
Spec sheet for the Guaranteed Tours link that we set up
based on EXI's specs that others are also using.
1. EXI Requirements
2. HTTP Request Data Structure
3. Expected HTTP Response
4. Dynamic Url for new preenrollee landing page
1. URL of a custom lead insertion processing page hosted by your web site
2. List of countries supported by your company. EXI Country List
3. Databasing of TransactionId for each EXI lead.
4. Dynamic Url for new preenrollee landing page.
EXI will post lead data to the custom URL with the following parameters:
The previous are defined as follows:
FirstName: Lead first name, 60 char max.
LastName: Lead Last name, 60 char max.
Phone: Lead Phone number, numbers only no other formatting characters.
May contain more than 10 digits if outside the USA 30 char max.
Email: Lead email, 60 char max.
Country: Lead Home Country, see attached country list for possible values.
EnrollerId: Identification value for the lead Sponsor/Enroller. 60 char max.
LeadProvider: Identifier for E.X.I, value = "EXI"
TransactionId: Unique Identifier for current transaction. All Members in your database must retain their original TransactionId.
IpAddress: This is the I.P. address that the client signed up from.
Note: All data will have leading and trailing spaces removed.
Expected HTTP Response
The custom processing page should return the following information as text only and should not use any HTML tags.
Case #1 (Success)
Successful lead insertion into database.
Case #2 (Duplicate)
Email already exists in database and has not been purged.
Note: TransactionId is the id of the original transaction that placed the lead.
If the lead was not place by EXI this number will be blank.
Case #3 (BadData)
Passed data does not meet requirements.
Case #4 (InvalidEnroller)
Enroller Id does not exist.
Case #5 (Disabled Account)
Enroller exists but account is currently disabled.
Case #6 (Profanity)
Post Data fails Profanity check.
Case #7 (Unknown)
Unknow or undefined status, All Datachecks should default to this value.
Dynamic Url for new preenrollee landing page
This is the url to redirect the new preenrollee to for a free tour or to view their new site. An example would be:
[[url removed, login to view]]<NewMemberNumber>
Where <NewMemberNumber> is generated by our system.
Also because the enroller id’s change daily with new orders…is there a simpler way to program it such as just having a part of the program where I would input something like this ?
Enroller ID # to deliver
something like that and then the program will know that once enroller id 10789 has gotten their 50 it goes on to filling the order for enroller id 10242