As I am aware that GTM provides tracking functionality to page to get tracked in the google analytics with the help of HTML classes or ids. But we have an in-house tracking system which tracks events generated on the page. Is there a way to configure the GTM to do the in-house trackings as well?
Yes, it's possible. Having said that, it also depends on how your in-house tracking system works.
If your in-house tracking system contains JS libraries, you can add custom HTML tags in your GTM. If it just an image request, you can add custom image tags in your GTM to do the work. You can even add your custom javascript codes and manage them to fire on the page as you want.
Recently, GTM launched custom templates. You can create a tag template for your tracking tool and use it across your organisation.
Related
I've implemented Google Tag Manager via the react-gtm-module. I've added Google Analytics and the Google Conversion Linker tags, which do fire on all page views / history change triggers.
My issue is custom HTML tags are not firing. I am using the same triggers as Google Analytics and Google Conversion Link -- both are using page view and history change triggers.
Does anyone know why custom HTML tags would not fire in a react app?
I've tried deleting the tags and re-adding them. I've tried publishing the changes in GTM instead of just previewing them. I've also tried setting the trigger as custom dataLayer events just to see if they fire and they do not.
Had the same issue. Initially there were ad-blockers in place which prevented the script injection. There may be some policies which are prohibiting to inject scripts in your project too..
Also double check that you are on the correct container and the version is live.
We've implemented Tealium throughout our site, including some newer, single page app (SPA) content. Our devs are new to Tealium, so we're all kind of building the car as we drive it.
I've read Tealium's docs on both single page apps and the standard order of operations. What I don't fully understand is when vendor tags fire on SPA sections. For example, when I first land on a SPA page, I see the HTTP requests indicating the tags have fired (We haven't disabled the initial page view event yet). But as I navigate around that app, triggering the manual link/view events that the devs implemented in the site code, I see those events being logged but the HTTP requests from vendor tags are inconsistent or not-existent. For example, we have a Google Ads tag that appears to fire with each of these events, but we also have Microsoft Ads tag that does not, despite both tags' Load Rules being configured to load on all pages.
Can anyone confirm whether utag.view() and utag.link() fire vendor tags when called? If I'm misunderstanding a piece of the implementation, I'd be grateful for a clarification. Thank you :)
As a general rule, Tealium knows nothing about your app's events. Like most tag managers, it'll default to firing off a utag.view() indicating a new pageview once the page has loaded, but in an SPA app, that happens once and it's got no hook into your router to understand future navigations.
Rather, it's on you to instrument your SPA and augment the router so that when a new route is successfully rendered, you call a utag.view() and when other actions occur that you want to track, you make the appropriate utag.link() calls as Tealium will not do this for you.
My company has an angular component library that we want to track usage of. This means that multiple developers will us it on multiple domains. I have included a single tracking id and am dynamically loading the gtag.js library when components are loaded. This works on the main domain but the tracking isn't logged in the dashboard. Does anyone know of the settings required to make this possible? Also I am not trying to link any pages or sessions, just have unique tracking per application.
It turns out that I had upgraded one gtag emit call but a second one was still in the ga syntax and wasn't registering in the dashboard.
I have a SPA here and I´m wondering what should I do to get it properly indexed by Google bot.
I read a lot on multiple views angularjs apps (hashbanging and that stuff) but my app has just one view / controller.
Should I create an html copy for each of the items being shown and link them together?
Thanks in advance,
Ariel
In AngularJS, you can compile templates & cache them using a variety of techniques - you'll need to write a process or build into your runtime logic building these templates & binding them to data, writing them out as static files.
Google allows for special handling based on user-agent. I have a friend who says, "This was called cloaking, before Google owned Angular." This is true. You need to setup server logic that re-directs any Google-bot user agent (or other search engine agents you care about) dynamically to one of these static "Search-Bot Friendly" pages.
Although this is more work, there are obviously bonuses to being able to maintain a set of content that search crawlers "see" and a (potentially different) set of content consumed by real users.
This is also the reason why AngularJS as a client-side framework quickly falls down the rank list when search visibility is a primary objective of the project.
I have a backbone app (a blog) displaying different articles we can share on many platforms.
I try to use open graph with google and facebook, i update the properties in the router just before rendering the view.
But the thing is, when the scraper reach the app, it doesn't get the meta properties, i don't know if it doesn't execute javascript or if it's too fast, but if i set up some default meta properties directly in my single page it works.
However i need to update the meta properties about the url (each article has their own meta properties).
So, is it possible to use open graph with backbone.js ?
I am struggling with the problem and it seems Facebook is not running javascript in their end. There is no way, but creating separate page in your server for stuff you want to share on Facebook and include all meta tags statically in those pages.
There are services that will render javascript generated page for SEO purposes. Check out https://prerender.io
An alternative is to have your server populate the <meta> tags before the page is served.