A trade association proved its website earns its membership dues with a GA4 setup its board understands

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Half of the association's income is membership dues and most of the rest comes from its annual conference, so the website has to serve three audiences at once: prospective members reading the public face, current members living in the portal, and attendees registering on a separate events platform. A small staff runs it all — communications, membership, and events share the same site and the same inbox. The board asks annually what the website actually delivers, and the answer has historically been page-view counts assembled by whichever director had the quietest week.

What it was costing

The association's board asked one question every year — what does the website actually do for members? — and the old analytics setup answered with page-view counts; event registrations, member-portal usage, and advocacy actions were invisible or double-counted.

What they could see

• The annual board report answered the dues question with page views, and at least one board member said so out loud each year.
• Event registrations sometimes counted twice — once by the events platform, once by the website — and nobody knew which reports agreed.
• Advocacy campaigns generated thousands of member actions that no report recorded anywhere.
• The member portal's usage was invisible, so renewal conversations relied on anecdotes from the membership team.

The constraints we worked inside

• The site spans a public face, a member portal, and a separate events platform; measurement must span all three without inflating counts.
• Board reporting is annual and plain-language; the setup must produce a one-page answer, not an analytics project.
• Member privacy expectations are high; member-area tracking must be aggregate and transparent.

What had been tried before

The communications director assembled the annual report by hand each year from three platforms' exports and a counts email from the events team.

The exports used different counting periods and different registration definitions, so the totals double-counted conference attendees and shifted year to year with whoever did the assembly.

A past vendor had enabled cross-domain tracking between the site and the events platform by following the measurement vendor's default documentation.

The defaults linked the domains but never addressed deduplication, so a registration that both properties saw landed in every report, and trust in the connected numbers eroded.

What we proposed

We proposed defining member value as named conversion events — conference registrations, advocacy actions, resource downloads, portal engagements — each with a plain-language definition a board member can read without translation. A single GA4 property would span the public site, the portal, and the events platform, with a documented deduplication rule so a registration counts once no matter which domain saw it first. Member-area tracking would stay aggregate and transparent, consistent with the association's privacy posture. The deliverable is an annual one-page summary built on fixed definitions, so the board's standing question becomes a standing report rather than a springtime scramble.

Just as important is what we ruled out, and why:

• Reporting only from the events platform's native dashboards — They count conference attendance well but see nothing else — the portal, advocacy actions, and resource downloads would remain invisible, and the board question covers all of it.
• A member survey program to replace tracking — Surveys measure stated value once a year with response bias; the board asked what the website does, and the website's own events can answer directly at far lower cost.

How the work ran

Delivered by the growth pod — analytics specialist over 5 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

GA4

One property across three domains is the only structure where a member's path from public page to portal to conference registration exists as one record.

Google Tag Manager

The small staff cannot edit site code; a container lets communications and events publish conversions themselves, with the definitions documented beside each tag.

BigQuery export

The annual report must be reproducible years later; raw exports freeze each year's numbers with their definitions, so last year's page never changes retroactively.

Looker Studio

The board sees the one-page summary, but staff need the living version; a shared report lets membership and events check their own numbers between board cycles.

Cross-domain measurement

The events platform is a third-party domain, and linker configuration plus a documented deduplication rule is what keeps one registration one count.

What went wrong

How we worked together

Cadence

Weekly working sessions with the communications director; a short written update to the executive director after each; a dry-run of the board page one month before the meeting.

Client side

The communications director led; the membership manager supplied portal access and renewal context; the events manager owned the platform relationship and historical registration files.

Decisions

Conversion definitions were decided by the staff group, not by us — our job was making each option measurable; the executive director signed the final set.

They provided

Admin access to site and portal, the events platform's export history, the board's prior annual summaries, and staff time for two definition workshops.

What changed

The headline: board's annual report grounded in agreed conversion definitions across site, portal, and events platform — Page views → member-value conversions, read from Annual reporting document. A second check: analytics sources the board needs to answer the value question at 3 → 1.

The board meeting stopped being an annual interrogation. The one-page summary leads with what members did — registered, downloaded, acted, returned — in sentences rather than metrics, and the discussion moved to program decisions like whether the advocacy platform earns its budget. Staff now check their own numbers before planning a campaign instead of asking for a pull, and the events manager books the conference with registration data she trusts. One set of definitions also ended the quiet fiefdom where each department's report showed a different website.

The result was read from Annual reporting document against the pre-engagement baseline over the stated window, with a guardrail check on analytics sources the board needs to answer the value question. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The conversion definition sheet in plain language, versioned and stored with the board materials.
• The annual one-page board summary template, wired to fixed BigQuery queries.
• A living Looker Studio report covering site, portal, and events platform for staff use.
• Documented cross-domain and deduplication settings, including the registration-window rule.
• A staff training session on publishing new conversion events through the tag manager.