The tracking we provide in our dashboard are verified visitors sent to your site. The way we do this is by sending traffic to a unique internal URL which tracks each individual visitor and then forwards them to your site. This way we can track the referrer, location, and IP of each visitor sent to your website. But this does not guarantee that the visitor stays on your page long enough for it to load or fire tracking codes.

To find track your visitors in our dashboard just visit:

Then find the Subscription you would like to update, and click on Details

You will then be taken to your Subscriptions page. Scroll down to the bottom to find your subscriptions tracking.

You can also click on the Referrers button or Countries button to change the panel on the right.

Countries - Shows which countries your visitors came from.

Referrers - Shows which websites forwarded visitors to yours.

Common issues using Google Analytics

Often your own onpage tracking such as Google Analytics may show less visitors than our dashboard. This is because our dashboard is tracking everyone who is sent to your website, where as Google Analytics is only showing everyone who loads and triggers your tracking code. This can be a problem if your tracking code only loads and fires after everything else on your website, and it's even worse if your website takes a long time to load.

Here are some steps to ensure your Google Analytics can track all the visitors we send you:

Correct Google Analytics Code Installation

You should always have your Google Analytics code installed in between the <head></head> tags of your webpages html, and before any other javascript or stylesheets are loaded. This will ensure it is the first thing loaded and that it does not have to wait until everything else on your page is loaded.

This practice is also recommended by Google:

Often the tracking code is installed at the end of the <body> tags which means it's only ever loaded and fired after the entire webpage is loaded. This means that visitors who leave your website before the entire page is loaded will not be accounted for in Google Analytics.

But it is better to have it at the top of the head tags so that it is the first thing loaded. This won't slow down your websites loading speed because the Google Analytics code does not prevent other things from loading at the same time, it's asynchronous.

Website Loading Speed

To prevent people from leaving your website before your Google Analytics code is triggered you should make sure that your website loads fast. 

It's especially important to have a fast server response time. The response time is how long it takes your server to start sending the webpage to the visitors browser. It's also known as the "time till first byte" (TTFB).

If your server takes a long time to start sending a webpage to your visitor they may leave before even having the chance to load your Google Analytics tracking.

A great gauge of your websites loading speed is Google PageSpeed. You can see how long your website takes to load on both mobile, and desktop devices. If your Google PageSpeed Score is less than 90 on either mobile or desktop then you may be losing a lot of your traffic due to slow loading times.

If your Server Response Time / Time Till First Byte (TTFB) is longer than 600 ms then you could lose a lot of visitors due to slow server response times.

To improve your loading and response times you can just implement the recommendations that Google PageSpeed offers for your website. But in general it's also helps a lot to use a Content Delivery Network (CDN) like Cloud Flare to speed up server response times, and optimize your website and content for faster loading times.

Content Delivery Network (CDN) Reporting

If you use a CDN like CloudFlare then you can accurately report for the amount of requests (files loaded) and unique visitors your website receives. 

This reporting is usually more accurate than Google Analytics because it does not require the visitor to load anything.

On CloudFlare you can find this on both the Dashboard, and in Analytics.

Server Reporting

If your server response time is fast then you should be able to find all of the visitors we send you in your Server Logs or Sever Analytics. But if you use a CDN these logs will not be accurate because the CDN will deliver your website requests rather than your server directly. In that case you should check the CDN analytics.

If your web host provides you with access to cPanel then you can track your visitors in the Analog Stats.

Google Analytics Reporting

The most common problem when using Google Analytics is looking at the wrong reports or dates when trying to track our visitors.

Default Google Analytics Tracking

When you check Google Analytics you should always make sure you are reporting for the correct dates, and that you are checking a report that includes visitors we send you.

By default Google Analytics identifies our traffic as a mixture of Referral traffic and Direct traffic. In reality all the traffic you receive from us is referral (aka forwarded) traffic, but if Google Analytics is not able to identify where the visitor is coming from it counts the visitor as direct, which is where all unidentified traffic is located.

So you can find our traffic split between two reports:
Acquisition -> All Traffic ->  Referrals
Acquisition -> All Traffic -> Source/Medium -> (direct) / (none)

Google Analytics Tracking with UTM parameters

To make tracking easy you have the option on our signup form to add UTM parameters to your URL. If this was selected when signing up then you should be able to find all of the traffic we sent you under one single report:
Acquisition -> Campaigns -> All Traffic ->  SimpleTraffic

If you did not choose to add UTM parameters to your URL just contact us and we can add it for you.

Did this answer your question?