Tracking Organic, SMS and Social Visitors
This document will guide you how to implement tracking to your organic sources to identify where your leads originate from.
This option to track using manual source parameters is very useful when we want to track specific links or pages.
To track any organic source simply add a manual source-link parameter with ?el= followed by the name of the source you would like to track to the end of a URL.
HYROS will then create a source based on the name you used in that parameter and begin attributing clicks and sales to it.
For example:
To track specific traffic sources just change the text that comes after “=”
For example www.hyros.com?el=pinterestpost1. This will create a source automatically named “@pinterestpost1”.
For example, if you create 3 sources using this method such as “pinterestpost1”, “pinterestpost2” and “pinterestpost3” then when you load up a report you will be able to see how much traffic is coming in via each post. This can be useful for tracking the performance of individual links and pages.
Organizing Your Sources
We also recommend using our extra UTM parameters to automatically allow you to add these new organic sources into specific traffic sources, inside of Hyros.
Although this is an optional step, it allows you to better organize and segment your data later based on this information, without having to manually adjust any sources later.
To do this, simply add the following UTM parameter at the end of ?el=yoursource, separated by an & symbol:
htrafficsource=yourtrafficsourcename
So in an example where we are tracking three separate Pinterest links, instead of just using ?el=pinterestpost1, then ?el=pinterestpost2 etc, we would instead use the following UTM parameters for each link:
www.mysite.com?el=pinterestpost1&htrafficsource=pinterest
www.mysite.com?el=pinterestpost2&htrafficsource=pinterest
www.mysite.com?el=pinterestpost3&htrafficsource=pinterest
As you can see, although in this case we are creating 3 different sources by changing the name slightly after el=, we are including them within the same traffic source, which will allow us to group them together by traffic source in the reports later in a more automated way.
For more details on some specific setups, follow the use case examples below.
