The Website Optimizer Experiment Management API allows for programmatic creation and modification of Website Optimizer experiments. Simply put, it allows Website Optimizer experiments to be created outside of the Website Optimizer interface.
If you are a developer of a content management system (Drupal, Zoomlah, etc), blogging software, or shopping cart, you can use the API to incorporate the Website Optimizer experimentation into your own platform. By doing this, you can enable your users to use website testing on their own sites.
If you are a website owner or developer who wants to simplify testing on your site, you can leverage Google's robust testing platform rather than building your own tool. Website Optimizer takes care of splitting traffic, runs the necessary statistics calculations, handle sites of any size.
If you are a very advanced Website Optimizer user, you might also find the Experiment Management API useful for quickly creating tests outside of the Website Optimizer interface.
We have resources to help you get started quickly with the API. We recommend you first read our Getting Started Guide.
We have set up a Google Group for discussing the API. The group is open to anyone and is read by Google employees and other experts on the API. Visit the group at http://groups.google.com/group/gwo-api. In order to post to the group, you need to be a member.
Both the API and the Website Optimizer interface use the same servers, so there is no difference between experiments created using either tool.
The Website Optimizer Experiment Management API only allows for creating and modifying Website Optimizer experiments. Reports are still accessed by signing into the Website Optimizer account.
Yes. If you do not have a Website Optimizer account, you will need to create one.
Like the Google Analytics Data Export API, the Website Optimizer Experiment Management API is provided at no cost.
While in Labs, our API will remain subject to change. In most cases, we will provide at least one month advance notice to migrate to new API releases before we remove or deprecate old functionality. In unusual cases—such as where our internal systems are affected or where we are unable to provide a high level of service to our end users—we reserve the right to make changes on shorter notice. As usual, usage of our API is governed by our Developer Terms of Service.
The API has quota limits to ensure we provide everyone with an equitable level of service. For more information, see the section on quota limits.
A 503 response means that we can't process your request right now and you should wait and try again later. A common reason for this is that you have exceeded your quota limit. Please see the quota limit policy for more information.
A 500 response means we've encountered an internal error. Don't worry: we log and monitor all errors. If you want to, you can also share your results with us in the Website Optimizer API Google Group.
A 400 response is most likely the result of a bug in your code. In most
cases, this is due to an invalid parameter in the URL query string.
For example, you might have dimension parameters listed twice, a malformed
regular expression in the filters parameter, or a start date that precedes
the end date. Check the body of the HTTP response for additional information.
|
