Thanks for the question. Honestly, it's the right critique we're looking for. For this particular case, the answer would be more naive than sophisticated. The

Thanks for the question. Honestly, it's the right critique we're looking for. For this particular case, the answer would be more naive than sophisticated. The research had a few strict requirements to ensure we we're not liable, so the service usage policies, self-serve trial capability and other terms left us with only a select few options (I'm sure we would have missed some solutions as well). Google's service technically falls under these criteria, but it's more of an infrastructure API rather than a product a merchant easily installs. I do believe merchants still have to hire agency/engineer resource to implement it. We do plan to include more in the next attempt, and this will be one of the new inclusions for sure, especially because of your comment about A/B testing - we'll figure out a way to compare all the vendors and still keep it apples to apples, without biasing the test for Quissly's favor, but given this was our first attempt and we leaned towards publishing quickly rather then large coverage.