Skip to main content


Sources section display metrics on your various traffic sources. You can use this info to improve your acquisition strategies. This is also a good way to identify new partnership opportunities.

You can click on a source to have the dashboard filtered by users who arrived from that source.

We identify source based on the following dimensions:

By Referrer#

When a user lands on your website from another one, browser set a parameter referrer (document.referrer) which is URL of referring page. GingerTag capture this information to identify the webpages that is sending you traffic.

In the Source section, you can see the list of referrers. For most websites we show the name and logo of the referring websites, otherwise it is just the domain name. When you click on the referrer, you can see the users count from pages within the referring website.

However, in some cases browsers only set the domain name as referrer instead of the full URL.

By UTM Parameters#

GingerTag parse and store all UTM params from the first URL of a session. UTM is a common standard for setting details of traffic source on the URL itself.


If a user comes to your website using the above URL, we parse UTM Source as instagram, UTM Medium as influencer, UTM Campaign as john.

You can view your UTM Sources, UTM Mediums and UTM Campaigns by selecting the respective tabs in the Source section. When you click on a particular item, the dashboard is filtered based on that parameter.

You can use UTM based tracking to accurately measure your marketing efforts. You can measure visitors coming from your social media, influencer campaigns, Youtube channel, etc. by URLs with different UTM params in them.

By ref#

Some websites append a query parameter called ref when redirecting user to other websites. A good example for this is Product Hunt. They add a ?ref=producthunt query parameter when you go to a product's website.

We store the value of ref parameter and you can view them under the ref tab on Sources.

Note that in most cases and also with the Product Hunt example, ref parameter is not relevant as document.referrer is already captured and displayed in the Referrer tab.