• Austin SEO
    • TastyPlacement in the Press
    • Meet the Team
  • Blog
  • Services
    • SEO Services
      • WordPress SEO Service
      • Magento SEO Services
      • Conversion Rate Optimization
      • Why Google Certification Matters
    • PPC & Adwords
      • Adwords & PPC Management
      • Remarketing Services
      • Display Ad Management
      • Facebook Ad Management
      • Pinterest Ad Management
      • Google Ad Grants Management for Non-Profits
      • Adwords App Install Ad Management
      • Product Listing Ad Management
    • Analytics & Data
      • Analytics and Monitoring
      • Google Tag Manager Experts
      • Data Studio Development & Consulting
    • Social Media & Local Marketing
      • Social Media Marketing
      • Local SEO
    • Web Development
      • Mobile Website Design
      • WordPress Development
  • Case Studies
    • SEO Case Studies
      • SEO Case Study: We Beat Lowes, Then We Beat Home Depot
      • SEO Case Study: Total Domination in Houston for Medical Provider
    • Analytics Case Studies
      • Case Study: Updated Design Yields 43% Increase in Conversion Rate
      • Case Study: PPC Optimization Yields Tripled Conversion Rate
    • Social Media Case Studies
      • Social Media Case Study: Hundreds of New Customers From Core Facebook Campaign
  • Portfolios
    • Display Ad Portfolio
    • Design Portfolio
    • Infographic Portfolio
    • SEO Testimonials
  • Contact
    • New Customers: Get to Know Us
    • Customer Service & Support
    • Referral Program
    • SEO Training Seminars
    • Job: Paid Search/PPC/Adwords Analyst
    • Job: Local Digital Marketing Specialist
    • Job: SEO/Marketing Junior Analyst
    • Privacy Policy & Terms of Use
  • Menu Menu

Pro Tip: Track Your Website Goals in Google Analytics (and More)

May 19, 2021/0 Comments/in Analytics/by Michael David

Tracking Website Goals In Google Analytics Should Not Be Optional in 2021 & Beyond

As TastyPlacement enters its 14th year of operation, we remain astounded how many new clients come to use with improper Google Analytics installations. We see it all, from mangled Google Analytics Snippets, to doubled Analytics Snippets. Far more common though, are websites without Goal Conversion Tracking installed–which is like going to battle with a blindfold on.

But don’t believe me, look what Google says about it:

  • “Defining goals is a fundamental component of any digital analytics measurement plan.”
  • “Having properly configured goals allows Analytics to provide you with critical information, such as the number of conversions and the conversion rate for your site or app. Without this information, it’s almost impossible to evaluate the effectiveness of your online business and marketing campaigns.”
  • You can read the full article here on Google’s support website.

Goal Tracking Defined

Goal Tracking, or Conversion Tracking, is very simple: when a user visits your site, Goal Tracking is a measurement of whether that user takes a specific action such as:

  • Dialing your company phone number
  • Filling out a contact form
  • Engaging with a live chat or chat bot
  • Making a purchase

It’s vital to track goals: with goals tracked you can now know valuable, actionable information such as:

  • Which of your paid keywords generate leads?
  • Do Facebook ads generate sales or leads to the same extent as Google organic traffic?
  • What time of day are users most likely to buy?

Goal Tracking Gives You More than Just Actionable Information

Now, let’s take it even farther. Google Ads can, with properly configured Goal Tracking, act on its own behalf using artificial intelligence to improve ad performance and increase Conversions.  More on this in a future article.

How to Recognize the Indeed.com Robot and Other Unwanted Visitors

April 2, 2019/0 Comments/in Analytics/by Michael David

The longer you stare at Google Analytics, the more you see things that don’t make sense. Sometimes the irregularities pop right out, users who crawl every single page exactly once in a single session, or users who load up pages that can’t possibly exist a couple times every month. Most likely these abnormalities are caused by robots, those sneaky denizens of the inter-webs, teeming in the millions and doing their masters’ bidding. Mostly the robots don’t execute javascript, so they don’t manifest in Google Analytics. And you can filter out a lot of the robots which do use javacript by clicking the “exclude known bots and spiders” box in your GA view settings.

Why this box wouldn’t be checked by default is anyone’s guess. Between views where you forget to check off that box, and robots which get around Google’s filters, you will see a lot of this fake traffic once you start to look.

A few months ago we noticed one robot in particular which stood out from the others. Instead of hailing from Russia or the Philippines, or some other sketchy location, it seemed to originate from right here in Austin, Texas (also an admittedly sketchy location). The pattern was a single user loading all of the pages on the site one right after the other.

This crawling seems to have started within the last year or so, and the declared user agent was an outdated version of Firefox. Once we made a segment which isolated the stats we found it everywhere. It was like that scene from Independence Day where Jeff Goldblum discovers that there’s an alien signal inside all the telecommunications satellites.

Drilling down to all the dimensions allowed by Google, we found the smoking gun under Audience –> Technology –> Network.

We believe the robot is how Indeed.com gets some of its job listings. It scrapes the entire dang internet to find those sites where the companies can’t be bothered to post directly to Indeed.com.

Here’s the stats for identifying the Indeed bot:
City: Austin or sometimes Denver
Network: indeed inc
Nework domain: cyrusone.com
source/medium: direct/none
Browser: Firefox, 38.0, 1024×768

If Indeed has the hardware and expertise to scour the digital world with a fully rendering bot, you think they could also make it not execute Google Analytics. Just saying.

A Few Other Robots of Note in Google Analytics:

New York Mystery Robot

Appears to be probing sites for security flaws. Deliberately loads 404 pages with mysterious hashes in various subdirectories, such as /blog/aHQtZ3JvdX . It’s declaring the browser to be a year-old version of Chrome. One theory is the hashed 404 pages load up remote shells. Or maybe that’s just being paranoid. Nearly every site has dozens of visits a month.
City: New York
Network: microsoft corporation
Nework domain: unknown.unknown
source/medium: direct/none
Browser: Chrome, 57.0.2987.133, 1280×960

Amazon Bing Bot

Surprisingly pervasive, sometimes visiting every day. Usually loads homepage, but sometimes a gibberish 404 page. It’s really apparent if you visit the Acquisition –> Channels –> Organic page, the keyword “Amazon” shows up right near the top. It’s not clear what they’re trying to do here, there’s no obvious spam message, and they’re not crawling much content.
City: Santa Clara/Anaheim/New York
Nework domain: paloaltonetworks.com, unknown.unknown, keznews.com
source/medium: Bing/Organic: keyword “Amazon”
Browser: Internet Explorer 8, 800×600

Weird Brazil Traffic

It’s probably no surprise that if you’re getting Brazilian traffic on a Texas home-services site, that the Brazilian users are probably not actual prospect customers. A variety of cities in Brazil are the homes to bots which methodically crawl all a site’s content.
City: Itacoatiara (Brazil)
Nework domain: sovereignease.com
source/medium: direct/none
Browser: Chrome, 52.0.2743.116, 1920×1610

City: Santarem
Network Domain: ip-158-69-167.net
Source/Medium: direct/none
Browser: Chrome

City: Maraba
Network Domain: ip-66-70-225.net
Source/Medium: direct/none
Browser: Chrome

Let us know if you see any interesting bots crawling your sites!

Analytics Tutorial: How to Segment Out Time Zones & Regions

August 30, 2018/0 Comments/in Analytics/by Michael David

Analyze your data for particular parts of the country to make better advertising decisions

This task came up recently when we were analyzing a particular PPC campaign–one of our own, actually. We run some remarketing and display campaigns throughout the US and Canada. We are always looking for hour of the day optimization (dayparting as it was called on Madison Avenue). However, when we ran an hour of the day analysis aren’t we looking at, say, 12 noon in Chicago and 10am in California?

This would seem to muddy the data: we are looking for particular hours of the day when website conversions are strongest, and since it isn’t the same time of day everywhere on a continent, we want to separate and segment the data.

Google Analytics “Hour of Day” Report

Google Analytics Hour of Day report shows us what we need: aggregate Adwords visitor data segmented on a 24-hour graph. We’ve set the following chart with a secondary data point, the Goal Conversion Rate:

 

Of course we care about conversion rate–that’s why we run ads, to get customers to reach out to us for further consultation.

And we can see from the chart that we’ve got a mixed conversion rate throughout the day. Keep in mind, we have our analytics set to (and have a headquarters in) the Central Time Zone in Austin, Texas. We like our conversion rate at 12 noon and 2pm, and clearly the conversion rate trails off in the evening after 4pm/5pm.

But even with this valuable data, our 12 noon is 1pm on the East Coast, and 12am on the West Coast.

Let’s Increase Our Accuracy With Segments

We want to see our hour of the day report for only those users actually in the same time zone. To do this, let’s create a custom segment in Google Analytics.

1. At the top of any report in Google Analytics, look above the chart and click “+ Add Segment”, you’ll find this right next to a button titled “All Users”. You’ll see the segment selection window:

Note that “All Users” is already selected in the segment selection window. That’s because technically, “All Users” is a segment, it is simply a segment with no filtering that allows all users in.

2. We could select an existing segment, but here, we’ll create one. To do so, click “New Segment”.  As a heads up, we are going to create a segment based on states that exist within the Central Standard Time Zone. Some states bleed into neighboring time zones, so we’ll fudge it. Here’s the screen where we create our segment, with a few fields filled in:

We’ve gotten started a bit with the previous screenshot. We’ve named our segment “CST Zone States”. Next we’ve made selections to the “Location” fields. “Region” lets us segment by states, and “Matches Regex” lets us use regular expressions to add states in series, with each state separated with a “|”, the pipe character. To add most of the states from the central time zone, you can enter the following into the Location/matches regex field:

Texas|Illinois|Oklahoma|Louisiana|Mississippi|Alabama|Kansas|Arkansas|Missouri|Indiana|Minnesota|Wisconsin

With this same technique, you can create segments that group cities together, group states together, or simply isolate particular geographic locations. Google Analytics Segments are very powerful tools and are commonly used by the best and the brightest.

Let’s Apply Our Segment to the Same Report

And when we are done with our segment, we simply click “Save”. Here is our new hour of the day conversion report.

A few facts become immediately apparent. First of all, we have a more stark difference between high-converting times during the work day and after hours. In fact, the period of 17:00 (5pm) to the workday morning is almost totally dead.  Keep in mind that when you work with segmented data, you might be substantially reducing your data set. In our case, we were now looking at only 30% of our total PPC traffic, and 1% or our total website traffic. If you over-segment, you’ll have tiny data sets and your insights won’t be meaningful.

Get Creative With Google Analytics Segments

You can do a lot with segments–essentially anything tracked in Google Analytics can be isolated and grouped with a segment. Just imagine: you can segment mobile users in Florida that arrived to your site via organic traffic. We use about 60 custom segments in our reporting to clients.

 

Instructions: Connect GMB Insights to Google Data Studio

October 12, 2017/0 Comments/in Analytics/by Michael David
Read more

Google Maps/My Business Insights in Data Studio [SOLVED]

September 22, 2017/0 Comments/in Analytics/by Michael David
Read more

How To: Install Google Analytics Dynamic Remarketing on Shopify

August 16, 2016/12 Comments/in Analytics, PPC/by Matthew Bey

Intro to Installing Dynamic Remarketing on Shopify

Before we get started, let’s make one thing clear: The instructions below are only applicable to those of you wanting to set up Dynamic Remarketing through Google Analytics (GA).

Before We Begin

As with any Remarketing Campaign, make sure the following steps are completed before you continue:

  • Enable “Remarketing” and “Advertising Reporting Features” in Analytics
  • Link your AdWords and Analytics accounts
  • Link your AdWords and Google Merchant Center accounts if you’re in the Retail vertical

 

Once you have completed the above steps, you’re ready to get started with the fun stuff!

Next, Create Custom Dimensions in Google Analytics

Next, you will want to create custom dimensions in Analytics using the attributes for your specific vertical. In our example, we are working with the Retail vertical, but you can find a complete list of verticals and attributes here.

Google Analytics Custom Dimensions

Add Custom Dimensions to Your Shopify Site

You’ll want to make sure that these dimensions are added to the code of your Shopify site. This ensures that when potential customers are served your Remarketing ad, they will be shown the exact products that they viewed on your site.

If you’re in the US, you shouldn’t need to change any part of the following code, however, if you’re in the UK, you will need to replace “US” with “GB.”

Shopify Dynamic Remarketing Attributes

 

 

 

Now the big question: Where to paste it. Intuitively, you would think it would naturally go in the “Add Custom JavaScript to Analytics” box on your store preferences page. We tried that too, but quickly found that the custom dimensions were not populating in Google Analytics. To get everything running nice and smooth, you will want to follow these steps:

  1. In your Shopify dashboard, select “Online Store”
  2. In the themes tab, click the box of 3 dots in the top right corner
  3. Select “Edit HTML/CSS”
  4. Click theme.liquid in the Layout folder
  5. Scroll to the very bottom and paste your code directly after the closing body tag

Where to Paste Code in Shopify

Congratulations! You’re just about ready to start showing all of your competitors what a digital marketing wizard you are.

Create a New Dynamic Attribute in Analytics

Assuming you already have your Remarketing audiences set up in Google Analytics (if not, learn how to set up Remarketing Audiences here) the last step is to create a new Dynamic Attribute in Analytics based on your business type.

To do this, go to the Admin tab of Analytics, under Property, select ‘Audience Definitions’ then ‘Dynamic Attributes.’ Here you will click “+New Attribute” and select your vertical. For Retail, you will want it to look like this:

Dynamic Attributes

Once you have completed this step, click save, and you’re all done! Go ahead and start building out your Dynamic Remarketing campaign in AdWords and watch the revenue pour in. Sit back and relax, you’ve earned it champ.

If you get stuck…

If you’d rather get pro help with your Product Listing Ads Management, think about reaching out to Tastyplacement; we offer these services. Not convinced of our awesomeness? Check out our PPC case study, and you will be.

How to Install Google Analytics on Your WordPress AMP Content

February 22, 2016/0 Comments/in Analytics, Mobile SEO/by Matthew Bey

In the last post we talked about how to get AMP working in WordPress and how to get it optimized for the Accelerated Mobile Pages search results. Today we’re going to talk about how to get Google Analytics working on the AMP content. We’re huge GA fans, and if we’re not tracking the traffic for our site, we really wonder why we’re doing it in the first place.

Google recommends that you create a new property for your AMP pages. The analytics library for AMP doesn’t have all the capabilities of a full-scale GA snippet, so there would be a bit of apples and oranges if you put that traffic into your main account. Also, there’s not going to be much traffic shuttling between the two versions of your site. There will be no traffic going from the real site to the AMP templates, and any traffic coming off the /amp pages will have only one source: Google mobile search.

Just like the logo we did in the previous blog post, you’re going to insert the Google Analytics onto your page using hooks dropped into functions.php. The AMP guidelines only allow pre-vetted one-size fits all javascript, which means you can’t just drop the normal GA snippet into your head. You will add Google Analytics using the “amp-analytics” tag, which you customize to your account using JSON.

Which is to say, copy and paste the code below and replace the “UA-xxxxxxx” with the Google Analytics ID for your new property, and that should do the trick.

//////////////adding analytics to AMP///////////

add_action( 'amp_post_template_head', 'xyz_amp_add_analytics_library' );
add_action( 'amp_post_template_footer', 'xyz_amp_add_analytics' );
function xyz_amp_add_analytics_library( $amp_template ) {
$post_id = $amp_template->get( 'post_id' );
?>
<script async custom-element="amp-analytics"
    src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>
<?php
}
function xyz_amp_add_analytics( $amp_template ) {
    $post_id = $amp_template->get( 'post_id' );
    // see https://github.com/ampproject/amphtml/blob/master/extensions/amp-analytics/amp-analytics.md for more on amp-analytics
    ?>
 <amp-analytics type="googleanalytics" id="analytics1">
<script type="application/json">
{
  "vars": {
    "account": "UA-xxxxxxx"
  },
  "triggers": {
    "trackPageview": { 
      "on": "visible",
      "request": "pageview"
    }
  }
}
</script>
</amp-analytics>
    <?php
}
/////////////end adding AMP analytics////////////////

I haven’t been seeing the GA AMP tag showing up in the Tag Assistant extension, so you will need to look at this property through the real-time viewer to see if it’s actually tracking.

How to Implement and Optimize AMP in WordPress

February 22, 2016/1 Comment/in Analytics, Mobile SEO/by Matthew Bey

Do you have Accelerated Mobile Pages working? Unless you’re a major news outlet like The Guardian, you probably don’t. In this post, we’ll talk about what AMP is and what it’s not, how it will be hugely important for SEO (or totally irrelevent), and lastly how to get it working on your own WordPress site. And in the next post we’ll cover how to install the analytics, which will answer the question which is hovering sword of Damocles-like above this whole project: Is AMP worth the trouble? Or is it another crazy scheme like Rel Author which won’t catch on?

Accelerated Mobile Pages: Possibly a Big Deal

Starting on Wednesay, February 24th, two days from the writing of this blog post, Google will start presenting AMP in its mobile search results.

First, let’s remove the two major misconceptions that the name “Accelerated Mobile Pages” has already given you and everyone else. AMP is absolutely not a way to speed up your site’s load time. In fact, AMP is a tool for bypassing your site’s speed entirely. Second, AMP is not a way to deliver mobile content to your users and it’s not the newest successor to responsive design.

Accelerated Mobile Pages allow Google to present extremely fast content through mobile search. If you’re not on a mobile device, Google won’t show you AMP content. And to ensure the fastest possible loads, Google will cut you and your second-rate hosting out of the equation entirely by caching your AMP content on Google’s own servers.

So basically, you’re jumping through hoops to give Google content to present to their users, through their hosting, using their stringent quality standards, and without the design and features that you’ve worked so hard to implement on your site.

Take a look at this very post in AMP format, presuming you’re not doing so already. All you have to do is type “/amp” at the end of the URL and go:
https://tastyplacement.com/how-to-implement-amp-and-google-analytics-in-wordpress/amp
Are you back? Doesn’t look like much is going on, does it? It’s supposed to be simple and cookie-cutter because everything here is about speed.

What Does AMP Mean for SEO?

If your site doesn’t pull any search traffic for the terms which provoke AMP search results, then this won’t amount to anything. If Google displays AMP results for your keywords, then it means choice rankings right at the top of the page. If there’s anything which is more of a no-brainer for SEO than automatic #1 rankings for a sizeable chunk of your organic traffic, please mention that in the comments.

At the moment, the AMP results demo only seems to show for very current news topics. You can expect that to expand as more publishers push into Accelerated Mobile Pages. Try opening this link in a mobile device to see it in action.
AMPresultsDemo

Getting AMP Working

The first step is to get the official AMP plugin for WordPress installed on your site. The team working on this piled on a bunch of updates under the wire before the big day. Just last month it gave some pretty raw results, with broken code displaying visibly on most pages.

Currently, the plugin only works on posts. It will not do regular-old pages or archive pages or anything like that. And it doesn’t have to. Remember, the mission for AMP is pretty narrow right now. It’s all about delivering content fast for mobile searchers and they won’t need any of that stuff.

The plugin is going to do all the heavy lifting of making the meta-tag markup work and having most of the content validate. You just need to make it look good and fix anything overly ugly.

Sprucing It Up

Out of the box, the AMP template for WordPress is pretty vanilla, but that’s kinda the point. You will want to customize it with your logo. The developers of the plugin want you to make your changes using hooks. This is the WordPress way and in the long term it will be the most future-proof strategy.

The AMP template will only display a 32×32 image. You may already have a favicon file of this size, but if not, shrink down your logo and then upload it to the WordPress media library.

To add that image, drop this function at the bottom of your theme’s functions.php file:

///////////////adding the site icon to AMP///////////
add_filter( 'amp_post_template_data', 'xyz_amp_set_site_icon_url' );

function xyz_amp_set_site_icon_url( $data ) {
// Ideally a 32x32 image!!!!!!!!!!!!!!!!!
$data[ 'site_icon_url' ] = get_site_url() . '/wp-content/uploads/YOURLOGONAMEHERE.jpg';
return $data;
}

If you want to make more sweeping changes, you will have to put together a custom template, but that’s probably not worth the effort until you know how much traffic you’re getting through the AMP initiative.

Troubleshooting AMP in WordPress

Most likely there’s going to be some problems. The AMP plugin broke our front page because we had our site name saved with a couple of capital letters. I found that the Digg Digg plugin broke AMP. Our caching plugin also caused strange results. Like usual, plugin conflicts will be the source of most of your problems.

To check to see if your page validates correctly, just add “#development=1” to the end of your AMP URL in Chrome. Then right-click, inspect element, and click on the “console” tab. If you haven’t made any mistakes, then you’ll get the all-clear validation:
AMPvalidationconsole
If you don’t, then you have more work to do.

Once Google has crawled the site, they’ll let you know if any of the pages failed to validate in Search Console.
AMP search console warning

Maximizing Your AMP Traffic

You will notice that the AMP template doesn’t have a menu or footers or sidebars, or all the bells and whistles we expect from WordPress. All this hypothetical traffic from Google mobile search won’t mean anything if you can’t keep visitors on your site. So try adding this code to your functions.php, so any users who get to the bottom of your content won’t be left hanging:

////A little message for the end of AMP pages/////
add_action( 'amp_post_template_footer', 'callToActionAmp' );
function callToActionAmp() {
	$sitelocation = get_site_url();
	?><div class="content"><h3>Get more great infotainment <a href="<?php echo $sitelocation; ?>">on our main site</a>!</h3></div><?php
	return;
	}

And that should more or less have you set up for Accelerated Mobile Pages. Let us know if you get any meaningful traffic from it!

In the next post we’ll talk about how to get Google Analytics working on your AMP pages.

Click to Call Tracking With Google Tag Manager: Tutorial

July 12, 2015/1 Comment/in Analytics/by Michael David

…with a bonus: Mobile Device Detection (updated for July 2017)

Here’s the need: we have a responsive website, as pretty much 1/3 of the web has these days. We love receiving emails through our contact form from customers, and they are easy to track as Goals in Google Analytics and we feel they represent a more interested and more serious purchaser. But we also receive phone calls are those are more problematic: tracking a click to call hyperlink is easy if you assign Analytics event tracking to the click. But a problem arises: if desktop users click on the phone number looking for a contact page (they do), then the desktop user registers an event, polluting your Analytics goal tracking with meaningless clicks. So, can GTM be leveraged to only register mobile clicks on the click-to-call link?

GTM-goal-tracking-phone

So here’s what we want to do with Google Analytics and Google Tag Manager:

  • We want to create a tracking event that registers customer phone calls as an event/goal
  • We want to track only mobile phone clicks, and not errant desktop clicks to keep our data meaningful
  • We know we can do it with Javascript, but we want to do it in Google Tag Manager so all our tags are in one place and so that we can repeat the technique on any site without rewriting and installing the code on every site we work on

Getting Started: Create the Tracking Event (As a GTM Tag)

We assume you have a Google Tag Manager account and have a tag container installed on your site. You’ll create the event in Tag Manager, here’s a link to GTM if you are lazy; of course, you can always hire TastyPlacement for Google Tag Manager consulting if you need, but for now, let’s learn…

To create the event tracking, open your GTM account, navigate to “Tags” and click the “New” button and then select “Universal Analytics” from “Choose tag type”. You want your new tag to look like this screenshot–and you might have to return to these tag parameters to edit it because we haven’t created the “Call Now Click” trigger yet that is shown in the picture: Google Tag Manager screenshot Analytics tag

 

 

 

You don’t need to configure Google Analytics to create the event, Google Analytics will “listen” for our event and store events under “Behavior” and “Events”. Note how our choices of Category/Action/Label appear in our Analytics Account based on the settings above. We want the “Label” to tell us which URL the user was on when they clicked the button; that’s a powerful benefit of GTM that would be a quagmire if coding in javascript. With this little trick, we’ll know which page generated the conversion.

Analytics-event

 

Next, We Want To Fire Our Tag Only on Phones

Key to having good data  is to make sure the event is only triggered when the click is generated on a mobile phone, not a desktop or laptop computer which, obviously, has no phone capability. We can isolate phones among our website visitors by creating a user-defined variable in GTM that records each user’s browser width. Smaller screen width means mobile browsers (in nearly all cases).

Let’s browse in GTM to “Variables”, and in the “User-Defined Variables” section, click the “New” button. At the “Choose variable type” pop-up, select “custom JavaScript”, because we’ll be writing a few lines of code here.

We’ve named our variable “Pixel Mobile Screen Width Test”, and selected “Custom Javascript” as the Type and then entered the following small javascript string:

function () {
 var width = screen.width;
return width;
}

Our user-defined variable in GTM looks like this:

GTM-custom-javascript

 

What this string will do is set a variable based on the user’s screen width. In the next step well set a trigger that is dependent upon the screen width being below a certain pixel size–we want to fire our event only when  Does a narrower screen width necessarily mean the user is on a phone? No, not with 100% certainty, but for our purposes, it’s close enough.

While you’re in the variables section, enable the Click Url variable by clicking “configure” and then the checkbox. For some reason the pre-configured variables aren’t automatically available, you have to manually enable them.

Tying it All Together With a GTM Trigger

Now we tie together our screen width variable and our Google Analytics event tracking with a GTM Trigger to fire the event tracking and register our click in Google Analytics. In GTM, navigate to “Triggers,” then click the “New” button. We are going to create a trigger with the following parameters:

  • Event: Click
  • Configure Trigger: Just Links, Wait for Tags, Max wait time 2000 milliseconds, Check validation
  • Enable When: set this to “Pixel Mobile Screen Width Test” less than 800. That way the tags won’t spring into action unless it’s a mobile device.
  • Now to set when our tag fires: set to “Some Link Clicks” and change the “Click URL” to “matches RegEx” and then your phone number. It may be easier to just match the last four digits of the phone number, because if people have been putting hyphens in the tel:URLs, that will make a regular expression match a giant pain.
  • You might notice the “Page Path” argument–you won’t need that unless you have a specific page on which you do NOT want the tag to fire. In our case, we have some sample code that might have caused errant triggers, so we wanted to exclude that page.

 

 

So, let’s break this all down: under the “Fire On” section, we want to fire the event tracking when the Click URL matches 5125352492, which is the anchor text in our click to call link (our phone number, obviously). We have another condition though, which is that we only want to fire the event tracking when the screen width is less than or equal to 600 pixels, which refers to the user-defined variable we defined above. Save the trigger, and start testing. There are probably other (and better) ways of doing this, but this meets our requirements; it’s reliable and repeatable. Also, our method will work with anywhere we put a click to call button on our site. Maybe we have a link at the top of the page and at the bottom: either link would register as an event as long as the anchor text of the click to call link is the same. Also, I like how we’ve set the event tracking label to show the URL of the page the user was on when they decide to call.

For troubleshooting, you can use GTM in preview mode. Matthew Bey, our operations manager, developed this solution with lots of reference to Simo Ahava’s blog.

Here’s how I feel after completing this tutorial:

images

 

Tutorials & Case Studies

  • Analytics
  • Backlink Strategies
  • Case Studies
  • Infographics
  • Internet Marketing
  • Local Maps and Local Listings
  • Magento
  • Mobile SEO
  • Our Book: SEO for Wordpress
  • PPC
  • Programming & PHP
  • SEO
  • SEO Power Tools
  • SEO Resources
  • Social Media Marketing
  • Updates & News
  • Web Design
  • WordPress

Our Most Recent Tutorials & Case Studies

  • Test Results: How to Stop Google Re-Writing Your Title Tags in the SERPs
  • Pro Tip: Track Your Website Goals in Google Analytics (and More)
  • How to Connect Google DataStudio to MySQL Database (cPanel Flavor)
  • UTM Codes/Tags: A Quick Guide to Tagging Ads Like a Pro
  • Social Media Case Study: Hundreds of New Customers From Core Facebook Campaign

Search

Archives & Tutorial Categories

  • Analytics
  • Backlink Strategies
  • Case Studies
  • Infographics
  • Internet Marketing
  • Local Maps and Local Listings
  • Magento
  • Mobile SEO
  • Our Book: SEO for Wordpress
  • PPC
  • Programming & PHP
  • SEO
  • SEO Power Tools
  • SEO Resources
  • Social Media Marketing
  • Updates & News
  • Web Design
  • WordPress

Austin SEO Company, TastyPlacement

TastyPlacement
4150 Freidrich Ln Ste C
Austin, TX 78744
Tel: (512) 535-2492

Google Maps: Get Directions or Read Our Awesome Reviews

Quick Navigation: Our Most Important Pages

  • Austin SEO [Home]
  • WordPress SEO Service
  • PPC Management
  • Social Media Marketing
  • Analytics and Monitoring
  • Remarketing Experts
  • Conversion Rate Optimization
© Copyright - TastyPlacement. Made in Austin, Texas
  • Twitter
  • Facebook
Scroll to top