I want to optimize a kind of page that prompts the user to either login if the user already has an account or register otherwise.
I have setup events for when the user arrives to the page, clicks on one of several possible login buttons (username and password, Facebook account, Google account, etc) or clicks on the register button.
To measure the conversion I would like to see from all of those that arrive to the page but did not click the login buttons, what is the conversion rate of those that register.
Basically I need to measure Registered / (Landed - Logged in).
Is there a way to measure this with Google Analytics or do you recommend some other solution?
Related
We have a website that provides information about our SAAS product, it also has a login button that redirects our users to the saas app that is on another domain.
I want to create a segment that excludes these users from our analytics, they all take the same journey of hitting the home page then clicking login which fires the event.
How can I achieve this, I can see how to filter for an event and path but not exclude if both these happen
On the Analytics page:
Configure -> Audiences -> Create custom audience
Here you may choose on which conditions the users will be included in this audience. The idea is to include all users except those who clicked on the login button. So as a condition you can specify click event and make sure that it was not on the login button, and how to achieve that depends on your metrics.
TL;DR;
Facebook login makes the original referral URL change since and in GA it will look like they originally came from a Facebook.
We have the following problem using Google Analytics (UA) for Facebook (Oauth) login:
user lands on /page/1?utm_campaign=aaa and GA session is created with correct initial referrer, campaign etc.
user visits a few other pages and decides to register using Facebook
Facebook login makes the user's browser to go to facebook and come back which changes the referral and thus creates a new GA session
When user lands back on our callback url we fire an event that is converted to goal in GA
The problem is that all users who register using Oauth have the referral set to Facebook and the landing page to the page where they land after Facebook's callback because that's when GA "resets" the session :( .
Is there a way of joining the two sessions in GA and making it know that it is the same user all the time so that Facebook registers keep the full information on initial referrer, landing page, UTMs etc. ?
Follow FB SDK example and OAuth dialog will open in a popup window.
It will remove the issue with GA.
Most of OAuth providers that I know also support opening a dialog in a popup window.
in the site in which I'm working the registration is mandatory to complete an order (is an ecommerce site). In the registration process, users have to fill in a registration form and then submit it. An email will be sent to users to confirm the account. After the confirmation (click on a link sent through email) the account is active.
I would to keep track of the user which complete the registration and then confirm his account clicking on the confirmation link in the email.
Basically, my questions are :Do users which submit the registration form, confirm their account? then, Do users which confirm their account make a purchase on the website?
I know how to track the submitting of the form (with event tracking or destination goal, it depends), but I don't know how to put a trackable link in the confirmation email. I can't use URL Builder, because the confirmation link is generated automatically and it depends on the account itself (each link is unique for the account). How can I keep track of it?
One solution for you is to include a Google Analytics _trackEvent call on the email activation page. Docs here:
https://developers.google.com/analytics/devguides/collection/gajs/eventTrackerGuide
This is the method we use to do something similar on our site.
I have an ASP.NET MVC application which uses Google+ sign-in to authenticate the user. The flow is as follows;
User accesses controller action decorated with [Authorize]
attribute, forms authentication is configured so the user is
forwarded to the log in page.
User clicks the Sign In with Google+ button and the server side flow is initiated as per guide
Server receives the Google tokens which are used to authenticate the user, logging them in and returning the standard asp.net auth cookie in the response. The user can then access the site with the cookie.
Now, if I go through the usual asp.net forms log out process of clearing the user's cookie/session there's a problem. If they attempt to access the application after they've logged out but are still signed into a Google product in another tab, they'll be re-directed to my login page. The Google+ sign-in button will automatically sign them back in again initiating the whole sign in process and getting a brand new asp.net cookie!! The only way to truly sign out is to ensure you are not signed into any Google products still and then attempt to sign out. Not exactly user friendly. I guess the same thing happens with all Google products, if I'm signed into Gmail and open Docs, I'll get signed in automagically. The difference being if you sign out of one, you'll sign out of all Google products. I think.
There is currently not a supported means of logging the user out from your site. What you can do is force the user to click the Google+ Sign-In Button before they will be authorized unless you have set a cookie on their client indicating they are signed in (or enrolled, if you want to distinguish between the sign-in action and being signed-in). You can look at this question:
how do i sign user out of my app?
or this question:
Preventing automatic sign-in when using Google+ Sign-In
for discussions on this topic on stack overflow and answers to similar questions.
I'm tracking the free trial sign-ups for an online service that requires
email verification to complete the sign-up process.
How do I create a goal to track the sign-ups given that email verification required?
The registration process is as follows:
Click on free signup button (goes to
"/signup/")
Fill out sign-up form, including email address (goes to "/check_your_email/")
Click account verification link in email.
Arrive at the new account confirmation page. I plan to define this URL ("/confirm/signup/username/hashcode/")
as the goal
If the user closes their browser, then opens their browser, and clicks on email verification link, will the goal be tracked properly?
If the user closes their browser it will be considered a new visit when the browser opens up again to complete the sign-up process. This will increase the reported visit counts and you might also have problems with using visit level reports.
There could also be a problem if the user is not using their default browser then opens the link from an email program and their default browser is used.
You should probably set up two goals: one for the /check_your_email/ page and another for the verification page. That way you will be able to see if there's a significant drop-off between the two and work from there.
If you define "/confirm/signup/username/hashcode/" as the Goal, even if the user closes their browser and comes back to this page it will still be recorded as a Goal conversion.
You will have a problem with the conversion funnel : for those that did not confirm during the same visit, it will look like their visits dropped at the /check_your_email/ step, and you should see a similar number of visits coming from (direct) - email is usually recorded as Direct visits.
Also bear in mind to use appropriate Regular Expression if the confirmation URL varies with usernames.