Wordpress PHP tweaking: Affiliate Tracking

Dibatalkan Disiarkan May 23, 2012 Dibayar semasa penghantaran
Dibatalkan Dibayar semasa penghantaran

We're an Internet Marketing company - specializing in online trading platforms - currently looking for a PHP programmer with extensive WordPress experience to help us develop a script that tracks where users are coming from (parse keywords from search engines, parse tracking codes from URL's etc). Work includes developing the code, debugging it and guaranteeing 100% functionality, as per our specifications (attached below). We are looking for long-term partnership. This is a test project and will help us determine which developers to continue working with in the future. =====================================================

## Deliverables

** File with identical text is attached in PDF format for easier reading. Tracking System Enhancement Project Purpose Enable tracking of specific users' origins (where the came from), relaying the data from a unique tracking link OR a search-engine keyword, to the "Link Cloaker" Wordpress module. Explanation Currently we use "Link Cloaker" module to track outgoing clicks from our websites to specific merchants. Link to module page: [url removed, login to view] Each merchant has 1 or more predefined links (e.g. [url removed, login to view]) which contains a unique trackable URL that is associated with our company's activities. A LinkCloaker module URL is typically relayed from the above URL (../goto_merchants/merchant_label) to the merchant URL, e.g.: [url removed, login to view] whereas 1100 is our company's unique code. For some merchants, we have the option of inserting a second parameter (henceforth called a "tag") in the URL, e.g. [url removed, login to view]?tag=ABCDEF whereas ABCDEF represents a source of traffic that only we know about (a certain landing page,referring website etc). We use the string "[ref]" in our LinkCloaker module destination links, whenever we want to automatically assign a value to the TAG field. (The "automatic" algorithm is described below) It looks like this: LinkCloaker link: [url removed, login to view] Redirecting to: [url removed, login to view][ref] Assigning a value to [ref] is made as follows: [ref] Algorithm There are two types of values that can be assigned instead of the [ref] strings in the LinkCloaker module: 1. URL Parsing of a referring tag (if tag was specified in the URL). e.g. [url removed, login to view] - (the tag is "NAME". Therefore, [ref] is replaced by the string NAME) 2. Capturing a search-keyword from the HTML header (if referring website is a search engine). E.g. a user searched for "trading online" in Google, and clicked on our URL from the search results. The keyword ("trading online") is passed via the HTML header when Google links to our site. [ref] is now replaced with trading online. Logic: If ?ref tag is exists in OurWordPressSite URL, assign its value to [ref] ELSE (if does not exist) Search for search engine keyword (usually available as ?q= or ?y= in the search engine's result page). If keyword parameter exists, assign its value to [ref] ELSE assign value="NONE" to [ref] Therefore, upon invoking the [ref] string from the LinkCloaker module, it is replaced by one of three values: 1. ?ref= value, parsed from the referring URL to OurWordPressSite. (1st priority) 2. The keyword which the user searched on Google or Yahoo, and clicked on OurWordPressSite URL. (2nd priority) 3. "NONE" string, if none of the above were found. (3rd and least desirable priority. Ideally used only when traffic is not tracked with ?ref= or user didn't come from a search engine) (* NONE represents a default value that is assigned to [ref] if no other value can be assigned to it, and represents direct access to OurWordPressSite URL (user typing the domain name in the browser address bar- [url removed, login to view]) Examples Here are some example flows: (OurWordPressSite = [url removed, login to view]) 1. User clicks on OUR banner advertisement on a 3rd party website: The banner links to [url removed, login to view] 2. User clicks on a link to a merchant, from our site. The anchor text points to: [url removed, login to view] which is being redirected to [url removed, login to view][ref] 3. [ref] is replaced with the ?ref= value and the link redirects to [url removed, login to view] 1. User searches for "trading online" in Google, and sees [url removed, login to view] , ranked 2nd on the results. 2. User clicks on this result and is directed to [url removed, login to view] 3. User clicks on a link to a merchant, on our site. The anchor text points to: [url removed, login to view] which is being redirected to [url removed, login to view][ref] 4. [ref] is replaced by the keyword for which [url removed, login to view] was displayed in Google's results, i.e. "trading online", and the destination url is: [url removed, login to view] (white space is replaced with a + sign to avoid URL errors) • User types in [url removed, login to view] in the address bar of his browser and is forwarded to our homepage. • User clicks on a link to a merchant, on our site. The anchor text points to: [url removed, login to view] which is being redirected to [url removed, login to view][ref] • [ref] is replaced by the default string, "NONE", since no keyword or URL parameter is found. The destination URL is: [url removed, login to view] Appendix A: Additional Remarks • This above functionality is already implemented on various Drupal site that we own. We currently don't have it for our Wordpress sites. • ** NOTE ** PLEASE RESPOND WITH THE WORD "ELEPHANT" IN YOUR BID. This will show me that you read the entire job description. • We can give access to our Drupal sites if necessary. • Winning bidder must provide guarantee to fully debug the project until it is 100% operational for all incoming users, unless we agree to abandon QA at some point after the development is complete. Failure to do so will result in a negative feedback.

Amazon Web Services JavaScript PHP Memasang Skrip Shell Script Kejuruteraan Perisian Ujian Perisian Pengehosan Web Pengurusan Laman Web Ujian Laman Web Wordpress

ID Projek: #2744182

Tentang projek

Projek jarak jauh Aktif Jun 6, 2012