This article reviews some best practices for working with SiteSpect.
Best Practices for Using SiteSpect
Copy Helpdesk on all emails to the SiteSpect team.
Organize processes and personnel to fit your needs/resources:
- Create a standard team and process for working through Ideation, Development Cycle, QA, Live Testing, Analytics.
- What team and process to drive ideation?
- What does the dev cycle look like? Who is doing the dev work?
- Generally the more eyes and devices you can have QA, the better.
- Who sets the test to live?
- Who analyzes results? Are you comparing to other tools?
- How is all of this being communicated and coordinated team wide?
Before starting the test build and development process:
- Have clear goals/questions to be answered
- Be careful not to test too many things at the same time
- Use iterative testing to help isolate the changes that are giving you the desired return
- Example of information captured:
- Area(s) of website (page types, line of business, etc.)
- Metrics to capture (add to cart, conversion, subtotal in cart, interaction with elements, etc.)
- Target Audience
- Estimated time to run to reach significance
- Traffic and overlay considerations
- Variations and differences between them
- Screenshots, mockups
- Specifications / Design Guide (fonts, colors, margins, etc.)
- Assets if applicable
Submit CDG for all campaign builds, metrics and other testing components:
- Here is the CDG Template
- Make sure to clearly specify affected pages, elements, and copy. Pictures are usually helpful here.
- Always consider any pre-existing variations in user experience. (Do any users already see a different experience based on location or other criteria?)
QA Best Practices:
- Always QA everything before turning it live
- Preview the campaign on multiple browsers and mobile devices if those are part of the target audience.
- Test any actions a user might perform and verify the variation changes are persisting as expected.
- Try navigating away from and back to the target page.
- Adjust filters/options/input values.
- It is also important to test the campaign across different URLs and page types on your site.
- Make sure the desired experience triggers where it should, and does not trigger where it should not.