Local Open Sans vs Metronet Tag Manager

Local Open Sans contains copies of Open Sans fonts that WordPress loads from Google Fonts. The plugin deregisters the admin style that loads these fonts remotely and replaces it with a stylesheet that loads local copies of the same fonts. Recommended for development when “fonts.googleapis.com” is adding time to admin pageloads. Not recommended for production (live sites) because it is almost always faster for your visitors to load fonts from Google or to use cached copies.

Integrate Google Tag Manager into your website. The great thing about Google Tag Manager (GTM) is that you are able to gather most of your tracking scripts in one place. You can then fire these scripts whenever you want, specified by the rules you set up. This sounds great, right? Well it is. The only problem is that sometimes it takes a bit of implementing to set these rules up. This implementation can either be setting a dataLayer variable in the dataLayer before the tag manager script is loaded, or pushing a HTML event handler with the variable “event” to the dataLayer when a button is clicked. The problem is that this isn’t always that easy to do when you don’t have the ability/access to add the code to your site. This is where the Metronet Tag Manager plugin shines. It really unlocks the power of the dataLayer so you can easily set macros and firing rules on almost any element. This plugin lets you: Easily add as many dataLayer variables on a per-post and per-page basis as you need. The plugin already gives you six predefined dataLayer variables that you can change/remove or test the system with. These will be loaded on all pages and posts. Set up separate dataLayer variables for pages that aren’t posts or pages (like archives etc). Lets you easily add a HTML event handler to any content link with the GTM TinyMCE button in the WYSIWYG. Lets you add your own unique ID or a class to each content link with the GTM TinyMCE button in the WYSIWYG. Please note that for this plugin to work there is a slight customization that is needed. WordPress doesn’t let you load scripts straight after the opening tag which is where the GTM script needs to be placed to work correctly. To fix this you need to add just after the tag and that’s it. Note, if you are using WordPress 5.2. and up, contact your theme developer and ask them to insert just after the opening body tag of their theme. Here is some code to show the theme developer to make it compatible with Metronet Tag Manager. Please let us know if you have any feature requests or if you have any issues with this plugin. Below are a couple of resources you might find valuable if you are new to Google Tag Manager Official Google Tag Manager website https://developers.google.com/tag-manager/ Tracking Google Analytics Events with Google Tag Manager http://moz.com/ugc/tracking-google-analytics-events-with-google-tag-manager Make Analytics Better with Tag Management and a Data Layer http://cutroni.com/blog/2012/05/14/make-analytics-better-with-tag-management-and-a-data-layer/ Filtering Variables If you choose to place variable values inside percentage signs (e.g., %replace_test%), you can filter these as necessary. Here’s an example: add_filter( 'gtm_replace_test', 'gtm_replace_test', 10, 3 ); function gtm_replace_test( $total_match, $match, $post_id ) { return "replaced with content"; } The filter name is gtm_ with the suffix of replace_test, since that content is inbetween the percentage signs.