The main point is this. One tracks before the visitor lands on the website, and the other tracks during page load.

77Tool is capable of both methods.

On-click tracking	On-site tracking

Problems with on-site tracking
With on-site tracking, the entry is only recorded after the script has loaded on the page. A number of things can prevent this.

• Browser has scripts blocked. – In this case, a ””noscript”” version of the tracking needs to be in place. This is usually an image tag, and it”’’s highly likely that the browser is not set to ignore images.
• Visitor clicks something on the website and moves away from the page before the script has time to load. Nothing can be done about this. Try to get the script placed at the top of the page code, so it loads before anything clickable.
• Script is not implemented correctly – Typos or incorrectly copy+pastes can lead to complete malfunction of the script. Make sure to test after implementation. Luckily, 77Tool has only a 3 minute wait between entry and reporting of entry in the 77Tool interface. This makes testing easy.
• Script does not have all required information. Our script generally requires a 77tadunit to be available in the source URL. An alternative is to have this value set on the website itself, but without either of these, the entry will land in natural traffic. Website tag is generally implemented in the site code, but is something else which can be stuffed into the source URL.
• Cookies blocked – if the browser does not accept our cookie, entry will be created, but the visitor might not be linked to the conversion, and the conversion will end up in natural traffic. In general, our cookie is able to write to browsers set to ””high”” security and anything below (assuming a higher level exists).

Problems with on-click or redirect tracking
Mostly, on-click tracking is more effective at reporting entries. User clicks on the advert, entry is registered, and only then do they get to the website. Problems still exist..:

• If website is down, entry is still reported, even though visitor never got to the website.
• If the redirect server fails, user never reaches the website.
• Parameters must be correct in the redirect URL, or visitor can end up on the wrong landing page.
• A script or pixel must be called during conversion anyway.

The main issue with on-click tracking is the second point. A strong system needs to be in place in the event of redirect server failure. In 77Agency we have a backup system in place, and a five minute TTL on our DNS records, so we can change redirect servers rapidly.

Why the different methods create discrepancies

Basically, the on-click method will always report higher entries, simply because it has none of the limitations of browser problems loading the on-site script.

This is not just the difference between our own two methods, it should be expected when comparing our on-site tracking with third party on-click systems also.

]]> http://www.karmaengine.com/general/redirect-tracking-versus-client-side-tracking/feed/ 0