Profile cover photo
Profile photo
Lindsey Buckle
189 followers -
Love my kids, love my husband, love my family and friends, my job (digital marketing analysis), my home and the place I live. Love my life.
Love my kids, love my husband, love my family and friends, my job (digital marketing analysis), my home and the place I live. Love my life.

189 followers
About
Posts

Post has attachment
Enhanced Link Attribution and In-Page Analytics

Where is enhanced link attribution reported these days? I have the Chrome extension but it's not working properly - keeps telling me to sign in to Google Analytics (see image), even though I'm already signed in. And the extension page says it has been deprecated (second image).

Is there anyway to see in-page analytics and link attribution these days? What's the alternative (besides creating a whole bunch of events)?
Photo
Photo
4/11/18
2 Photos - View album

Can anyone tell me how Goal Starts is calculated?

Is it just me or is GTM a bit odd when it comes to regular expressions?

I have the following pages:
/faults-and-emergencies
/faults-and-emergencies?location=someplace
/faults-and-emergencies/subpage1
/faults-and-emergencies/another-subpage

You get the drift.

I'm creating an event to capture the location parameter, and to record the event with a different action if there is no location parameter, e.g.
Event category = Faults and Emergencies
Event action = Location search | Direct view
Event label = parameter value |

I can then remove the parameter and aggregate all the pageviews. But I don't want to include the subpages. I thought I could do it with one regex trigger:

faults-and-emergencies[^/]

(Note, I have also tested it like this: faults-and-emergencies[^\/], which works in my regex tester).

I can't seem to get this regular expression to match the first page path listed above. It correctly captures the ?location url, and ignores the subpages, but the only way I can get the tag to trigger on /faults-and-emergencies is by adding a separate "equals" trigger.

Have I gone crazy here? Am I doing something wrong? I'm happy that it works but a bit frustrated that I have 2 triggers instead of one. Thoughts?

I'm after a bit of advice on the best way to track something - not sure whether he or Google Analytics is the best forum:

So, we have GTM set up on our pages and we are doing the marketing for a product related to our industry, and created by us, and only available to certain eligible customers of ours BUT we do not actually sell or own the product. It is being sold by a third-party through their website and we receive a small monthly commission from them. The commission is not really a money-earner for us, and in fact we'll spend more on marketing than we'll make. Our interest is more in providing value to our customers in the form of a product they have requested. We are responsible for marketing the product and we'll send customers to the third-party site from our website.

Currently I'm tracking clicks on the outbound links as a goal but beyond that point we don't know what happens - although we receive a daily update as to which of our customers have purchased the product. Obviously in order to market effectively it's in our interests to track the online journey right through to the end. My questions are around how best to do that (providing we get buy-in from the other organisation).

Would it be best to have a separate view to track these sessions, or is it okay to just include some cross-domain tracking in our usual customer view?

The client already has GTM on the sales pages. I understand that it is possible but not recommended to put more than one container on a page. Should I ask them to put our GA code into their container? This might be a good idea if they've already set up ecommerce tracking and are happy to let us access that data. Or I guess alternately they put our tracking code directly on the page separately. Or, they add our GTM snippet to the page.

I guess another option is to feed the data exports we receive from the client back into GA, although I'm reluctant to do anything too manual and I'm not really sure how we would connect it up with the GA data.

Any thoughts/advice?

The powers at be have chosen Cognito forms (embedded in an iFrame) as our website form solution. Despite my having written specific requirements for the tracking of web forms, which appear to have been either ignored or not passed on to the relevant person, it seems that Cognito forms are not easily trackable in Google Analytics, if at all. Can this really be? Our new website goes live tomorrow and currently I have no way of tracking anything about any forms, other than views of the pages they are embedded in. Not even simple form submissions. Does anyone have any clue or any hack or ANYTHING AT ALL (please!) that will allow me to track these forms? I'd prefer a GTM solution but right now I'll settle for a simple form submit direct to GA.

TIA.

This may be a question for the Google Analytics community rather than GTM. I'm looking for some guidance as to how best to set up our GA/GTM accounts. We have 2 separate subdomains - one public and one logged in. We have 3 GA accounts (argh!). One per site plus a roll-up. The main site has a property for live and another for staging. The other two accounts only have 1 property each. Then each property has multiple views for various combinations of test/working, internal/external IP.

Then there are 2 GTM accounts, one for each site. And each container contains multiple tags to track to both the main GA account/property and the roll up one.

We're just about to go live with completely rejigged sites - same URL but new IA etc. For perhaps obvious reasons I would like to simplify the GA/GTM accounts.

My original plan, which I've pretty much implemented, was to have both subdomains use the same GTM account and only one container within the account. They then use GTM environments (and a look-up table) to track dev, uat and live to different GA properties (within the same account). The live property would then have multiple views (raw, test, and variations of working for internal/external IP plus different subdomains, e.g. authoring, customer service). There is also the need to segment customers depending on whether they're logged in or not but I'm thinking this will occur at the segment level rather than view filter.

As for the GTM container, there will undoubtedly be some tags that are only used by one or the other subdomain but I was planning to use folders to organise these and to use the hostnames in the triggers.

I've since discovered that we probably don't need the dev environment - and in fact it was always my plan to use it for testing and then delete it after launch - but we'll stick with UAT for any future feature releases. The public site is ready to go live this week but the logged in portion isn't even ready for me to test tracking beyond pageviews. I was led to believe they were pretty much the same site and that customers would log in and then move freely between the secure and public pages, and I based my design on this. But it seems that this may be less the case than I'd assumed. It sounds like they are still very much separate subdomains, although there will always be enough movement between the two for roll-up tracking to be necessary.

I'm now questioning (sanity-checking) my original design and wondering would I be better to have 3 properties (public, logged-in, roll-up). This would probably result in a greater number of views overall, but may mean fewer views per property. I feel like it might result in more repetition of configuration, but wonder if it would offer more valuable data. Does anyone have advice as to the best approach? Or pros and cons of each?

In my original design, what happens if I have a view for each subdomain and the customer travels between the two and back again? Is it still classed as one session if sub-domain tracking is configured correctly? Also, is it recommended that I state all of my sub-domains in my referral exclusion list, or just my main domain?

(Sorry for the long post and thanks for reading.)

I've been asked to provide stats on a particular page on our site. And it's kind of doing my head in.

One of the things they want to know is whether people come back to the page, or just use it once, and I'm trying to understand how dimensions such as returning/new users and count of sessions can be used in the context of a page (what with the whole hit level v session level thing, not to mention report period).

Can I get this information? Can I work it out? What's the best way? As a secondary dimension on a filtered (by page name) All Pages report? Or with returning user as a segment then viewing the pages report? Or with "sessions including page x" segment and view the frequency/recency reports?

Any advice?

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Post has attachment
I have a best practice question.

We are currently in the process of implementing a new (replacement) website. The website CMS will be Sitecore with ADX forms embedded in iframes (sigh). What is the best method for ensuring accurate tracking of the forms? I've been reading a fair bit about this and I'm just trying to get it straight in my head. AFAIK the forms will be on the same domain as the pages.

We'll need to track form submissions, but also (probably) engagement, abandonment and possibly timing; the usual suspects.

We'll also need to ensure that we don't inflate the pageviews (naturally).

So should I put the tracking code on both the parent and the child frame, with an exception on the pageview tag (as per Simo's article: https://www.simoahava.com/gtm-tips/prevent-tag-from-firing-in-iframe/). And then just pick up all of the other event tracking/form submission tracking as normal?

I read about the postMessage method in this article (http://www.lunametrics.com/blog/2015/10/21/google-analytics-iframes-form-submissions/) but I'm thinking that I probably don't need it as I should be able to push straight to GTM from the iframe. (Assuming we can access code in the iFrame; I have no experience of ADX and I'm waiting for developers to confirm.)


Wait while more posts are being loaded