My Click Reports (from Facebook or LinkedIn) do not match my Snoobi Analytics metrics, what can be the cause?
 

Snoobi Analytics is a great tool for understanding about how visitors and organizations use your website.  However, keep in mind that it is not tracking data the same way that log servers or platforms such as LinkedIn track clicks.

Click data is based on ad server logs from the ad exchange(s).
 Analytics data (such as Snoobi Analytics), is based on cookies or page loads.

HOW SNOOBI ANALYTICS TRACKS 'A VISIT’

1. Before a session (visit) is recorded, there are several things that have to happen according to Snoobi
2. When the click from an ad takes place, the browser is pointed to the advertiser’s landing page on their web site.
3. When the browser starts to download the landing page, there may be a request for several files at the same time, including JavaScript, CSS, images, video, audio, etc., including the Snoobi Analytics tracking code.
4. The Snoobi Analytics JavaScript file must first be downloaded and interpreted by the user’s browser.
5. The user’s browser/device and security settings must support: Cookies, JavaScript and Images
6. If any of the above are disabled, Snoobi Analytics may not be able to record a visit.
7. Next, the browser sends a separate request to analytics.snoobi.com or analytics.snoobi.eu, the Snoobi Analytics servers.
8. Then,  a visit is recorded.

There are a number of reasons why ad server click reports and Snoobi Analytics may report different numbers of clicks and sessions:

CLICKS ARE NOT THE SAME AS SESSIONS

Ad servers track clicks, while Snoobi Analytics tracks visits or sessions. If a user clicks on your ad twice within thirty minutes without closing his or her browser, this is registered by Snoobi Analytics as one session, even if the user left your site and then returned shortly after.

For example, if a user clicks on your ad once, clicks the back button, and then clicks your ad again, the ad server registers two clicks while Analytics registers one session. Analytics only counts visitors in a 30 minute window. 

If a user were to click on the ad, go to the site, view the landing page, then repeat the process (perhaps from another page on your site with another ad from the advertiser with the same referral URL) within 30 minutes, Snoobi Analytics will still only count the first referral, but the ad server will have counted 2 clicks.

YOUR LANDING PAGE MIGHT REDIRECT TO A DIFFERENT PAGE

Redirects in landing pages can often keep the Snoobi Analytics code from properly identifying the traffic coming from a specific site.

USERS MIGHT HAVE SET THEIR BROWSER PREFERENCES IN WAYS THAT PREVENT SNOOBI ANALYTICS USED ON WEBSITES FROM COLLECTING DATA

Users entering your website through a click might have JavaScript or images turned off, or might use other technologies preventing Snoobi Analytics from reporting about your website users (such as by installing or setting blocking codes).

SERVER LATENCY

If a user comes to your site from an ad, and then leaves the landing page before the Snoobi Analytics tracking code executes, then the “url parameter” is never passed to the Snoobi servers, and that click is not associated with the session. The result is a clicks vs. sessions discrepancy.

If your Snoobi Analytics tracking code is at the bottom of your web page and placed right above the closing of the body section then you are definitely at risk for reporting discrepancies. And, the bigger and heavier the page the more at risk you are. 

Why is this an issue? Because a person who clicks on your ad and bounces quickly will in all likelihood never trigger the Snoobi Analytics tracking code lying at the bottom of your page code. One simple solution is to place your Snoobi Analytics tracking code near the top of the page to minimize the risk.
 

A VISITOR MAY CLICK YOUR AD MULTIPLE TIMES.

When one person clicks on one advertisement multiple times in the same session, the ad server records multiple clicks while Snoobi Analytics recognizes the separate pageviews as one visit. This is a common behavior among visitors engaging in comparison shopping.

A VISITOR MAY CLICK ON YOUR AD, BUT THEN CHANGE HIS/HER MIND AND PREVENT THE PAGE FROM FULLY LOADING.

This can happen by clicking to another page or by pressing the browser’s stop or back buttons. In this case, Snoobi Analytics won’t register a visit, but the ad server still counts this as a click.

1ST PARTY VS. 3RD PARTY COOKIES

Even among cookie-based tracking solutions, there is a difference between 1st party and 3rd party cookies. Because 3rd party cookies are set by a source other than the website being visited, they’re often blocked by browsers and security software. Snoobi Analytics uses 1st party and 3d party cookies depending on the analytics code setting.

NO SNOOBI ANALYTICS TRACKING CODE ON LANDING PAGE

This might sound like a no-brainer, but it happens too often that a landing page doesn’t contain the Snoobi Analytics tracking code. If this happens, a click is measured, but no visit at all.

YOU EXCLUDED CERTAIN IP-RANGES FROM ANALYTICS

This may also sound like a no-brainer, but if you have disabled to show traffic from certain IP ranges then Snoobi Analytics doesn't register that traffic.