Profile cover photo
Profile photo
Lindsey Buckle
176 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.

176 followers
About
Posts

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

Post has attachment

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.)


Does anyone know why Tag Assistant might give me different results when I'm logged in as different Chrome users?

Same public website. Looks like my Tag Assistant settings are the same. In one browser, both the GA and GTM tag have happy faces. In the other browser the GA tag is showing a "non-standard implementation" error.

Is it possible another extension is interfering with Tag Assistant?

Post has attachment
Can anyone solve this mystery for me?

When I segment my data by sessions containing a specific event I get 31,313 users. When I add a second session, segmenting by users that have sessions with the same event, the Users metric for the first segment adjusts, as do my All Users metrics. See the screenshots. The time period is a year so could it be a sampling issue? And if so, how can we trust data when applying mulitple segments? (The two segments are exactly the same but one is session-based and the other is user-based.)

Is there any other way to analyse this data over this time period? I have PowerBI but still learning so I'm wondering if that is a better option than GA UI?
Photo
Photo
9/9/16
2 Photos - View album

Quick question.

I have a client with cross-domain tracking set up to a booking engine. Using tag assistant I can see that the booking engine is sending data to my client's GA. What is confusing is that the booking engine pages are showing up as landing pages (source/medium = direct/none). I wondered if it could be from sessions timing out but there is a high number of New Users.

About 20% of all sessions are starting from a booking engine page and together these have an average of 81% New Users (higher than site average of 74%).

Any ideas why this could be happening or how I might investigate further? I can't help but feel like I'm missing something really obvious here.

Quick question re. Data Import.

Does anyone know whether I have to upload my data file again following a change of views in the data set?

I created my data set to apply only to my test views then uploaded the data. I'm happy that it's working and have now extended the data set to all relevant views. Just wondering whether I now need to upload the data again. I will anyway, for expediency, but it would be good to know whether this is actually necessary for future reference.

TIA
Wait while more posts are being loaded