Skip to content
Albright Labs Albright Labs

Case Study · Customer Experience

CXPA's platforms now work as one workflow.

A global association with member and program data spread across four disconnected platforms. We unified them into one workflow with single sign-on, tamed runaway API traffic, and rebuilt their website.

At a glance

Client
CXPA
Industry
Associations
Engagement
Multi-system integration
Stack
Rhythm AMS, Circle, PathLMS, SSO

4

systems unified into one workflow

The outcome

4

systems unified: Rhythm AMS, Circle, PathLMS, and SSO

17,000

member profiles in one source of truth

1,393

active CCXP certifications managed in the system

In the 90 days after launch

+171%

organic search sessions

6,852 to 18,603

2x

traffic overall

26,532 to 53,755 sessions

+146%

page views

41,427 to 101,871

42

membership conversions

from zero in the prior 90 days

Google Analytics, 18 Aug – 15 Nov 2025 compared with the preceding 90 days.

The problem

Data trapped in separate platforms.

CXPA is a global customer-experience association. Its member and program data had ended up spread across four disconnected platforms: Rhythm AMS for member management, Circle for community, PathLMS for learning, and a separate single sign-on layer. Beyond the fragmentation itself, the Circle integration had developed runaway API traffic, generating roughly 4,000 write calls per day and pushing toward the monthly limit of 30,000. Their public website was also due for a rebuild.

What we built

One connected workflow.

We integrated the four platforms into a single workflow with single sign-on, so a member logs in once and moves between Rhythm AMS, Circle, and PathLMS without re-authenticating. We brought the Circle API back within its 30,000-call monthly limit by identifying and eliminating the source of the excess write traffic. We rebuilt CXPA's public website, and built out the resource and content library on PathLMS, which now serves around 200 users across 4 courses.

The resource library, I really like the look and feel of it. I like how fast everything spins up when I can apply one filter or multiple filters in the taxonomy.
Gabe Smith, CCXP
01

Map the platforms

Rhythm AMS, Circle, PathLMS, and SSO: four systems with gaps between them.

02

Unify with SSO

One login flows across all four platforms without re-authentication.

03

Tame the API, rebuild the site

Circle API brought back within its monthly limit; new public website launched.

04

Build the library

PathLMS resource library live with 4 courses and 200 users.

You've done an awesome job, you and your team, getting our website up. You've been bringing in a lot of information, putting in a lot of widgets, and doing a lot of things.
Greg Melia, CAE, CEO, Customer Experience Professionals Association

The result

The platforms work as one.

The four platforms now run as one workflow. Members sign in once and move freely across Rhythm AMS, Circle, and PathLMS. The resource library is live on PathLMS with 4 courses and around 200 users. All 17,000 member profiles live in one source of truth, alongside 1,393 active CCXP certifications. And the website rebuilt alongside them changed the shape of their traffic: in the 90 days after the August 2025 launch, sessions doubled from 26,532 to 53,755 and active users from 17,000 to 35,456, led by organic search, which rose 171% and became the clearest signal that the rebuild was being found rather than merely announced. Page views grew faster than visits, from 41,427 to 101,871, and the membership page recorded 42 conversion events having recorded none at all in the 90 days before.

Before

  • Member data split across Rhythm AMS, Circle, PathLMS, and a separate SSO
  • Circle API generating around 4,000 write calls per day, near the monthly limit
  • An aging public website due for a rebuild
  • No single connected workflow for members or staff

After

  • 4 systems unified into one workflow with single sign-on
  • 17,000 member profiles in one source of truth
  • Circle API back within its 30,000-call monthly limit
  • New website live: traffic doubled and organic search up 171% in the 90 days after

Operations Audit

Have systems that do not talk to each other?

Most integrations like this start with an Operations Audit. Two weeks to map the systems and where the payback is.

Start with an Operations Audit

A senior engineer reads it and replies within one business day.