Robust platform that requires coding knowledge and technical support to optimize use.

While our DSR is extremely responsive and helpful, he often needs to go to one of the platform's DECs or developers to get the more technical information we request.

For more advanced tests or experiences, getting insight from a DEC or developer is time-consuming as the queue is long. This holds up our ability to run advanced tests, sometimes by weeks. Additionally, I find the Knowledge Base articles do not often go in-depth enough to adequately answer a question and finding the exact article you need can be tricky too.

The interface is user-friendly, and the action builder makes sense. I do find it beneficial to have prior knowledge of coding languages like HTML, CSS, and Javascript.

We use Monetate primarily for testing and setting up 100% experiences. We run multiple A/B tests and dynamic tests each month to great success and new learnings. Additionally, if we need to change site content for specific visitors for a short period of time, we use Monetate's 100% experiences to take over a section of site content. We use this the most often when targeting visitors who come to the site from a specific campaign UTM. We do not use Monetate to track sitewide behavior and analytics, even during a testing window. For example, when running a test on the Hamburger menu, we do not have a straightforward way to Monetate to see how those visitors behave during the rest of their time on site. Essentially, it can be tricky to see the detailed full-funnel effect of a test variant. For that information, we often turn to a third-party analytics platform like Google Analytics.