ActiveCampaign combines marketing, marketing automation, and CRM capabilities in one software. In order to provide customers with an even more seamless workflow, ActiveCampaign offers over 290 integrations.
Shay Howe, the VP of Platform Strategy at ActiveCampaign, shared his insights on how to grow a successful tech ecosystem and technology partnership program.
When I joined ActiveCampaign, close to three years ago, I was hired to lead the Design team, including Product and Brand design. Being a startup, we’re an organization where you tend to wear many hats and at different times I’ve led our Platform Engineering and Marketing teams in addition to Design.
My experience leading these different teams, as well as owning relationships with a number of our strategic partners, has provided the opportunity to dig into all aspects of our business, which today, is leading our Platform Strategy.
Outside of Design, the Platform Strategy team is a new team at ActiveCampaign which is still coming together. Responsibilities for the team include building an application ecosystem around our platform, all Strategic and App partner operations, be it sourcing, recruiting, onboarding, and growing partnerships, as well as helping define and shape the future of our products and services.
A core strength of ActiveCampaign is our automation capabilities. And with automation in mind, we continually ask ourselves, “How do we build automation throughout the entire customer experience?”
A large part of this requires integrations. Any given business is going to use many different tools to serve their customers, and all of these tools impact a customer’s experience. We provide the ability to bring these tools together, share data across them, develop new insights, and layer automation into the core customer experience.
Very early on we opened access to our API for third-party development. Around the same time, we created a few integrations ourselves, including one with Zapier to open up access to a wide range of other integrations, and added the ability to send data via webhooks across our platform. This planted the seed, allowing anyone to extend the capabilities of ActiveCampaign.
More recently, we’ve been adding new native integrations and applications for our customers. Many of which are being built by our partners, a select few including Calendly and Survicate.
Today, anyone is welcome to register for a developer and sandbox account on our website. Then when ready, partners are able to submit their application or integration for review. We’ll work with them, ensuring we’re able to test the integration, and once all is approved, we’ll list the integration in our public and in-app marketplaces. At the time, we also open other areas of promotion for these partners, including our recipe marketplace.
Setting up an integration can be quite a complex process, so we’re continually trying to reduce friction here. Two small areas that can have an impact during setup:
First, we look to see how we can authenticate, most commonly across platforms. Best case scenario, we can do this with one click, logging in to connect the two platforms. Worst case scenario, we share API credentials.
Second, after authentication, is often field mapping, including what are the fields within each platform that need to be related to another. A customer's name or email address, for example, need to be synced and aligned across systems. During setup, we’ll look to try to dynamically and automatically map these fields for a customer, allowing them to override mappings where they want but not forcing them to set up each field mapping individually by hand.
Once connected and integrated, we look to improve the experience by offering branded and native touch points within the ActiveCampaign platform.
On a contacts profile, for example, partners are able to brand tags with their logo to create quick visual references. Within an automation, partners are able to brand automation start triggers and actions. So rather than saying, “send data to this webhook,” which can be a bit of a black box to know what that webhook is doing, partners can have their banded identity and the specifics of what that action is doing, such as creating a new row in a Google Sheet.
Cognitively, this makes using integrations easier as there is less of an unknown with respect to how our tools are working together, and better visibility into how the customer’s experience is being improved.
Elsewhere, to allow customers to get started quickly, our partners are able to create automation recipes. Where a partner sees common use cases for their integration they’re able to create a recipe, allowing customers to easily add an automation to their account.
Our goal is to make the integration and continued user experience as seamless and self-serve as possible.
We are a very customer centric and customer-led organization. Today, we have 100k customers with no less than 50 ways to capture their feedback and listen to their needs.
This starts during onboarding, we ask what types of tools and products they're using and looking to integrate with. This continues with routine NPS surveys, is extended by our different social and community groups with customers supporting and helping one another, and weaves into our service, support, and user experiences practices internally.
As there are requests, we have a good pulse for how frequently an integration is being asked for and who’s asking for it. With this, we’re able to both prioritize the integrations and partnerships we should build, as well as understand from the customers what their desired use cases are for an integration.
For our many integrations, we’re able to see the number of connections, API requests, and the like while customer data is always kept secure and private. Likewise, we track support requests and questions regarding integrations.
All of this is in effort to improve the customer experience, learning where we need to improve or expand the capabilities of an integration.
First, listen to your customers. Always orient around what customers are saying, and what they are asking for. From there, if it makes sense, decide which integrations you’re up for taking the responsibility to build and maintain.
Second, if you’re getting requests to extend your product in a number of different ways or you’re not quite sure where to begin, look to open an API or build an integration with an integration platform as a service (iPaaS). This will allow others to extend your product in many different ways, and you’ll learn how you can best evolve an ecosystem of integrations and partnerships.
Ecosystems, integrations, and partnerships are all an incredible opportunity for growth.
At ActiveCampaign, we see this as a way to expand the capabilities of our product while bringing together and building automation into all the tools that impact a customer's experience. For us, it’s a new wave of growth and opportunity for our customers.
Thinking about it in this lens, using an ecosystem and partnerships to support your customers, will end up improving your business greatly.