So you want to set up a goal funnel to track the funnel path / dropoff from when a visitor looks at a product detail page through to checkout?
For most ecommerce sites, this is a pretty basic goal and could probably be accomplished simply by setting up a destination goal page of final checkout completion. But some sites, including ours, have pretty extensive resource sections that would deflate that goal conversion rate.
If your site uses a pretty typical url structure such as domain.com/product/productXYZ/482904/product-name-something/ or even includes a category in the url (domain.com/widgets/product/productXYZ/etc….) you could probably get by by simply adding /product/ in the goal path, as Google Analytics accepts this as a valid regular expression and will return all those detail pages that match.
HOWEVER, if you do something crazy like put the product name or id BEFORE a ‘product’ directory, time to use that noggin. In these instances, we need to setup a regular expression to grab all the dynamically created product detail pages.
Let’s use my site’s url structure as an example. Here’s a typical product detail page url:
How would you set up a regex to pull back all projector detail pages? Simple.
You might be thinking – “you idiot, you could have just put /Projector/ in there and it would have done the same thing”. I can’t criticize your thinking as you would be correct – except for the fact that we also have a /Projector/ directory that doesn’t have product detail pages and we don’t want to include them. Besides, I could also add (Projectors/|Screen/|Accessories/) to this regex and pull back groups of specific categories.
Regular Expressions are powerful little monsters. If you want to find out if it’s going to work before saving your funnel, simply go to the content > pages section in Google Analytics and enter your regex snippet in the filter box and see what’s returned.
We know that Google Analytics (free version) has a 10 million hit limit per month, but what we don’t know – for certain, anyway – is how long they store our web visitor data. Several years ago, the general consensus was ‘at least 25 months’, but I can access data from at least the last 4 years and I’m sure many of you can go back much farther.
But this caught my eye when I logged in to GA this afternoon. Is this just another glitch, or do they really plan to hang on to 50 years of data?
Nevermind, this was obviously just a one day glitch. Phew
OH HELL NO.
I logged into my Google Analytics account this morning to pull some basic visitor data for the last 12 months and was shocked to discover that the ability to select a date range that long is no longer an option. In fact, I couldn’t select any date range longer than 192 days. Thinking something must be wrong, I went ahead and switched to a different site under my same account but the date range limit remained. What the hell Google?!
note that anything after July 11th is unselectable…grrrr
I couldn’t find any mention of this on their blog, or elsewhere on the internet as of yet.
Why would Google do this? We already know that for large data requests, Google provides us with a ‘sampled’ set, or a reasonable estimation (which is debatable) of the actual numbers – so why the sudden change? My initial thought is that they want to force more businesses into using their premium service, which has a much higher data limit. But that would be so unlike Google to give us something for free, get everyone to use it, start taking things away and then forcing us to pay to get things back.
Fortunately, it looks like there is NOT a date range limit when using their API – at least not yet. I ran a quick query using Excellent Analytics within Excel and was able to pull back data for the last 18 months no problem.
Are you experiencing the same issues within your Analytics account? If so, sound off below and let me know what you think of this. Do you think it’s nothing to be concerned about, or a massive pain in the you-know-what?
I’ve been trying to implement some structured schema data on our e-commerce site for the last year, but it’s turning out to be a much bigger pain in the ‘you-know-what’ than I’d anticipated. I’m sure many of you can relate, which is probably why we’re not seeing the search results pages with an option to ‘sort by top reviewed’ just yet.
Things may be about to change though, as Google has just recently released their new ‘Data Highlighter’ tool. You can find it in the webmaster tools section, under Optimization.
You can view more information on this tool, which currently only lets you highlight ‘event’ data (BUMMER) , by checking out the video below.
I’ve been neck deep in work (and loving every second of it) since landing the position of ecommerce manager at AVISPL, but I need to chug out a post – even if it’s a quick one - just so I get back into the blogging mindset again.
One of the things we’ve been working on since I arrived is trying to close the loop on transaction reporting, specifically matching up final transaction and revenue numbers to reported phone and web sales.
Google Analytics ecommerce tracking was already implemented, but we weren’t recording the Google Checkout transactions – an easy enough fix, but then we wanted to filter out those transactions vs the transactions that took place on the site.
The problem was there’s no easy way to set up an advanced filter to show only those transactions that went through Google Checkout. The only difference in transactions was the length of the transaction number.
Regex to the rescue! Here’s what you do:
Go to the Goals > Ecommerce > Transactions tab in Google Analytics. In the on-page filter box, edit the filter and select regex, then add this regex code:
You can choose to include or exclude depending on your needs. Then simply save to dashboard and you’re good to go.
Big Whup, you say? You’ve already got the Google + button on your site, you don’t need no stinkin badge?
Well, yeah..you do. Here’s why.
Google Direct Connect.
Once you install this badge to your site and link it to your Google + business page (doesn’t work with personal accounts as of now…bummer), you are automagically added a brand new search feature known as Direct Connect.
To see what this is, just go to Google and start your search with +’keyword’, e.g. +cat. Here’s an example of what you’ll see.
According to Jenny Murphy over at Google, the keywords being pulled in for use are contained in the Title of the Google + business page. So make sure you optimize those business page titles, people.
Another cool feature of this is that once you click on one of the ‘plus’ results, you go right to the Google plus business page, where you’re presented with a pop-up to follow that page. Nice.
Installing the badge on your site is pretty simple, it just requires a few lines of code. You’ll have to sign up for a Google + platform account first, then get the code from the Google + Platform developer page.
As long as you have the Google Plus button already on your site, all you need to do is add one more line of code:
This one is for all the developers who are still pulling their hair out because they can’t get Google Chrome to refresh the page.
I’m thinking that this mostly applies to sites that have an ‘expires-header’ set, but I could be wrong. Regardless of what the core issue is – you just want to refresh the damn page, so let’s get right to it.
Forcing Chrome to Refresh a Page
Step One – Open Up Dev Tools (ctrl + shift + i) or hit f12.
Next, click on the ‘network’ icon inside the dev tools bar, then look for the gear at the bottom right of the dev tools.
You are so close to solving this nightmare now. Click that gear icon and you’ll be presented with a bunch of options (many of which are supremely cool, but let’s not worry about all of that now).
Click the ‘Disable cache’ box under the Network heading – on the right side of the page.
Reload the page - Hallelujah! You’ve just refreshed your cache for this page.