I give each visitor who signs up to my Google Form an unique url to my landing page for them to share with their friends. The idea is the more they share and their friends visits the site through their given unique url, I'll move them up the waiting list for a product launch.
So for each visitor I gave them example.com/?ref=uniqueCode which is unique to each visitor. Currently I'm using Google App scripts to programatically generate individual url to each visitor who signs up my Google Form.
The goal is if I see traffic coming in from eg: example.com/?ref=a, and I know tag a belongs to John Doe, I'll move John Doe up the waiting list.
Tried googling for a solution but couldn't find any. All solution directs me to creating a particular campaign in Google Analytics with the URL building which really isn't the right solution for this purpose.
How do I set this up with Google Analytics and track the incoming traffic for each unique code of the ref tags of each user?
Going over your question I cannot see why URL builder does not fit your needs.
However, when it comes to immediate and accurate statistics of incoming referrals you may also use a server side script to track incoming visitors.
Also for lots of existing CMS there are plugins to track referrals. If you use a CMS please update your question.
Related
Pls apologize if I'm not clear enough, i'll try to be as concise as possible.
I'm working on a a company that created it's own competitors, each has it own website, all share the same GA through GTM. Cross-domain tracking is implemented and working.
I want to know if users do actually visit these different sites, which is very likely because there is a lot of research before buying what this company offers.
I understand User Id's will not do the trick because I want to track them before visitors identify themselves through a form. There's no login.
Initially I thought I'll be able to create a segment to narrow down to users with more than one of this company's domains in their history, but that is not working. Should that do the trick?
Thanks.
In the view that get all data you have to create a segment to show users that visited first and second domain. If it is greater than 0 means the cross domain is set correctly.
For good implementation see Troubleshooting Cross-Domain Tracking in Google Analytics: https://www.google.com/amp/s/www.simoahava.com/amp/analytics/troubleshooting-cross-domain-tracking-in-google-analytics/
I'm starting with google analitycs.
Before I'll start implementing this into my pages I'm wondering if I'm able to get informations like average time at site, where my user came from, which devices they are using etc.
I would like to get those information from my VueJS front SPA application by async HTTP GET call and display those there. Is it possible?
If yes I would be very thankful if you provide some links to google API where I can find it or some tutorial.
Since Universal GA you can't access users' origin data outside GA in your application. Before that you had all this juicy information inside a cookie, inside __utma, __utmz etc (more info here).
The information you're asking about (time on site, pages visited, etc) can be retrieved from GA afterwards if you make use of the userid feature.
I've been looking into offline tracking of google analytics goals. I want to implement this in a similar way to how call tracking companies do and I'm guessing the GCLID is the answer.
If I store the GCLID of every visitor that comes to our website in the database alongside some info about their session and then identify their session at a later date as one that produced an offline goal, can I then generate a goal from that?
My thinking is that if I had a button in our CRM system that when I click it opens up an invisible iframe that links to mysite.com/goalurl.html?gclid=xxx then analytics on that page would track a goal on that page but attribute it to the original click that the other user made on our PPC advert. Theoretically I could do this 10 times in a row for 10 different sessions and they would all be tracked as if the 10 original owners of those GCLIDs has visited the goal page, right?
Am i missing something here? Would this not work because Google would spot that they all came from the same IP address, or because I would have the same GA cookie on my machine? Or does Gogole not care about any of that?
Any help would really be appreciated.
I am not sure if it works with the gclid but would also be interested in the answer.
Besides that, a possible solution is to store the Analytics client ID in your own database and, whenever there is a conversion, sending that conversion data (referencing the recorded client ID) directly from your server to Analytics by using the Measurement Protocol.
Exactly this topic is a case study in the book "Google Analytics Breakthrough: From Zero to Business Impact".
There are multiple profiles on my website and each user is managing his/her profile himself. I am trying to find the most efficient way to present analytics of each profile to its owner. Here are 3 ways I found:
Record each and every hit made on a profile page against that profile. This is not just count of hits, this requires to record IP, country, referrer, search terms etc. against each hit. This would require me to manage a huge database as there would be a lot of hits on each page. And a lots of processing on this database. Even if I have to de this, what database is recommended for such use?
Use Google Analytics on each page. But I am not sure that Google Analytics provide an API to fetch Analytics for individual pages.
Use some open source solution like piwik. Again I'm not sure if they provide per page analytics or not.
Please suggest the pros and cons of using each approach.
Update: More explanation - Think of it like a facebook page where each user can see hits on his page. What solution you'd suggest?
For Piwik, you can create a site id for each user, because you are allowed unlimited site ids with Piwik. You can can use a tracker with that user siteid, so when your member logs in, they get data only on their pages. You might also want to look at using custom variables and use the Piwik API to filter data.
Check here for info on multi-tracker: http://piwik.org/docs/javascript-tracking/#toc-multiple-piwik-trackers
I have two websites, website A and website B, the website A is a hotsite that is linked to website B, where the sales happen.
We need to know how the user got the website A and turned into a customer in website B(it means he bought something), so we can mesure the good sources to invest.
as the developer, I have access to these two websites source-code and can implement any google-analytic tag on them.
Thanks,
Jonathan
Web browsers generally send a referrer header, which contains the URL of the page which linked to the current page.
You can access this in the HTTP requests made to site B, and track sessions differently when the first page load is referred by site A. You can also access a document.referrer property in JavaScript, and use it to manipulate your analytics.
The correct way to implement this in Google Analytics is to configure the trackers so that they work cross-domain.
This will allow you to see all the information about where the converting visits originally came from and their path to purchase.
If you don’t use cross-domain tracking or you have it improperly configured, you’ll end up with meaningless data that shows self-referrers in the visit reports and a lack of proper attribution towards your conversion points. As a visitor moves from your primary domain to the other, they will start a brand new session in Google Analytics.
...
If a visitor clicks an ad or performs and organic search and ends up viewing a page on the www.3rdpartycheckout.com after viewing pages on www.primarydomain.com, you lose ALL data about how that user arrived and the complete picture of what they did. If they end up converting, you will only know that they came from www.primarydomain.com (which is not helpful at all).
http://www.blastam.com/blog/index.php/2011/02/google-analytics-cross-domain-tracking/
Have the landing page on website B look at the referrer tag and if its website A then use a separate Google Analytics instance on website B for all sessions that were sourced from website A.