I'm New when it comes to google analytics and I have an Apps that use google analytics, but I got some question, Can we use google analytics to track paid and free user separately? If it can where I can find it in google analytics? I'm quite confused with a lot of information in there to use it in data studio
some metrics that I used right now from Google Analytics:
users -> to get all unique user that come to my apps
You can distinguish whether sessions that came or not from paid campaigns, but a user can have more than one session and each session could have been started by different channels, for example from a pay channel and another from an organic channel, but the user is always the same. So, with basic tracking, I'd talk about sessions and not users.
Yes, you can track such details, but you need to let Google Analytics know, who do you consider to be a free or a paid customer, as this is not a standard dimension. This can be achieved with Custom Dimensions.
Key steps involve:
Creating the custom dimension in Google Analytics administration. This is a property level setting. Based on your description, this will likely be a user level dimension.
You need to adjust your tracking code (or Google Tag Manager settings) to include the customers' level among the data, which is sent to Google Analytics. You need to refer the proper dimension ID, which you get during the creation of it.
You need to apply the given custom dimension to your reports. This can be done by using a secondary dimension within the standard reports, or by creating a Custom report. It is also possible by creating a segment of different users, and to apply this segment to various reports.
Further reading is available in this support article.
Related
I am trying to get to a point where I can identify visitors who are generating website Goals. And identifying them via their Pardot ID-s in GA.
Do you think that's possible?
On the site every visitor gets a Pardot cookie and in that there is a readable Visitor ID which via an API query can be turned into a Pardot ID.
But how can this piece of information get stitched to the rest of the GA parameters? How to push this into GA as a custom data point so I can create a report on who are the Pardot IDs that completed a certain goal this week?
Is there any guidance you can give?
Assuming, that Pardot ID itself is not a Personally Identifiable Information (PII) in terms of Google Analytics, there are several ways to accomplish this.
You could provide this data as User ID, which helps Google Analyitcs to identify users across several browsers and devices. However, this dimension is not exposed on the reporting GUI or the reporting API. (Available dimensions and metrics can be browsed here.)
Instead, or in parallel, you could store this information in a custom dimension, which, can be used in standard or custom reports, or via the reporting API as well. There a couple of things to consider. According to the Measurement Protocoll reference, the maximum length of this field is 150 bytes. You should also decide, if this dimension is most useful for your needs and possibilities on hit, session or user level, about which you can read here.
I am looking to provide analytics for a website which has user generated pages (which would therefore require a unique tracking ID for each page).
Is there a limit to the amount of different pages I can track?
I have looked around documentation provided by Google on data limits but have found no information regarding this.
Thanks in advance
You can create up to 50 propertys per account.
The trackable documents should be unlimited. Only limited by pageviews per month (10 million /month).
limits and quotas
Your assumption that you need to have a different tracking ID for each user generated page is not necessarily correct. You can track the entire website using the same Google Analytics property. I assume you're worried about exposing analytics data about the page generated by user A to user B accidentally. To prevent this from happening, what you can do is configure a custom dimension in Google Analytics that records which user a page belongs to. Then, when exposing analytics data to a specific user, you can make sure to only expose data about pages that belong to that specific user.
I have asked this question several times over on the GA forum, but no result. So maybe you guys can help...
I have set up google analytics with userIds on various pages of a site, with the aim of identifying exactly which pages are looked at by which users. So, sending GA the string
ga('create', 'UA-39536320-1', {'userId': '1001'});
means GA keeps track of all accesses by user 1001, and I can then (in theory) track all pages looked at by this user.
Trouble is, GA reporting seems to offer no out-of-the-box way of doing this. Indeed, some of the reporting features supposedly enabled by GA with userIds just don't seem to be available (eg coverage; user engagement; etc).
Am I the only one trying to do this? Seems other people have achieved a similar result using custom variables; do I have to do that, and give up on GA userIds?
The userId feature can be used in conjunction with a user id enabled view (profile) to analyze cross device sessions.
As pointed out by DalmTo it is possible to use custom dimensions to track any non PII information about a user. This article here gives a good example combining sending user scoped custom dimensions along with imported CRM user data to analyze and segments users for remarketing purposes.
I'm trying to track the success of marketing campaigns through conversion on a portal. The portal is largely JS based and for right now we can't use URL goal tracking. Instead, I'm planning on using event-based goal conversion that can report all the variables I need. The problem is how do I connect marketing campaigns to the eventual conversion? These campaigns span SEM, email, landing pages, partnerships, etc.
My initial idea was to use a URL param to set a session-level custom variable identifying the marketing campaign that funneled the visitor, and then to compare this to goal conversion. However, I'm not sure custom variables can even be compared to goal conversions in Google Analytics -- and I'm worried that I might be over-thinking this.
I'm worried I'm way over-thinking this. If I create a custom campaign using the URL Builder, will that give me everything I want, allowing me to track campaign conversions?
Yes, I think you are over-thinking things. :-)
As long as you properly tag the campaigns using the utm variables in your destination URLs as they show you how to do in URL builder, they should allow you to see your specific goal conversions by source, medium, campaign, etc. in your GA profile. Using the new Multi-Channel funnels features you'll also be able to see how the sources of previous visits influence future conversion behavior as well.
Generate help with campaign conversion tracking here: http://blog.crazyegg.com/2011/12/02/track-conversions-google-analytics-campaigns/
Info on Multi-Channel funnels here: https://www.google.com/analytics/features/multichannel-funnels.html
Just wondering if this this possible? I realise you could never use it to display recommendations on a page but it would be useful from an analytics point of view to see for example what other products user's who've looked at product x have also looked at.
You can use Advanced Segmentation to do this.
Advanced Segments slice Google Analytics data on the basis of sessions. Sessions are a collection of pageviews that correspond to the popular notion of a visit.
If you create an Advanced Segment for users who visited /product/x/, it will return data from all the sessions in which that page was viewed. (Similarly, you could create a segment for /product/x AND /product/y. From there, you could filter it to only include your product pages, and exclude the original products themselves.) As a result, this session-based querying is perfect for your use case.
So, yes, you could use Google Analytics API data to inform a simple recommendations engine. The only caveat I'd give is that the Google Analytics API is a little slow, so you'd want to cache the data locally in your app, rather than querying it directly on every pageload.