Profile cover photo
Profile photo
William Vicary
139 followers
139 followers
About
William's posts

Email this morning "Important update to Remarketing with Google Analytics".

This is good news and it's great to see that the difference between the remarketing audiences from GA are converging with the Adwords tags.

I just wanted to see if there is an update on whether this will enable View Through Conversions once rolled out? That's the only other element currently only available with Adwords tags after the above rolls out and it would be great to see 100% parity between the two tag types!

For large websites that span multiple countries but are all within the same domain what is your preferred approach for GTM/GA?

We could, of course, segment by View within a single property, utilising the same GTM container. This has the benefit of cookie sharing and originating source/medium being properly tied and the automatic roll-up overview (which they are used to with their Adobe suite) however it has it's limitations on the number of views available and this can be a limitation when the website spans a number of countries/regions/campaigns.

What would your preference be for a client using the free version of GA?

To add, GA Premium is probably out of the question for these guys for now, otherwise an auto-roll-up in the premium account with separate properties would probably be preferable...

Can anyone help to unpick what's going on here?

We have a client, lets call their domain clientdomain.com.

They have a separate subdomain, lets call that subdomain.clientdomain.com.

They've just migrated to a new platform on subdomain.clientdomain.com which has frustratingly included a historic classic Analytics code. The main domain still contains their GTM container which remains untouched.

So we've now got:
subdomain.clientdomain.com - classic analytics (gaq code)
clientdomain.com - universal analytics via GTM

As expected our filtered subdomain.clientdomain.com (and unfiltered) views now contain a ton of self-referrals from the main domain.

However, oddly, our clientdomain.com Analytics view also contains a large number of self referrals, the entire clientdomain.com website is using the GTM container which utilises Universal Analytics and should (in theory?!) exclude any self referrals via our Referral Exclusion lists.

To add additional madness to the situation, the self referrals on the clientdomain.com view follow this pattern:
- Full referrer: clientdomain.com/page.html
- referrer path: /page.html
- page (secondary dimension): /page.html
- hostname: www.clientdomain.com

Looking at the recording I can see at subdomain.clientdomain.com that the flow goes similar to this:
- https://ssl.google-analytics.com standard request with the expected typical variables
- And then additional a request to
https://stats.g.doubleclick.net/r/collect with CID that MATCHES the clientdomain.com code.

To me it seems like the hit to stats.g.doubleclick.com here is causing issues? This feels like very unexpected behaviour going on, as if the Classic Analytics code is seriously conflicting with the Universal Analytics across different pageviews which sounds crazy but I can't see any other reasoning...

To add:
I don't see any referrals from subdomain.clientdomain.com on clientdomain.com filtered view which I would expect as the referral exclusion lists are being appropriately used on the main domain's universal analytics implementation.

+Elisabeth Yates We've received another request to link directly to our client account without prior access from a "Agency Development Manager" in your UK Acquisitions team.

Whilst I appreciate they have a job to do receiving an email to the effect of "Currently, the following account in your MCC are eligible for support. I have sent an access request to the account" is jumping the gun a little. If that email was "Currently, the following account in your MCC is eligible for support. If you would like I could send an access request?" it would be totally fine but sending a request BEFORE even touching base just feels like slimey sales pushing for their targets (which I'd say is more an issue with the relationship with Capita than with the rep's themselves).

I just want to flag this as a serious concern, these requests for access go directly to clients and understandably confuse them - this is the third time this has happened and the third time we've said we'd like no further requests to be made which apparently fell on deaf ears as a new rep comes on board!

This is very frustrating and a touch worrying.

Can anyone confirm how the Adwords Conversion Tagging differs from Google Analytics Tagging (and imported into Adwords?).

We always use Google Analytics imported goals and generally report with a mix of last click (Adwords) and Attribution modelling (Analytics). However I've been doing some research into how these differ and I believe they work like this:

Google Analytics Goal Imported into Adwords:
- Last Non-Direct Click (i.e if the last non-direct click wasn't adwords it would not be pulled in).

Google Adwords Conversion direct in Adwords:
- Last Adwords Click (Effectively)

So the attribution path below:
- Organic > Display > Adwords > Organic

Imported from Analytics: No conversion recorded in Adwords
Direct in Adwords: Conversion recorded in Adwords (as no understanding of the other paths are available).

Can anyone confirm this? I've read mixed messages and Google's documentation is vague around this.

We are concerned about members of Google's team namely job roles of 'Agency Development Manager' adding themselves to our clients accounts without first asking prior permission.

This is the second time we've had such unexpected requests and our clients also receive the requests and it naturally confuses them. We're paid to work for our clients and do not require support from frankly a team at Google that seemingly have the sole purpose of inflating their client numbers/spend to hit their targets.

The account management team from Ireland are super useful but this just feels like a waste of our time.

To quote an email from (unnamed) Google representative:
'we need to keep on top of your best practices and customer care so you maintain your partners badge.'

This feels like a threat to me and it does not sit well, can someone please shed some light here?

UX Improvement Request:

Does anyone else find it infuriating that there is no easy method of enabling macro's when creating a tag forcing you to either cancel your tag creation, fill a field with a temporary macro to then leave the tag, enable the in-built macro required and go back to create the tag as you were intended. (Similarly if you add a manual macro at another step of the tag creation stage the other fields do not have that new macro within the drop down list until refresh!).

I must bump into this every time I create a fresh container, very frustrating!

Does anyone have a preferred extension for implementing GTM with Magento? 

I have an install where jQuery is loaded after gtm.load and I want to set a customDimension for product availability as this website has a very short product lifetime and I have a feeling their old products are getting a significant number of essentially useless visits which I feel are likely detracting from the user experience on the website.

My current work-around was to implement a customMetric which was sent on gtm.load as an event, however I've just realised that this won't really expose the report we want (as, from what i can tell undefined == 0 when it comes to customMetrics and running a custom report only shows hits on products with availability, when we want both ideally).

I feel the only option is to send a customDimension and as it has to be hit level this has to go alongside the pageview, my concern is I don't want to delay the pageview tag until gtm.load as we'll likely miss out on a good number of pageviews. (I think gtm.dom is a good compromise here)

Ideally I don't want to push anything into the dataLayer for this website (development expense required) but I know that's the perfect solution.

To add further problems this makes use of jquery contains: parameter that isn't easily duplicated natively!

Our code is similar to the below:
function getQuantity(){

if ($('.prodDesc p:contains("Quantity Remaining")').length)
return $('p:contains("Quantity Remaining")').first().text().split(":")[1].trim();

  if ($('.prodDesc p:contains("Product Sold")').length)
      return 0;
  
return undefined;
}

Any thoughts?

Post has shared content
Wait while more posts are being loaded