Published June 25, 2026
Last updated June 25, 2026

How we tripled Persona's Marketplace integrations in under a year

Persona's Marketplace PM breaks down how we decide which integrations to build, highlights a few standouts, and shares what's next.
Jenna Kim
Jenna Kim
7 min
Illustration of someone dropping an icon of a storefront into a slot

When I joined Persona's Marketplace team as the product manager in August 2025, we had around 25 integrations. Our goal was to make Persona a seamless fit in every customer's stack: easy to get started with and even easier to grow with. Less than a year later, we've tripled the size of our marketplace to include more than 75 integrations.

Here's how we've approached our Marketplace strategy this year.

Building for breadth

Our strategy is simple: support as many of our customers' existing tools as possible. We're prioritizing this for three reasons.

The first is credibility. When an organization evaluates Persona, they may look at our Marketplace to gauge how mature and scalable our platform is. A comprehensive list of integrations reinforces the idea that Persona is built to serve as infrastructure, not a point solution.

While reaching 75 integrations is an exciting milestone, our strategy has never been centered on hitting a specific number. Instead, we're focused on expanding the ecosystem in ways that create meaningful value for customers. Even if we don't support a specific tool today, a robust Marketplace gives organizations confidence that we have the technical foundation, subject matter expertise, and operational processes to build new integrations quickly.

The second is stickiness. The more workflows Persona touches, the harder it becomes to remove from a customer's stack. Switching costs are real. Replacing an integrated platform means rebuilding connections, retraining teams, and disrupting the workflows that depend on it. Once a user habit is cemented, it’s hard to shake!

The third is less about business outcomes and more about a product philosophy of mine: we should meet customers where they already work. Identity verification shouldn’t happen in a vacuum. It belongs inside the tools teams rely on every day, from applicant tracking systems and customer relationship management software to help desks and more. Persona's goal is to fit naturally into those existing workflows so customers don't have to build workarounds or change how their teams operate.

Without revealing too much about our team's day-to-day, I will say that AI has been one of the biggest reasons we've been able to expand our Marketplace at this pace. After defining a clear path from development to launch, we used AI to automate repetitive work and eliminate process bottlenecks. AI has helped us write code, QA test, and even prepare GTM materials (like our Help Center articles!).

Different GTM playbooks for different integration types

Of course, process and strategy are only part of what makes an integration launch successful. Once those foundations are in place, the next challenge is connecting the right integrations with the right customers. At Persona, we generally approach that challenge through two go-to-market motions: customer-led and Persona-led.

Customer-led integrations are requests from a customer looking to integrate their existing tech stack with Persona. These types of integrations are almost an expectation: “I use Salesforce, so I need Persona to integrate with Salesforce.”

This also applies to other tooling beyond CRMs, like project management software, messaging platforms, and more. The goal is to reduce context switching and centralize identity insights directly within the workflows our customers already use. Ideally, the integration is already live when the need arises, and when it isn’t, we make speed the priority.

The converse of this is what we call Persona-led integrations. These typically involve strategic partnerships with third-party data providers, such as credit bureaus, business registries, and network intelligence platforms, allowing customers to build a richer picture than Persona provides on its own.

We proactively recommend these integrations when we see an opportunity to strengthen a customer's identity strategy. A customer might come to us with a fraud problem or a slow onboarding process, and the solution we recommend often combines Persona with complementary technologies that address those challenges more effectively.

Background checks are one of our more common examples. We frequently work with customers and prospects who want to run background checks alongside identity verification, and in those cases we introduce them to our background check integration, built in partnership with Yardstik.

A little-known fact is that Yardstik offers much more than just criminal screening packages, which are what most employers run when extending a job offer to an applicant. As customers bring us new requirements, we're able to work closely with Yardstik to support more specialized background check use cases, such as verifying employment history and education credentials. Over time, those customer conversations create a feedback loop that strengthens both the partnership and the solutions we can offer.

Our current focus is workforce and productivity integrations

While customer-led and Persona-led integrations require different playbooks from a GTM perspective, they're increasingly converging around the same set of categories where we see the strongest customer demand and the greatest opportunity to shape the market.

I'm particularly excited about integrations that support our workforce use case by connecting Persona with the systems organizations use to manage the entire employee life cycle. This includes applicant tracking systems (ATS), human resources information systems (HRIS), and identity and access management (IAM) tools.

With workforce use cases, identity verification doesn’t happen in isolation. When you think about the end-to-end flow (the trigger, the verification itself, and what happens after), integrations are the connective tissue. A government ID check and selfie cover the middle step, but customers also need to know the person being verified maps to a real candidate in their ATS and that their IAM system updates their access once verification passes. Integrations orchestrate the entire process.

Productivity integrations are the other half of our focus. The goal is to make identity verification a native part of existing operational workflows. Operations and compliance teams shouldn't have to open Persona every time a verification result needs follow-up. That's why we have integrations like Jira. Rather than requiring teams to monitor a separate queue, Persona automatically creates a ticket whenever a verification is flagged for manual review.

Three integrations worth spotlighting

While we've added a few dozen new logos to our marketplace, I'm especially excited about the following:

Workday Recruiting: As one of the most widely used applicant tracking systems for large enterprises, Workday was a priority for our workforce use case because of how central it is to enterprise hiring flows. With this integration, hiring teams can make candidate verification a native part of the pipeline, triggering checks automatically at key milestones and syncing results back to Workday.

ServiceNow: Not every Marketplace investment comes in the form of a brand-new integration. This year, we expanded our ServiceNow integration to support Incidents, one of the primary objects used to manage help desk and account recovery workflows. When someone needs to reset MFA or regain access to an account, that process often begins with a ServiceNow incident. By connecting Persona directly to that sequence, teams can verify users without leaving the systems they already rely on. It's a good reminder that Marketplace growth isn't only about adding new integrations; deepening existing ones can be just as impactful.

Zoom: Our Zoom integration serves organizations that need confidence in who's on the other side of a call. Hiring teams are among the early adopters as part of the candidate verification process. Since then, we've seen interest from higher education institutions, law firms, remote consulting companies, and other scenarios where that same assurance matters.

What I'm betting on over the next 12 months

Identity verification is showing up in workflows that would have felt out of place just a few years ago: hiring pipelines, help desk tickets, video calls, and more. As those use cases continue to expand, our goal over the next 12 months is to ensure Persona fits naturally into the systems customers already use while continuing to introduce capabilities that make those workflows stronger.

The information provided is not intended to constitute legal advice; all information provided is for general informational purposes only and may not constitute the most up-to-date information. Any links to other third-party websites are only for the convenience of the reader.
Jenna Kim
Jenna Kim
Jenna Kim is a product manager building Persona's third-party integrations marketplace. Outside of work, she can usually be found at the driving range, tennis courts, or park with a book in hand.
Continue reading