I'm working on an app that, according to user feedback, has a high frequency of errors on the login screen. I set up a dashboard in Data Studio to check the volume of users leaving the journey at the login screen and a little later. I can create a segment in Google Analytics to identify how many users accessed the app's Home, how many users made it through the Login screen, and how many successfully ended the journey. Of course, many users "get lost along the way", but I would like to know why these users don't finish the journey and specifically how many abandon the journey due to an app error.
Is there a way to identify the reasons that led a user to abandon a journey inside an app in Google Analytics/Data Studio?
loot at hotjar https://www.hotjar.com/, im not affiliated, a front end dev (also systems admin) just showcased it for us and I really liked it! There are free alternatives, Matomo looked nifty.
It records the users mouse and typing events purely inside your page (no bookmarks or the address box in the browser for example, those are private).
It creates a heat-map for how far people scroll the page, what percent get how far, a heat map for clicks, but also user "stories" following a screen recording of each visitor. including mouse trace, where they seemed to get confused, sometimes you can see people are bored and click on things just for no reason lol. pretty fun! hope it helps
Related
I have a website that sells products and I'm using google analytics to know some statistics about the website. Sometimes, errors happens for various reasons and purchases doesn't go through. You then have to refresh the page and try again, then everything works. The website displays the message telling the user to refresh and try again. I'm curious how many people actually do that. My question is, is it possible to know what users do when this error happens? Do they refresh and try again? Do they close the tab or do they do something else?
The question is quite broad at this moment, but there are a couple of improvements to your measurement setup, that can help you to investigate this customer behavior.
What I would do, is to implement an event tracking to indicate, that this error has occurred. You can find details about event tracking in this guide. Although I suppose, that your users are not likely to enter the website at this page, it might be a good practice to set the non-interaction flag of the event, as it is not actually generated by a user interaction.
I'd also create tracking for page reload, either by creating an other event for this, or by adding -reload suffix to these repeated pageview URLs. You can find good resources for this on SO as well, e.g. this one.
If you have a special URL for this error page (e.g. purchase-error.html instead of purchase-success.html), it is also easy to track the exit rate specific to this page.
Besides of Google Analytics, you might also want to set up heatmap or screen recording tools to understand this behavior. Hotjar, Lucky Orange are a few examples. (No affiliation.)
I have been searching for a solution to this problem for a while and surprised it doesn't exist. I have a low traffic site but a high conversion/acquisition cost per customer.
So when a customer hits a certain page on my website, I want to be notified via SMS. So I can instigate a live chat and get them converting.
I have tried an option with Google Analytics, but that seems to have a delay. The live chat platforms do not seem to have this feature.
How could this type of action be achieved?
David here, from the Zapier Platform team.
That certainly might be possible! I haven't tried anything like that, but I have an idea that might work (albeit with some caveats).
First, you'll want to trigger when someone is on the site. For that, I'd send a webbhook to Zapier from the front-end of the page. If you wanted to only trigger if someone is there for a few seconds (not a bounce) you can put the outgoing webhook in a setTimeout. If you have the following code:
fetch('https://hooks.zapier.com/my/hook/path')
It will contact Zapier. From there, you can use SMS by Zapier to text yourself. You could also pass along relevant data to be used in the text, if you wanted.
All that said, it seems like live-chat apps (something like Olark) will make it seem like you're online always and can forward incoming messages to you somewhere you can respond right away. I haven't tried any, but I can't imagine yours is a unique problem.
So I've been working on a website for a while. GA account has been up for a couple months but I waited for the website to be finished before putting up the actual JS tag.
In the meantime, the website is being HTTP password restricted (basic authentication) so it isn't even accessible unless you know the user/pwd combination.
To my surprise, I realized today that GA has logged several hundred views to the root of my website. Paths are mostly things like:
/
/?from=http://social-widget.xyz/
/?from=http://www.traffic2cash.xyz/
Bounce% and exit% both at 100% for all of them.
I realize this looks like referral spam, and there are ways to prevent it. Came across this upon googling:
http://botcrawl.com/block-social-widget-xyz-referral-spam-in-google-analytics/
My question is: how can GA log anything anyway when no tag is up and the website isn't even accessible?
Thank you very much in advance
Because it's spam. They hit Google Analytics directly with random GA codes and don't even go through your website.
GA can't tell if these are real hits (from website visits) or fake hits (from spam bots who hit GA directly calling the same ode as they would if on the website). Though arguably they should do more about this.
Massively annoying - particularly when first starting out as this can be a heavy proportion of your "traffic".
It's easy to set up a filter rule is to catch a lot of this by filtering on hostname. As they are randomly hitting GA and don't even know what website they are hitting GA for, they don't usually set this correctly. Real traffic should only come from yourwebsitedomain.com so add a filter for that.
STRONG piece of advice: abandon the default UA-########-1 tracking code of your new website -- simply do not use it!
Create a second and third property on the Admin screen, then use the tracking code for the third property. You will immediately see a lot less spam. No filters or segments necessary!
If you want the whole sad story about spam visits in GA, I have been maintaining the Definitive Guide article for over a year now:
http://help.analyticsedge.com/spam-filter/definitive-guide-to-removing-google-analytics-spam/
I've set up a goal for the signup process on my site, and I can see that users exit the Goal funnel at a page with nothing but a input and a next button, landing on another page on my site.
I'm guessing this is when users create fake profiles in one tab, while having another tab open somewhere else.
Does anyone have any ideas on how to deal with this? I'm not even sure what's best practice here, here's a few ideas:
Force the user to finish these steps as long as he is signed in for the first time and havent completed them, but that would be a development issue.
Setting cookies in the signup steps, and (if first time signed in) add a check globally on the site that redirects the user to the last step.
Other suggestions?
Even if a user has multiple tabs open to GA the requests are serialized and they all look like one browsing session. I do not believe you can check for this with GA at all.
I want to see how many users are on a particular page and limit future attempts by other users. I have a radio station and using a simple swfobject to play music from my system to everyone.
It works just fine, but I want to limit the number of concurrent users on the radio page ONLY. The users can be on any page without listening to radio, but limit the concurrent users on this particular page.
How do I do that?
Thanks for help.
If you can isolate your actual player to its on site on IIS, like radio.yoursite.com you can throttle the connections easily using IIS, the link is to IIS 6, but 7 should have a similar option. I guess the point I'm trying to make is that it would be a challenging task to do at the page level, but if you do it at the site level, it might be easier, an option if you can move your radio to its own IIS site.
As Aristos pointed out, this is easier said than done:
You can easily track how many have opened the page, but if they leave via an html link you will not be able to know they left.
There are ways to get around this which may not be very accurate or elegant.
You could use AJAX to keep tabs on who is still on the page by polling the web service. If the system doesn't get back a response for the particular id in a certain amount of time you can infer that the user has left.