With all of these new goals to configure, it's a good practice to use your goal sets to group your goals strategically. For example, you might use Goal Set 1 to track a set of e-commerce related goals such as Successful Purchase, Added Item to Shopping Cart, Deleted Item from Shopping Cart, and things of that nature. For your next set, you might want to track interaction goals such as Newsletter Signup, Followed us on Twitter, Logged In, etc... The sky's the limit, but make sure to consider how you'll want to use your reports when configuring your new goals.
New Goal Types - Engagement Goals
Time on Site allows you to specify a greater than or less than value of time spent on your site as one of your goals. The following goal would fire once a visit passes five minutes in length:
As always, if you'd like a monetary value to be assigned to any of your goals and used in cost and revenue calculations, just enter the amount in the "Goal Value" field.
The number one reason people give us for not upgrading to the latest version of WordPress is fear that their plugins won’t be compatible. As part of our continuing efforts to make WordPress core, plugin, and theme upgrades as painless as possible, Michael Adams developed and launched a beta of a new “Compatibility” feature in the plugin directory, powered by your votes. When viewing a plugin in the directory, select a WordPress version and a plugin version from the drop-downs. If there has been feedback about this WordPress / plugin version combination, we’ll show you what percentage of responses marked that combination as compatible vs how many marked it as incompatible.
If you log in, you’ll be able to help us gather this information! Just select a WordPress version / plugin version combination and click the “Works” or the “Broken” button. Please note that this shouldn’t be used to report minor issues with a plugin. You should mark a plugin as “Broken” only if its core functionality is truly broken when run on the specified WordPress version.
Right now we’re just in information gathering mode. So get out there and vote! Don’t just vote on broken plugins… cast a “Works” vote for every plugin that works on the version of WordPress you are using. This can help improve the signal-to-noise ratio in our data and prevent a few mistaken “Broken” votes from weighing too heavily.
For developers, we’re now including this data in our API. The plugin_information
action now returns a “compatibility” member with the multidimensional array format:
array( {WP version} => array( {plugin version} => array( {% of reporters who say it works}, {# responses} ) ) )
If the API knows which version of WordPress you are using (for example, if you are making this query using the plugins_api()
function from with WordPress), the API will only return compatibility information for your version of WordPress.
Eventually, we’d like to gather this compatibility feedback from within WordPress, allowing you to vote directly from your plugins admin screen. The ultimate goal is to use this information to inform you of plugin incompatibilities with a new version of WordPress during the upgrade process. For that to be useful we need a large set of high quality compatibility data. Start voting!
十月 2009 | ||||||
一 | 二 | 三 | 四 | 五 | 六 | 日 |
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |