We’re often asked by our audience … “I know I should be testing, but which platform should I use?” There is no one right answer to this question, so I’ve been writing a series of blog posts with quick guides to online testing and optimization solutions.
This latest post will be our quickest quick guide because it is not about any specific branded tool, per say, but rather internal proprietary tools…which vary widely. That said, I wanted to cover a few basic considerations.
When does it make sense to use internal proprietary tools for testing?
Here are a few points to consider…
- More effective when using your own tool, since with other tools you’re calling a third-party server
- Ability for your own team to troubleshoot rather than waiting on support
- This will require servers and internal resources to build/manage
Safety/privacy of data
- Must secure internal servers and encrypt data
- Encryption may take longer development time
Can develop the platform in whatever code development feels most comfortable
- Prevents the need for purchasing only product X due to its development language
- Ability to support/build tool with resources already on staff
- Control over added features and functionality
More likely an option when there’s an established Content Management System (CMS)
- Adding extra features to an established CMS is sometimes easier than also purchasing and installing an additional testing platform
- The CMS will provide a pre-created administration side to display reports and control permissions
- Adding features to a CMS for testing ability is quicker than building an entire testing platform
We’d love to hear some customer reviews as well. Use the comments to share your experience with internal proprietary tools. And stay tuned to this blog as we provide quick guides for more online testing solutions to help you choose a platform that is best for your individual situation.