I have multiple HubSpot forms on site. I need to track each on setting up conversion goals in GA. Ideally, I'd like to be able to track how organic traffic is converting.
I set up goals as explained here: https://medium.com/#dillonjones/the-easiest-way-to-setup-hubspot-form-tracking-in-google-analytics-a8ad9ab1fc4d
The problem is that since it tracks an Event, it triggers a conversion for all HubSpot forms, no matter which one is filled in.
Is there a way to set it up to track the conversion for HubSpot per destination page? All forms have separate thank you pages.
If you configure 2 different goals, one for each form (for example by distinguishing them with the event label), you can make sure that the two forms are activated separately, however if you have many forms all the same, for the current session you will not be activated more than one goal for each type of goal per session.
You can always rely on events, perhaps by writing the landing page url in the label to more easily distinguish them in Analytics.
Related
We have a complex order form with multiple steps all taking place on one page. From a business analysis point of view we've been given a requirement to be able to visualise the progress of users through this form in Google Analytics as a funnel.
e.g.
Option on step 1 clicked
Option on step 2 clicked
Input on step 3 completed
Checkbox completed
Form submitted
I know we can add various JS events across the form to track the actions that have been taken, but I can't seem to find a way to create a funnel in GA from this. We're using GA with Google Tag Manager.
The goal is to be able to analyse where on this form users are abandoning it, and how long they are spending on the various steps.
Is this possible? My current research suggests that GA couldn't create funnels from events a few years ago, and that it doesn't seem possible still. I don't want to use the method of virtual page views that I have seen floating around, as this comes with too many other negative effects.
If you want a manageable funnel report in Google Analytics, you shouldn't be using events but virtual pageviews. Anyway, if you don't want to use the latter, Google Analytics offers the Events Flow Report (https://support.google.com/analytics/answer/2521316?hl=en&ref_topic=2521315), in which you can see how users activate the different events you have configured, even if it is not strictly what you are looking for.
The alternative is to track these events in Google Analytics and create a funnel with Google Data Studio.
I have a pretty big website, and I'm wondering if google analytics api allows me to look at how many pages were made per month. Or rather, a list of sites that were made with a date tag, that way I can transform it into a count.
No, GA will only provide you with information based on visits, if pages were created and no one visits them, then that page will be missing. Plus you're looking at this MoM, if all of your pages don't get visited during a month, then they will be missing as well. Your best bet is to use a site crawler to index all of your pages.
If you really want to capture this in GA, then consider triggering a GA event when pages are created, this is assuming the creation process is via a web interface (wordpress for example).
I'm looking for some advice in a best-practice sense. Let me sketch the situation:
There are 8 companies with similar services. Together they have decided to launch a new brand, which will encompass all of them. To promote this new brand, an ad will be placed on all of their websites. This add will include a CTA, and a close button which will minimize it into a bar. This element will be opened the first time someone visits the website. Upon later visits, element will be closed and only the bar (with a fold-out option) will be shown.
The CTA will link to a page in the site of the main brand.
I'm unsure on the best way to measure this in Google Analytics. The 8 sub-companies each have their own tracking, but integrating with theirs will take too much time for now.
My idea was to add separate tracking to the ad, firing a virtual pageview to the GA of the main brand's website, and tracking clicks on the CTA and closing/opening of the ad through events. To prevent interference with the GTM of websites it is placed upon, this would be hardcoded. To prevent interference with the current analytics (since it is a short-term campaign), I would measure this in a separate view, perhaps adding a custom dimension and excluding the hits with a filter.
This will give us insight in how often it is shown for the first time, how often it is opened/closed and how much people click through. Furthermore this will allow us to track a conversion rate on the landing page (which has a form to fill out).
The 8 websites on which it will be shown each have their own analytics, implemented in various ways (GTM, Classic Analytics or Universal Analytics). We do not wish to interfere with this.
Do any of you have tips/tricks or feedback on my plan?
Situation: I have used Google Tag Manager to set up Google Analytics (GA - Universal) on a multisite network. There is one GTM container, and each website has its own GA property. I used a GTM variable to reference all of the GA properties. I am able to track cross-domain sessions. In testing, I am able to follow a user's session across multiple domains under the same session / client ID.
Problem: I'm stuck with what to do next. I'd like to create some Goals and Views that track a user's journey through my sites and measure the usual stats (bounce, drop-off points conversions, etc.). However, I'm not sure where to begin. I see plenty of information on the Internet for how to set up cross-domain GA tags in GTM. However, I don't see anything out there for how to create Views and Goals for cross-domain setups. A few questions that come to mind are:
Do I create Goals in the destination site's GA account (e.g. mycheckout.com), or the site where the session begins (e.g. myproductinfo.com)?
When creating Goals, do I only use the permalink slug, or the entire link? I thought I could only add the permalink.
How does this information roll up into one report?
I found this link, but I'm not sure if it's the 'best practice'. I would greatly appreciate it if someone who has previously implemented this could provide an outline of best practices, or a link to a good tutorial on the subject.
Thanks for your help!
Chris
You need to understand GA definition of Views and Properties. Views are like database table views: you can either show the whole table or a sample of it.
To have all data collected without sampling a "Raw Data" view (no filters) should always be used. Each view has its own conversion goal definitions. So in the "Raw Data" view you can create a goal for any page tracked. If you filter a view for one domain (e.g. "confirmation.com View with appropriate filters"), only goals for this domain should be created (otherwise they will never count a conversion).
When creating goals you can define filters for the "ga:pagePath" parameter. So it depends on your GA tracking setup, what part of the URL it tracks. Go into chrome web developer toolbar and hit the "network" tab. Open your page in this tab. Then search for requests ending with "collect", these are the data trackpoints send to GA. There you can debug what URL information is sent to GA (search for the "dl" parameter within the query string parameters list).
I'd like to track screenviews in my website, is this possible or are screenviews just meant to be used on apps? If so, how can I do it? Let me give you an overview of my situation.
I am restructuring a web site. Some of the pages that used to live under differents urls are now living under the same, with a hash id to denote the particular area of the page the user is in. So, for example, http://www.example.com/topics/topicA, http://www.example.com/problems/topicA and http://www.example.com/equations/topicA, are now in http://www.example.com/topics/topicA#content, http://www.example.com/topics/topicA#problems and http://www.example.com/topics/topicA#equations.
Now, I'd like to keep track of users visiting these areas. My initial idea was send a page view when the url is loaded and send a screenview each time the user clicks on the button to change the area of the page (i.e. #content, #problemas or #equations). For doing so, I used something like ga('send', 'screenview', {'screenName': 'content',});. As I couldn't see the screenviews in reports, I played a bit, setting the app name, the app id, the installer id etc before sending the screenview, for example:
ga('set', {
'appName': 'myAppName',
'appId': 'myAppId',
'appVersion': '1.0',
'appInstallerId': 'myInstallerId'
});
ga('send', 'screenview', {'screenName': 'content',});
So I can't see the screenviews in the real time reports (though I can see the page views). I can't see them in the regular reports either. I decided to create custom reports with dimensions Page and Screen name. There, I see sometimes screenviews are tracked (I think it happens when I set the appid etc before sending it, but not sure about this point).
Are screen views adecuate for tracking this behaviour or should I use just events, as I'm not on an app at all (just a responsive website)?
By the way, I am using Drupal 7 but that shouldn't make a difference.
Thanks in advance for your time and I hope I am making my question clear enhough.
Technically speaking its probably possible to send both pageviews and screenviews to the same Google Analytics web property.
The problem you will have is seeing the information. The way the Website is set up its either application or web account, Screenviews or pageviews. The reports are different, and you cant swap between them.
So you could send screenviews to a web site web property but you would never be able to analyse it on the website you would have to use the API to rip the data out. That and you would be analyzing apples and cars. Screenviews and pageviews are different they cant be analysed together.
Because of this web property's should be kept separate one for application (screenviews) one for web sites (pageviwes).
You should in my opinion do this using events.
+1 for an interesting question that made me think :)
Is possible, actually in BigQuery you can reach both data and see how this interact, both will have the same schema and will be stored in the same dataset(it is linked the raw data view). Even in the same sessions, you can send pageview and screen views having funny results.
But there is some important consideration when you implement this.
You need 2 different views, one Web View and One App View. Both views will let you access to different information and is not possible on the web interface of Google Analytics to access to both info at the same time. Not sure if with the API you can access to both info at the same time, I think that is totally possible
In the App View, you will able to see only information of screenview, events and ecommerce.Is also mandatory the App Name parameter on this hits.
In the Web View, you will able to see only the pageview reports,events and events.
The ecommerce info and events will be reachable from both views, there is no way to know if this comes from a web or an app ( technically). So is tricky to read this kind of reports in that case.
Sessions can experiment stranges behaviors. As example gosht sessions coming from the screen view with no page view, sending events.
Taking this into consideration, as Dalmto says, the best to you is use events or sent virtualpage view.
Mixing pageview and screen view is not recommended by Google but is totally possible.This kind of implementations is only useful when you have an embed web-app and a webpage on the same server and you want to have it all on the same dataset, if this case apply, is highly recommended to add a custom dimension to filter the app info on the web view and the web info on the app view and keep both worlds separated.
As the last point, your code is working, I can see the screen info on the desktop property. But not be able to see it in the web view.