It should be so simple, that it is frustrating.
There is the famous 'landing page' dimension. However, a 'landing page' is defined as the FIRST page of some session. What dimension shows the FIRST page of the FIRST session of a user? For example, when I create a report, that shows for every custom event (==goal/conversion) the landing_page, I see the landing page of the session in which the event was sent. But I want to see the data (landing page, source, referral) of the FIRST session. This is also called First Touch attribution. But I can't find a way to change it. I should be simple, and I can't find any information about it.
Related
I need some help with Google Tag Manager and Google Analytics.
I want to send a pageview to Google Analytics if a user is viewing an image in a gallery on an article. The user is staying on the same URL, when he is viewing an image.
I created a trigger group which consists of two events
• Consent given by the user to use Google Analytics
• Event which is fired when an image in a gallery is being viewed
This works so far so good. Unfortunately, the trigger group is only being fired once on a page. When a user open the gallery and views the image and scrolls to next image, he is staying on the same URL. In that case, the trigger group is only being fired once.
How can I achieve that the trigger group is being fired multiple times on the same page without removing the second trigger (consent)?
I found out that I can create a second trigger group and add two image views and the consent as a trigger. But this solution means that I have to create 100 new tags, which is kind of crazy. Is there any workaround?
Thanks in advance
Once consent has been given by the user in a way that each pageview can pick up (e.g. you're setting it in some persisted state: data layer, cookie, etc.), you're ultimately just looking at triggering when the event happens.
Since you describe a scenario where it happens only once, I'd urge you to take a look at the other triggers on your tag and remove the page-specific trigger your description suggests you have in place. Replace it with only your event and consent triggers and it should work every time an event is observed.
I have a form that when submitted it goes to a different "success page" and I want to use that landing page to track conversions or count how many times people hit the "submit". I could use a page view tag but then that will fire every time someone goes to that page. So perhaps if someone hits the back button and reloads the page then that will count as a form submit.
So I would like to make a page view Tag in google tag manager that only fires if the page view is coming from a specific URL or referred from a specific URL. Is this possible?
Thanks in advance.
It is possible. Enable the built-in "referrer" variable, and on your target page create a trigger "pageview", with an added condition "referrer equals <your referrer>".
Some browsers might not send a referrer header, so this is not 100% reliable. If the page that sends the traffic is under your control, you might consider using a tracking parameter instead.
I have a single page web app with a third party marketing tool I need to track. The tool implements a form.
What I need to know is:
How many people started filling in the form on a certain page type, i. e. first-clicked any of the fields (once per page)
All of the fields share the same class (at least partly). So I created a trigger that fires on
"[click classes] starts with [classname part]" AND
"[page url] contains [pagetype]".
This trigger is used for an event tag A with the "tag firing options: once per page", so that I do not get all of the element clicks, but only the relevant amount of starts which is per page. *
How many people successfully submit a form (once per page)
This was a little more tricky, since "successfully" means that I am not interested in simple button clicks, since those could also end in error messages if someone missed filling in a required field. Also, I do not get a success page, but a success message. The div this message appears in is always there, it is just not filled until submission. I solved this by creating a custom variable defining that element and an "element visibility trigger" that fires on
"[page url] contains [pagetype]" AND
"[custom variable]" equals [success message]"
+ DOM change observance.
This trigger is used for event tag B with the "tag firing options: once per page". This is necessary, since the marketing tool allows multiple successful submits of the very same form (please don't ask). Therefore, I need to restrict this to once per page as well. *
*) Now here's my struggle: This setup would be working fine for a multi page application with a standard page view tracking. However, I need to have my standard page view trigger to fire at history event changes, and this crashes my setup. I don't know how to restrict the two new event tags A+B for firing "once per page" if I don't have actual page views.
I cannot imagine that I am the only person who needs to solve this case. However, either everyone else just knows how to or I am not searching well enough - I don't find anything on this matter.
Does anyone have any idea on how to solve this?
Any slightest hint would be very much appreciated!
Thanks in advance!
I'm creating a form that a user has to completely fill out before they are able to register for a website. What i'm trying to counter is if the user gets to url of the second page by accident. I've tried using if(!isPostBack) and then inside the if statement redirecting them to the first page but that only works the first time, and the user can never hit the second page that displays their details when they click on the submit button because the second page is now a post back. Any help would be greatly appreciated!
There are several ways of doing this. You could use Session to store user progress. Also, if you have a long multi-page form you could have a master table for your form in the database that tracks user progress (column named ProgressPage, for example).
For example, if I have a news page that's already being tracked via GA and I add a javascript event to capture clicks on a specific link to the news page (e.g. navigation) am I then 'double counting'?
If a fake pageview is not beneficial in this situation, and from your description that you're looking to track an engagement click on your page, use Event Tracking instead of Pageviews.
Tracking a click/event is easy (especially if you're already using Javascript). The best part is that this event is not considered a page view, keeping those stats safe.
The implementation is simple and allows for quite a bit of customization:
_trackEvent(category, action, opt_label, opt_value)
Below is an example of a link that's been encoded with an event tag:
Play
Here's the Google Analytics resource page on Event Tagging:
http://code.google.com/apis/analytics/docs/tracking/eventTrackerGuide.html
Well it's not a real page view, but Google Analytics thinks that it is--i.e., it shows up in your pageview counts.
Fortunately, it's easy to filter those so they don't contaminate your pageview data.
So for instance,
_gaq.push(['_trackPageview', 'unique_virtual_pagename']);
So in your GA Browser, you'll see the number of clicks actually shown as the number of pageviews of *unique_virtual_pagename*, which is not good.
There are a two ways to fix this (that i am aware of): (i) set a temporary filter at the bottom of the pageview table; or (ii) set a persistent (c*ustom*) filter in your Admin Panel (which i think is best) to remove pageviews having only the name *unique_virtual_pagename*, or whatever name you've chosen. This will of course take up to 24 hours to set, so the best plan is to set the filter first, then add the javascript to your page. so the filter is active when you begin collecting clicks.
But that just solves the problem of disaggregating these virtual pageviews from your real pageviews, you still need a way to count/record them.
I prefer to create a separate profile in these cases. So first, i filter the virtual pageviews from my actual pageviews using a custom filter, then i create a new profile which has another filter excluding everything but these virtual pageviews. I usually give that profile a name based on the event.
What you're doing is registering what's called a 'virtual page view'. To GA it's seen as a real page view and shows up in your content report's and page view counts etc. This is often useful if you want to show a page view for media that GA can't track. It's also commonly used to count an event, such as a button click, as a goal conversion.
If you just want to record the event and not count a page view you should look at using GA event tracking instead.