|
Analysis Paralysis
Web Analytics, Search Analytics, Social Media Marketing...It's all moving so fast. There are plenty of other blogs on all sorts of topics, but much of it is still way too complicated. Too much info can cause brain overload leading to a condition called Analysis Paralysis. Let me help ease the burden on your brain. Follow me on Twitter @click2dennis
Sunday, April 19, 2026
Reset your Square password
Saturday, December 20, 2025
Square Password Expired
|
Saturday, April 17, 2021
We're Updating our Terms of Service
|
Sunday, June 9, 2019
We're Updating our Additional POS Terms
|
|
Thursday, April 26, 2018
We're Updating our Terms of Service and Privacy Notice
|
|
Friday, May 27, 2016
We’ve updated our privacy policy and terms of service
These updates provide additional clarity and transparency, making our terms easier to read and understand.
|
|
Wednesday, October 15, 2014
Get your free Square Card Reader
Check out what we've been working on and then sign in to your Square account to request your new free card reader.
|
|
|
Friday, December 28, 2012
Raven Mad to Raving Fans
The past few weeks have been a whirlwind. I have the distinct privilege of representing a platform that is perhaps the closest to Raven tools as a competitor could be. That was never our goal. In fact, we've been much more focused on building a world class- Enterprise SEO platform. Along the way, we also provide some of the same types of reports as Raven. We also go much deeper than Raven- according to our raving fans. The bottom line is, we are positioned very well. We're offering a top notch SEO platform which encourages good, solid, white hat SEO techniques. (HINT! GREAT content that the Search Engines can read and index and that others also find valuable.) This platform is more than just a safe place to land- we've also shown loads of new customers the many additional advantages we offer beyond what they even realized was possible.
Feel free to read more about our Raven Migration Process and our SEO resources including what we feel are "reasonably" unbiased reviews of other SEO solutions.
In an effort to pay homage to my journalist roots, I'll pretend that this article is being written in inverted pyramid style. That is, the most important information is at the top. I haven't posted anything on this blog in quite a while. Lame excuse, but I've been busy starting Analytics SEO in the US and Canada. that's been rather time consuming. I think I've discovered more about the role of this blog in my overall "Voice." If you don't know what that means, please check out some of my much older posts.
Feel free to read more about our Raven Migration Process and our SEO resources including what we feel are "reasonably" unbiased reviews of other SEO solutions.
In an effort to pay homage to my journalist roots, I'll pretend that this article is being written in inverted pyramid style. That is, the most important information is at the top. I haven't posted anything on this blog in quite a while. Lame excuse, but I've been busy starting Analytics SEO in the US and Canada. that's been rather time consuming. I think I've discovered more about the role of this blog in my overall "Voice." If you don't know what that means, please check out some of my much older posts.
Friday, November 4, 2011
Monday, October 17, 2011
Google Analytics Blog: Webmaster Tools in Google Analytics for everyone
Google Analytics Blog: Webmaster Tools in Google Analytics for everyone: Back in June, we announced a pilot program to allow users to surface Google Search data in Google Analytics by linking their Webmaster Tool...
Friday, October 14, 2011
Google Analytics Blog: Webmaster Tools in Google Analytics for everyone
Google Analytics Blog: Webmaster Tools in Google Analytics for everyone: Back in June, we announced a pilot program to allow users to surface Google Search data in Google Analytics by linking their Webmaster Tool...
Wednesday, July 27, 2011
Customizing Omniture
Recently, I've been using Omniture er um I mean Adobe Analytics to extract some rather complex metrics. A few things struck me that I believe I should share. Because I've tried not to blog about too many technical or implementation issues, I thought I would explain how Omniture has been providing more and more new features which are reducing the need to "re-implement" new code in the form of new (jargon alert) e-vars.
New Implementation:
This is really targeted to those of you who (like me) remember the horror stories (or worse yet lived the nighmare) of a painful omniture implementation. Omniture now claims that they are leveraging the experience from deploying SiteCatalyst over 3000 times and have developed best practices which combine business, industry, and technical needs in a process they are calling their Fusion Methodology.
If you are wondering how much easier this is since the "good ol days," consider that Omniture is still suggesting that implementation will take between 4 and 6 weeks- working with a technical contact and includes weekly status calls. It's still not as easy as GA for sure. They have also moved from what they call "G" code to "H" code and offer migration guidelines.
Server Side versus Client Side scriptng also seems to be an important "new" option. It used to be that all the code was on the client side and that was the only option. That is based on hearsay on my part, but my research seems to back that up as well. I never personally implemented under this methodology. The "variables" can now also be contained in a library for reference by the javascript.
This is in no way designed to be an exhaustive list of all implementation methodologies, but suffice it to say that if you have been constantly ruling out Omniture because you don't have the technical resources or the time to implement this robust solution, you may want to look again.
Modifications:
Depending on how your particular instance of Omniture was implemented (and likely WHEN), you may find yourself lacking the flexibility you might "want" in the reporting suite. Traditionally, the problem I've run against is that a website is a dynamic entity which often doesn't resemble itself from one year to the next. Check out the archive.org project and you'll see what I mean. Also- all too often, you "don't know what you don't know" when you first implement any analytics application and that can be a real problem.
Omniture seems to have been adding functionality to help with these issues. Custom dashboards are easier that ever to build and their Excel tools are greatly improved from the past as well. The "Excel Client" has been replaced with the new "Report Builder" which opens up a whole new layer of flexibility. Originally, I was not a fan of "having" to use excel with an enterprise application like Site Catalyst, but it turns out that there is tremendous benefit.
For one thing, most business users are already trained on how to use excel. It's a native environment for them. Also- regardless of your level of experience with Site Catalyst, custom dimensions and metrics can be confusing and you're likely to run into limitations. Report Builder removes many of those limitations. It also provides a means of refreshing the data automatically and can even send reports on a schedule as well.
I recently ran into a situation where the only way I could determine to reasonably get the data I wanted was by using Report Builder. Unfortunately, I needed to request access to Report Builder from the admin of this client- which can sometimes be a problem. It's also kinda hidden- I couldn't find it even when I knew what I was looking for. There doesn't appear to be a way to just download the excel add-in except from the post log in menu and even then, it won't do you much good if you don't have the proper permissions to use it.
Perhaps the biggest benefit to Report Builder is that, based on my unscientific observations, I'd say it would likely dramatically reduce the need to re implement code or even new variables into the library. That removes a ton of hassle and, of course, the need to wait for new data to build- since you can't go back in time with new variables.
Remember- approach your analytics in the right order:
Re implement only if you're sure it's necessary...
New Implementation:
This is really targeted to those of you who (like me) remember the horror stories (or worse yet lived the nighmare) of a painful omniture implementation. Omniture now claims that they are leveraging the experience from deploying SiteCatalyst over 3000 times and have developed best practices which combine business, industry, and technical needs in a process they are calling their Fusion Methodology.
If you are wondering how much easier this is since the "good ol days," consider that Omniture is still suggesting that implementation will take between 4 and 6 weeks- working with a technical contact and includes weekly status calls. It's still not as easy as GA for sure. They have also moved from what they call "G" code to "H" code and offer migration guidelines.
Server Side versus Client Side scriptng also seems to be an important "new" option. It used to be that all the code was on the client side and that was the only option. That is based on hearsay on my part, but my research seems to back that up as well. I never personally implemented under this methodology. The "variables" can now also be contained in a library for reference by the javascript.
This is in no way designed to be an exhaustive list of all implementation methodologies, but suffice it to say that if you have been constantly ruling out Omniture because you don't have the technical resources or the time to implement this robust solution, you may want to look again.
Modifications:
Depending on how your particular instance of Omniture was implemented (and likely WHEN), you may find yourself lacking the flexibility you might "want" in the reporting suite. Traditionally, the problem I've run against is that a website is a dynamic entity which often doesn't resemble itself from one year to the next. Check out the archive.org project and you'll see what I mean. Also- all too often, you "don't know what you don't know" when you first implement any analytics application and that can be a real problem.
Omniture seems to have been adding functionality to help with these issues. Custom dashboards are easier that ever to build and their Excel tools are greatly improved from the past as well. The "Excel Client" has been replaced with the new "Report Builder" which opens up a whole new layer of flexibility. Originally, I was not a fan of "having" to use excel with an enterprise application like Site Catalyst, but it turns out that there is tremendous benefit.
For one thing, most business users are already trained on how to use excel. It's a native environment for them. Also- regardless of your level of experience with Site Catalyst, custom dimensions and metrics can be confusing and you're likely to run into limitations. Report Builder removes many of those limitations. It also provides a means of refreshing the data automatically and can even send reports on a schedule as well.
I recently ran into a situation where the only way I could determine to reasonably get the data I wanted was by using Report Builder. Unfortunately, I needed to request access to Report Builder from the admin of this client- which can sometimes be a problem. It's also kinda hidden- I couldn't find it even when I knew what I was looking for. There doesn't appear to be a way to just download the excel add-in except from the post log in menu and even then, it won't do you much good if you don't have the proper permissions to use it.
Perhaps the biggest benefit to Report Builder is that, based on my unscientific observations, I'd say it would likely dramatically reduce the need to re implement code or even new variables into the library. That removes a ton of hassle and, of course, the need to wait for new data to build- since you can't go back in time with new variables.
Remember- approach your analytics in the right order:
- Strategy
- Implementation (Access)
- Reporting
- Ad Hoc Analysis
Re implement only if you're sure it's necessary...
Thursday, March 24, 2011
Connecting Adwords and Google Analytics
I don't usually blog about "technical" issues, so I'll try to keep this as practical as possible. There are a few really important decisions that need to be made when setting up both Adwords and Google Analytics. Some of these decisions can have traumatic long term implications by missing a few key subtleties.
Beginning with the end in mind, suppose you have a few websites. Many companies do. You're likely to want to manage those websites separately, but you may also want to see them "together" in a roll up. So- many Google Analytics Gurus will recommend setting up ONE account with several "profiles" to see the separate websites. That's the easiest way to set things up. With a few tweaks, you can even see traffic crossing domains and referring to one another.
This can have some unintended consequences. You are also likely to want to run separate AdWords campaigns with separate line item budgets. In order to do that, you'll need at LEAST separate campaigns (because you can only control budgets at the campaign level) but ideally you may even need separate ACCOUNTS.
As of a few years ago, you can now "connect" Adwords and Analytics. that's a really nice feature- you can open analytics directly in adwords, and some other nice features present themselves as well- likely even more to come as this becomes more standard. Here's the problem:
You can't connect one Adwords account with a "profile" you can only connect an adwords account with one analytics account. To make matters even worse, some Analytics accounts are set up with an incrementing "UA" number in other words, you can set
up a new "site" under the same account and your UA structure will look something like this: UA-XXXXXX-1 then UA-XXXXXX-2 and so on. Google Analytics mixes it's metaphors on this one- and they consider these to be the same account but separate profiles- even though there are unique profile numbers assigned separately. Perhaps Danny Sullivan will add this to his list of the 25 Things I Hate About Google and this one may be on it next time.
This may seem rather trivial, but it's pretty interesting the number of things that don't behave properly as a result of this. So how do you fix it? Well- that's the worst part- the only fix is to start new accounts- which of course means starting your numbers from scratch...and this is according to two separate Googlers I've spoken with about this issue. It's kinda one of those things where you need to think carefully about whether there are enough reasons to re-implement. Unfortunately, there may be more and more features only available for accounts that are connected.

If your accounts are connected, You'll get this neat option inviting you to import conversions from Google Analytics into adwords under "conversions." Only problem is, I've tested this a bunch, and it's unreliable. I'm not even allowed to try it again or my boss will get mad at me. He's convinced it's never going to work. Ironically, you can't import Adwords conversions into Google Analytics. It's just not an available feature...so you have build conversions in Adwords and goal conversions in GA...urgh.
So- be careful when setting up your new Google Analytics account and reach out to me if you need info on some of the work arounds we've developed- there out of the scope of the blog.
Beginning with the end in mind, suppose you have a few websites. Many companies do. You're likely to want to manage those websites separately, but you may also want to see them "together" in a roll up. So- many Google Analytics Gurus will recommend setting up ONE account with several "profiles" to see the separate websites. That's the easiest way to set things up. With a few tweaks, you can even see traffic crossing domains and referring to one another.
This can have some unintended consequences. You are also likely to want to run separate AdWords campaigns with separate line item budgets. In order to do that, you'll need at LEAST separate campaigns (because you can only control budgets at the campaign level) but ideally you may even need separate ACCOUNTS.
As of a few years ago, you can now "connect" Adwords and Analytics. that's a really nice feature- you can open analytics directly in adwords, and some other nice features present themselves as well- likely even more to come as this becomes more standard. Here's the problem:
You can't connect one Adwords account with a "profile" you can only connect an adwords account with one analytics account. To make matters even worse, some Analytics accounts are set up with an incrementing "UA" number in other words, you can set
up a new "site" under the same account and your UA structure will look something like this: UA-XXXXXX-1 then UA-XXXXXX-2 and so on. Google Analytics mixes it's metaphors on this one- and they consider these to be the same account but separate profiles- even though there are unique profile numbers assigned separately. Perhaps Danny Sullivan will add this to his list of the 25 Things I Hate About Google and this one may be on it next time.This may seem rather trivial, but it's pretty interesting the number of things that don't behave properly as a result of this. So how do you fix it? Well- that's the worst part- the only fix is to start new accounts- which of course means starting your numbers from scratch...and this is according to two separate Googlers I've spoken with about this issue. It's kinda one of those things where you need to think carefully about whether there are enough reasons to re-implement. Unfortunately, there may be more and more features only available for accounts that are connected.

If your accounts are connected, You'll get this neat option inviting you to import conversions from Google Analytics into adwords under "conversions." Only problem is, I've tested this a bunch, and it's unreliable. I'm not even allowed to try it again or my boss will get mad at me. He's convinced it's never going to work. Ironically, you can't import Adwords conversions into Google Analytics. It's just not an available feature...so you have build conversions in Adwords and goal conversions in GA...urgh.
So- be careful when setting up your new Google Analytics account and reach out to me if you need info on some of the work arounds we've developed- there out of the scope of the blog.
Subscribe to:
Comments (Atom)