PCA|Association Membership|Pilot · Live Data
Deployed System · Case Study

The Member Profile Engine

How a national painting-contractors association got four platforms that had never met to admit they know the same people — one profile per member, and an action list for every event.

4 platforms unified · 1 profile per member · every event → an action list
View Case Study
CHAPTER 01

Every platform knew a quarter of each member.

Membership in one system, course streaming in another, email in a third, events in a fourth. Four honest platforms — and no single place where a member was a whole person.

Systems detected & mapped
MB
CONNECTED

Membership system

The member of record — the spine
API
ST
CONNECTED

Course streaming

What members actually watch
API
EM
CONNECTED

Email platform

Opens, clicks, gone-quiet
API
EV
CONNECTED

Events & social

Attendance + interest tags
API + tags
Where member signal lived
Membership records
25%
Streaming behavior
25%
Email engagement
25%
Event attendance
25%
Illustrative — the point is the spread
The gap
Before

Four dashboards, no member.

Staff swiveled between systems to answer a simple question: is this member engaged, drifting, or gone? Usually, nobody had time to ask.

After

One profile, then action.

Every member’s behavior assembles into a single record — and the records roll up into lists someone can actually work through.

CHAPTER 02

Making the systems admit they know the same people.

The membership system anchors identity. Everything else gets matched against it — behavior, not survey answers.

The join rules
Encoded assembly rulessample of the set
01The member-of-record system is the spine — every other platform matches to it, never the reverse.encoded ✓
02Streaming joins as behavior: which courses, how far, how recently — interest you can see, not guess.encoded ✓
03Email joins as engagement: opens, clicks, and the members who’ve gone dark.encoded ✓
04Events and interest tags close the loop between what members say and where they actually show up.encoded ✓
05Segments rebuild themselves from the data — nobody maintains a spreadsheet on the side.encoded ✓
How it plugs in

Live membership records anchor every profile — who the member is, their company, their standing.

Member recordsCompaniesStanding

Streaming and email engagement attach to the spine — what each member watches, opens, and ignores.

Course progressOpens & clicksGone-quiet flags

Event attendance and interest tags complete the picture — where members show up and what they keep showing up for.

AttendanceInterest tagsFirst-timers
Captured from the association

We don’t have a data problem — we have four data problems that have never been introduced to each other.

Source: Association staffThe join, in one line

After every event we say we’ll follow up with the people who lit up. By the time we know who they were, it’s renewal season.

Source: Association staffBecame Event Actions
CHAPTER 03

Events stop being a blur.

The association runs on gatherings. Now each one comes with its own to-do list — before, during, and after.

The actual product
PCA member profile · pilot · internal surface
PCA Holistic Member Profile
The actual pilot surface on live association data — member names, companies, and emails blurred.
The membership team’s view
What the engine assembles
1
profile per member
4
platforms behind it
live
built on real records
0
swivel-chair lookups
The question “is this member engaged?” became a glance instead of an investigation.
A member, in one glance
MBR-1188readyEngaged · rising
profile ✓

Owner-operator · watching the estimating series

Three courses deep this quarter, opens everything, attended the spring regional. A candidate for the next cohort offer.

MBR-0417highDrifting
flag

Long-time member gone quiet in every channel

No opens in months, no events this year. Exactly the member a renewal-season call should reach first.

Representative sample · names and details anonymized
Around every event
Before
who’s registered, who should be but isn’t
nudge lists, not blasts
During
who’s in the room for the first time
worth a deliberate hello
After
who lit up · who went quiet
follow-ups while it’s warm
An event’s action list
EVT-PREmediumBefore · outreach
list ready

Members who match the topic but haven’t registered

Watching related courses, opening related emails, not on the list — the personal-nudge shortlist.

EVT-POSTreadyAfter · follow-up
list ready

First-timers who engaged hard

Showed up, stayed, and clicked the follow-up — the warm list for a call this week, not next quarter.

Representative sample · names and details anonymized
The leadership view
Whole
members as people, not rows
across all four platforms
Early
drift visible before renewal season
quiet members surface themselves
Working
staff hours go to conversations
not to assembling lists
The shift
“The association always knew its members in aggregate. The engine makes it possible to know them one at a time — at scale.”
CHAPTER 04

Profiles that rebuild themselves.

Nobody maintains this by hand. The joins re-run, the segments re-form, the lists stay current.

One assembly, traced

Read the spine

membership system

Current member records pulled — the anchor every other signal attaches to.

Attach behavior

streaming + email

Course progress and email engagement matched member by member.

Attach gatherings

events + tags

Attendance history and interest tags joined to complete each profile.

Hold the unmatched

identity hygiene
held

Records that can’t be confidently matched are held for review — never guessed into the wrong member’s profile.

Rebuild segments

from behavior

Engaged, drifting, first-timer, topic-interest — segments re-form from the fresh data.

The feedback loop
Engine grouped

Two records, one member

a rename hid the same person twice

Staff corrected

Merge rule added

the pattern now resolves on its own

Identity corrections become rules. The next rename, rebrand, or typo resolves without anyone noticing it happened.
Identity fixes
manual
After
encoded
CHAPTER 05

Piloting on live data.

Built against the association’s real systems from day one — not a slideware demo waiting for permission to be real.

Current state
Live
the profile spine runs on real records
refreshed from source systems
Pilot
event actions in the field
around real calendar events
Next
renewal saves & journey nudges
same spine, more surfaces
Why it holds up

Runs on their systems

The four platforms stay exactly where they are. The engine reads them; it doesn’t replace them.

Member data stays home

Profiles assemble inside the association’s own accounts — nothing exported to a third-party warehouse.

The joins are documented

Every matching rule is inspectable. The association can explain any profile to any member.

The spine is the platform

Renewal saves, journey nudges, cohort offers — each new surface reuses the same assembled truth.

Sitting on platforms that don’t talk?

One conversation. I’ll find the join, scope the build, and tell you honestly whether it’s a fit.