BLOG

How to Install and Debug the Facebook Pixel using Google Tag Manager

Published August 24, 2018
As a digital marketer, juggling a variety of advertising platforms is just a part of everyday life. From Google Ads and Facebook to Twitter, LinkedIn, AdRoll, and more, you’re used to having a lot on your plate.
 
But when you have to worry about installing performance-tracking tags and pixels on your website so you can optimize for each platform, things can get overwhelming. Not only do you have to add this time-consuming task to your IT team’s already long to-do list, but it creates a lot of additional code to manage, maintain, and update.

Landing Page Tracking with Google Tag Manager

Published September 18, 2015
As a Digital Marketer, you often need to create special-purpose landing pages – most commonly for digital advertising campaigns or email marketing campaigns.

How to Install Google Tag Manager in WordPress

Published August 29, 2015
You probably know that Google Tag Manager is a great and free way to manage all of the tracking code needed on your website.
What you might not know, unless you are proficient with modifying WordPress Themes, is how to install Google Tag Manager in a WordPress site.
Fortunately, it is not that hard. You can get it done in less than 10 minutes. Here’s how.

 

 

ALSO IN THIS BLOG

Remember how your mom told you not to stand too close to the television because it might hurt your eyes?
The same rules can apply to data. If you’re too close, you may miss the patterns and trends that are crucial to understanding your website’s performance. You can’t judge a site’s performance looking at data in the bubble of a single day, you must consider any day’s traffic compared to the days before and after.
Google Analytics makes it fairly easy to analyze trends over long periods of time. But it also allows you to stand right in front of that TV, to look at more granular levels of time, right down to the hour.
There’s a better way to get that close to the data, without burning your retinas. We’ll cover how to analyze traffic effectively in today’s post.

 

 

When the client first came to you, you talked up the value of Google Analytics. You emphasized the importance of seeing where your traffic was coming from. You went on and on about how Google Analytics can show traffic sources to pinpoint whether people came from search, social media or a specific site referral, and how valuable this data was. You sold them on it, so much so that your client looked forward to receiving that first report, the magical day when they would finally understand where visitors were coming from.
But then the report came, and it looked like this:

 

 

It showed that 10% of your client’s traffic came from “(direct)/(none)”. What does this label mean? How do you explain Direct traffic to your client? Better yet, how do you explain “none”?
Let’s take a closer look at understanding Direct traffic in Google Analytics and how we can address it with clients.
One of the most exciting and important aspects of digital marketing is the ability to understand exactly how your customers are finding you. It informs every single part of integrated campaigns and helps determine which efforts are working and which ones need to be revisited. Google Analytics allows you to zero in on the performances of different marketing channels to evaluate everything from brand awareness to social media messaging. To get the most insight from that data, it’s crucial to understand exactly how Google sorts your traffic.
Channels in Google Analytics are high-level categories indicating how people found your site. While the Source/Medium report shows you in more detail where people came from, Channels are broader, more “user-friendly” names lumping visits together in buckets useful for high-level reporting categories.
For instance, Facebook Sessions often show up in multiple ways in the Source/Medium report. They may appear as facebook.com, m.facebook.com, and l.facebook.com, all of which are variations of the same source. The Channels report will include all of these in the Social bucket, so you can see less granular, aggregate numbers on social media performance.