What I like best about Impartner PRM is its flexibility and ease of use. The UI is brilliant and intuitive, and it was very easy to learn how to navigate and manage the platform.

I particularly like the ability to create custom pages and objects, which allows us to tailor the portal to the very specific needs of our partner program. We can provide different experiences, views, and permissions based on user roles and partner types. There are also many out-of-the-box objects and capabilities available, and even though we don't use all of them, we have the flexibility to configure and adapt what we do use to fit our needs.

Most importantly, as a Partner Operations Manager who isn't highly technical, I'm able to self-administer and manage the portal effectively. I can make changes, configure experiences, and manage much of the platform myself without constantly relying on our CRM or IT teams for support. That level of independence has been incredibly valuable and has made Impartner a great platform for us. Review collected by and hosted on G2.com.

One area I would like to see improved is the availability of examples and resources for more advanced customization. While Impartner gives us a lot of flexibility, building custom widgets and Orchestration Studio flows from scratch can sometimes be challenging. A larger library of templates, real-world examples, best practices, or even a customer community where users could share widgets, flows, and solutions would be extremely valuable.

Some of the out-of-the-box objects and their built-in behaviors can also be quite rigid. For example, with the Applicants object, moving an applicant to the "New Partner" status automatically creates an account record in Impartner. Because of our CRM synchronization requirements, all of our accounts need to originate in our CRM. There isn't currently a way for us to disable that automatic account creation, so we have had to develop workarounds by creating custom status fields.

I'd also like to see improvements to the Journey creation UI, as it could be more intuitive and easier to manage.

Finally, reporting is probably the biggest limitation for us. The standard reports offer relatively limited customization unless you purchase the add on reporting module. This becomes particularly challenging when we've had to develop workarounds for certain out-of-the-box objects or processes, because the standard reports don't always reflect the way we're actually using the platform. Beyond basic metrics such as logins and page visits, we've found the standard reporting capabilities fairly limited. Review collected by and hosted on G2.com.