One final consideration on scalability: While an embedded integration provider must be able to scale elastically, it shouldn’t risk uptime and availability. Ensure your provider includes a financially-backed SLA with 99.5% uptime and delivers transparent, updated status and a strong track record of availability for all its embedded and platform services. Case Study: Why Eventbrite chose a serverless embedded integration platform Eventbrite (NYSE: EB) is the global self-service ticketing platform for live experiences. The company needed to deliver self-service integrations to its customers at a massive scale. It has more than 650,000 creators on its platform, managing more than 4.6M events in nearly 180 countries. As a result, any self-service integration Eventbrite rolls out can easily create a surge in demand on its embedded integration platform By choosing an entirely serverless embedded integration platform, Eventbrite enabled more than 59,000 active customer integrations in less than 12 months without adding any staff to its operations team. So, while it was able to reduce the number of engineers for each integration from six to one—more importantly, Eventbrite avoided the massive operational overhead from integrations at scale that comes with older, non-serverless integration platforms. Learn more 3. Sweat the details on end user activation (or face the consequences) One of the biggest reasons embedded integrations fail is that the end user marketplace activation experience is painful. So let’s take a moment to name and shame some of the recipes for failure: “The Homegrown Horror.” Code-first embedded integration platforms’ inflexibility can lead to significant customer pain. When using such tools, your development team may have embedded some connectors, but the platform doesn’t provide an end user activation experience. So, your development team must build out an activation experience in-house, which requires enabling end users to easily authenticate with their apps, allowing them to pick parameters and map fields step-by-step—in a way that’s flexible for different integrations. What often happens instead is the activation experience ends up being limited, it breaks, or it’s inflexible, and it ultimately drags down CSAT. “The Wait-What? UX.” You can’t just IFrame an entire, unguided workflow builder and brute- force it in your application—it’ll clash awkwardly with your product’s native UX and be painful for users to learn. And you don’t want an embedded integration activation that doesn’t feel 10