By Kevin Plankey
October 30, 2020
There are a number of optimization platforms on the market, each touting its own set of differentiators and benefits. However, they all have one critical similarity – they are tag-based. This is something we talk a lot about at SiteSpect, as our patent makes us the only tagless solution on the market, which provides our customers many capabilities that other tools don’t have. But, what exactly does that mean, and why exactly does that matter? In this blog, we’re going to break down what we mean when we talk about the benefits of SiteSpect’s “tagless architecture.”
What is a “Tag-based” tool?
- User requests a URL
- Request goes to server
- Server delivers original experience
- Request goes back to server
- The correct experience loads
What is a “Tagless” tool?
- User requests a URL
- Request passes through SiteSpect on the way to the server
- Server delivers original experience while SiteSpect modifies it appropriately
- Correct experience loads in browser
The fundamental difference here is that the browser only reads and delivers one experience. This means SiteSpect sites see faster page load time and don’t experience flicker.
What About Server-Side Testing?
Tag-based versus SiteSpect’s tagless architecture also affects server-side A/B testing. Server-side deals with parts of the user experience that don’t happen in the browser, for example algorithms (such as for search results or product recommendations), or product releases. These changes have to happen before the request returns to the server, and therefore they work differently for tag-based tools.
Typically for tag-based tools, server-side testing involves a software development kit (SDK) and installing third-party code into your server stack. This requires developers and regular maintenance. Additionally, server-side tools are usually sold as a separate product, with a separate point of access and separate campaign management.
SiteSpect’s tagless architecture means that server-side testing works the same way that client-side does. Experiments can happen at the origin without any additional code installation. Plus, all of SiteSpect’s capabilities live within one interface, one point of access, and unified campaign management.
The difference between the two methods is fairly straightforward, but can have major effects on your stack. You can learn more about SiteSpect’s specific benefits here, including the flexibility that being tagless provides.
To learn more about SiteSpect in general, visit our website.
Subscribe to our blog: