Important change to goals
Goals have always been "exact match" by default, and only used any kind of wildcard matching if you specifically added that in. We thought this was the best way to do it but over the years, we've found that the vast vast majority of support requests that have to do with goals are because the user is not using wildcards where they should, usually on the end of the string.
For example, a user might enter "/thankyou.php" as their goal URL, without realizing (or simply forgetting) that these types of pages typically have query parameters too. Then their goal wouldn't work, so they'd contact us, and adding a wildcard on the end was almost always the only change needed. Sometimes a wildcard is needed at the start though as well, but usually just the end.
So, as of now, all goals by default will be processed as if they had a wildcard at the start, and at the end. We know this won't work for everyone of course, so we added a new checkbox to the goal setup page called "exact match". This will force the old behavior, but it is off by default (based on our analysis of how you have setup goals, very few of you will need it). We also expect quite a few people who setup goals but they never worked to suddenly find them start working as if magic has occurred.
While we were at it, we also fixed a few long outstanding bugs: "https://" goals used to not work, and depending on how goals were setup, sometimes they were case sensitive which was quite obnoxious. These are both fixed.
4 comments | Jul 25 2011 2:27pm
For example, a user might enter "/thankyou.php" as their goal URL, without realizing (or simply forgetting) that these types of pages typically have query parameters too. Then their goal wouldn't work, so they'd contact us, and adding a wildcard on the end was almost always the only change needed. Sometimes a wildcard is needed at the start though as well, but usually just the end.
So, as of now, all goals by default will be processed as if they had a wildcard at the start, and at the end. We know this won't work for everyone of course, so we added a new checkbox to the goal setup page called "exact match". This will force the old behavior, but it is off by default (based on our analysis of how you have setup goals, very few of you will need it). We also expect quite a few people who setup goals but they never worked to suddenly find them start working as if magic has occurred.
While we were at it, we also fixed a few long outstanding bugs: "https://" goals used to not work, and depending on how goals were setup, sometimes they were case sensitive which was quite obnoxious. These are both fixed.
4 comments | Jul 25 2011 2:27pm

Recent Comments
Anychance you guys could create a little script widget we could paste on our sites ... chris, May 24 2012 This is great news, but I'm having some problems as it doesn't appear to be working ... Deargeek, May 24 2012 The new EU KEBORD law should be coming in to effect soon, controlling and prohibiting ... Simon Nicklin, May 23 2012 hi iam boy and eager to become friends , with you if you want my love saeed, May 23 2012 Very good on my Galaxy tab! doctormauri73, Apr 01 2012 too bad... force close on checkrom evolution on galaxy s2 pierement, Mar 31 2012 Finally!! Thank you! Daymon, Mar 28 2012 Hi Guys. I haven't been able to access your website all day, and just wondered what ... Alison, Mar 28 2012 My biggest site is on 30 and would rather it was done on a weekday! Weekend is the ... Lee, Mar 27 2012 It's not going to affect tracking in any way, your stats will just unavailable for ... Sean (Clicky), Mar 27 2012