I’d never bothered to figure out how Google Tag Manager actually works, because… well, nobody ever asked me to. But today I found myself trying to figure out how to do basic link tracking, and sure enough, the GTM site/webapp was still utterly incomprehensible to me. It was definitely easier to use than before, but it still doesn’t make any sense if you’re a raw beginner. Which I was.
Normally, I hate trying to learn developer skills from videos, but the GTM documentation wasn’t helping me, either. So I finally caved and found Measureschool’s YouTube video, which was both short and subtitled, so I could actually enjoy it at work.
And now I’m not a raw beginner anymore, and can actually use GTM to do stuff besides basic session tracking. And hopefully, Google’s documentation won’t be completely opaque to me anymore.
(Another achievement unlocked this week: genuine object-oriented programming in PHP. Again, nobody actually needed it from me before. This one I could actually figure out from the documentation, though.)
Another new site that took a little longer than the last one to build, due to the somewhat complicated nature of the designed landing pages and multiple forms. Built with JS, PHP, Bootstrap, SCSS, Gulp, and a few other things I’m trying to standardize on.
A new partner site to Stonegate Advisors, this one not only uses the same design, it shares 98% of the CSS. The only big change was the conversion of the news articles from static HTML to a database-driven PHP/MySQL system, which was also copied from another recent site of mine (Vasilko Architectset al). This meant we could get the site up and running from only rough design sketches inside of a week.
This is a fairly basic site content-wise, but it’s the first client site we’ve built on the Bootstrap 3 framework — extensively customized, of course, and fairly heavily optimized. jQuery provides animations when you mouse over project thumbnails, and the project slideshows themselves are powered by Bootstrap’s Carousel component. Continue reading Vasilko Architects→
However, if your application tends to hit the same addresses over and over again — say, to plot the location of restaurants near your business address — it’s possible to cache these lookups in a database. You’ll still be using Google to look up new addresses, but any user hitting the same address twice in the same day will use your database instead of Google’s service. Continue reading Caching Google Maps geocoding lookups→
Solution: Use a server-side script that will retrieve the same data, requesting it over and over if an OVER_QUERY_LIMIT error occurs.