Section 10 · Instrumentation roadmap

Instrumentation roadmap — P0 to P3

The roadmap groups instrumentation work by sequencing, P0 first and P3 last. Every P0 item is independently valuable and can be parallelized.

P0 closes the four conversion-measurement gaps that bias every number in the deck. P1 stitches the cross-property view and standardizes UTMs. P2 brings sector and audience identification. P3 reaches user-level reporting across products and the long-form analysis layer that needs a CRM and a warehouse.

P0 — Conversion measurement

Do these first. The four items address the four caveats listed in §09.

P0.1

Mark page-scoped form submits as key events

What

Configure GA4 key events for form_submit filtered by lead-bearing pages: programs and events, designation-information-session, contact, free-trial, registration. Do not mark the global form_submit as a key event — it would inflate conversions with 49–65% noise from account-login and cart-flow forms that are already tracked elsewhere.

Why

ProDir registers 1,714 form_submit events; only 107 are real lead intent. GSI registers 5,389 form_submit events, including 402 on /governance-solutions/events-and-education plus a long tail on contact and consultation pages. These are the missed conversions. Today they are invisible in GA4 dashboards.

How

GA4 admin → Events → Create Event with a condition on page_path matching the specific pages → Mark as Key Event.

Effort

Half a day, including admin work, page-list collection, and validation.

P0.2

Reconcile the duplicated cart_view event

What

The same event name cart_view appears with isKeyEvent=true (1,345 events) and isKeyEvent=(not set) (2,899 events) on the GSI/ProDir property. The flag is split across streams or hostnames. Identify which stream sends each variant, then either consolidate to a single configuration or apply the flag consistently.

Why

GA4 currently undercounts purchase intent on GSI by roughly 67%, with 1,133 of 3,373 actual cart_view events flagged. This affects every "key event" report in the platform.

How

GA4 admin → Property → Data Streams → review the cart_view definition per stream. Cross-check which GTM container fires the event on which hostname; the variant likely depends on a hostname condition in the firing rule.

Effort

Half a day to one day for the audit, GTM update, and validation.

P0.3

Configure key events on the BoardConnex marketing site

What

Add and flag at minimum three events: book_a_demo on the button or form submit, pricing_engaged triggered by scroll or copy interaction (the existing page_view on /pricing is too thin a signal on its own), and contact_form_submit. Mark all three as key events.

Why

1,494 sessions on BoardConnex over 12 months produced 0 measured outcomes. The November–December 2025 spike (663 sessions across the two months) is unaccounted for. This is the largest single tracking gap in scope and the easiest one to close.

How

GTM → add tags on the relevant button and form interactions → GA4 admin → mark as key events.

Effort

Half a day to one day, depending on the existing GTM container state.

P0.4

LinkedIn Insight Tag and conversion events

What

Three steps in sequence. Verify the LinkedIn Insight Tag is installed on governancesolutions.ca, professionaldirector.com, and boardconnex.com. In LinkedIn Campaign Manager, define conversion events for each priority action — form submit, demo request, course registration. Wire the events to fire via the Insight Tag at the right moments.

Why

$861 USD spent on 13 campaigns over 12 months produced 0 measured conversions inside LinkedIn. The traffic is real: LinkedIn recorded 754 landing-page clicks and GA4 recorded 313 form_submit events from LinkedIn-sourced sessions. Without conversion measurement, LinkedIn cannot optimize delivery and ROI cannot be calculated.

How

Open view-source: on each conversion-relevant URL and search for _lsl_partner_id or the Insight-Tag URL. If absent, install via GTM. Then in Campaign Manager → Plan → Conversion Tracking → Create.

Effort

One to two days, depending on what is already installed.

Parallelization

The four P0 items touch different surfaces (GA4 admin, GTM containers, the LinkedIn account) and have no sequencing dependency on each other. Two implementers can run them in parallel without conflict.


P1 — Cross-property visibility

P1.1

Cross-domain measurement linker

What

Configure GA4's cross-domain measurement to stitch users across governancesolutions.ca, professionaldirector.com, boardconnex.com, and browngovernance.com. Today the GSI ↔ ProDir stitching works because they share the GSI/ProDir GA4 property; BoardConnex sits on a separate property and is not stitched.

Why

The platform cannot answer "did the same user view BoardConnex pricing then visit GSI to register" — a question that becomes important if BoardConnex is part of the cross-sell strategy.

How

Either move BoardConnex onto the GSI/ProDir property (preferred for cross-property visibility) or configure user_id sync via BigQuery export.

Effort

One day for the move, five to ten days for the BigQuery path.

P1.2

UTM hygiene standard

What

Document a UTM template for every owned campaign type — Email, LinkedIn paid, Meta paid, Google paid, Display, partner referrals — and audit the existing UTMs across the active campaign set.

Why

Direct represents 79% of ProDir sessions and 75% of GSI sessions. Brand awareness genuinely drives a large share of this volume, but UTM-less email and outreach fold into Direct and become invisible. The 90-day target is to bring Direct's share below 60%.

How

Standard template along the lines of utm_source={platform}&utm_medium={paid|email|partner}&utm_campaign={campaign-id}&utm_content={creative-id}&utm_audience={audience-segment}. Enforce via a shared spreadsheet of pre-built tagged links and audit existing landing-page URLs quarterly.

Effort

Half a day for the template, one day for the audit, plus ongoing discipline.


P2 — Sector and audience identification

P2.1

Sector field on consultation and lead forms

What

Add a required Industry or Sector picklist on the GSI consultation form, the ProDir free-trial form, and the BoardConnex book-a-demo form. Push the value into GA4 as a custom dimension via dataLayer.

Why

Sector engagement today is a proxy reconstructed from LinkedIn paid plus LinkedIn organic visitor data. Once forms capture sector directly, the team can answer "which sectors are converting" rather than only "which sectors are clicking ads."

How

Form-library update plus a GTM step to push the value into a GA4 custom dimension.

Effort

One to two days, depending on form-library complexity.

P2.2

utm_audience parameter for segmented campaigns

What

When a paid campaign targets a specific sector (Higher Ed, Financial Services, and so on), append utm_audience=higher-ed to the destination URL.

Why

Lets GA4 segment performance by audience without depending on whether a form was submitted.

How

Part of the P1.2 UTM template.

Effort

Included in P1.2.

P2.3

LinkedIn Insight Tag for retargeting and visitor identification

What

Beyond conversion measurement (P0.4), use the Insight Tag to enable LinkedIn-side audience features: retargeting visitors who reached /26w-the-governance-professional-certificate-program, lookalike audiences from converters, and demographic insight on website visitors. LinkedIn returns aggregated demographics for any website-visitor audience that exceeds 1,000 members.

Why

Once the tag is in place, retargeting and lookalike modeling become available without additional engineering, and LinkedIn can report demographics on the inbound visitor pool.

How

Configuration only, inside Campaign Manager.

Effort

Once P0.4 is done, one to two hours.

P2 — ABM tracking

Three options were laid out in §08, ranked by effort against payoff. Option 1 is RB2B or Leadfeeder for immediate company resolution at $200–$1,000 USD per month; Option 2 is a user_id sync from CRM to GA4 for the highest fidelity but requires a CRM; Option 3 is utm_audience tagging per ABM list for low effort and partial coverage. The recommendation is to run Option 1 and Option 3 in parallel as the first wave, with Option 2 sequenced after a CRM is in place.


P3 — User stitching across products and long-form reporting

P3.1

user_id sync from CRM to GA4

What

When a user authenticates through login or a form submit, push the CRM contact ID into GA4 as user_id. This enables user-scoped reporting that survives across sessions and across browsers.

Why

Without a stable user identifier, every cross-device journey resets and per-account behavior reporting cannot be computed.

How

CRM event hook plus dataLayer push on authenticated pageviews.

Effort

Five to ten days, and requires a CRM.

P3.2

BigQuery export of GA4 plus CRM join

What

Stream GA4 raw events to BigQuery (free up to 1M events per day) and join against CRM contacts.

Why

Unlocks any custom analysis — cohorts, attribution models, account-level dashboards — outside GA4's native UI, where the platform's own aggregation rules cap what is reportable.

How

GA4 BigQuery linking plus a scheduled join job against the CRM export.

Effort

Two to five days for the data pipeline, plus ongoing analysis capacity.


Areas missing from the original brief

The original ask covered ProDir, GSI, BoardConnex, and The Governance Community. Four additional areas warrant attention based on what surfaced during the audit.

A · Email marketing analytics

Not measured

GA4 captures 112 sessions tagged RD Station / email on ProDir over 12 months — proof that an ESP exists and at least some emails are UTM-tagged. We have no visibility into open rates, click-through rates, list segmentation, or the share of total email volume that is not getting UTM-tagged. The next phase of analytics should include an ESP audit and an email-attribution pipeline.

B · Podcast analytics

Not measured

The page /governance-solutions/the-governance-solutions-podcast is the 5th most-viewed page on GSI with 3,624 pageviews over 12 months, but there is no event for podcast listens or episode plays on the page. If the podcast is hosted on Spotify, Apple, or a custom player, those platforms hold their own analytics outside GA4. Pull native podcast platform stats — downloads, listens-to-completion, geographic distribution of listeners — and reconcile against the website pageviews.

C · Paid Search opportunity

Untested at meaningful volume

GSI Paid Search recorded 96 sessions over 12 months — essentially zero. Paid Search has historically been one of the most efficient channels for high-intent B2B education ("board governance certificate program," "director designation Canada"). The GSI keyword space is small and brand-protective campaigns are cheap. Scope a brand-and-category Paid Search test in Q3–Q4.

D · Search Console linkage to GA4

Not connected

Search Console data — clicks per query, impressions per query, average position — is not visible in GA4 today. (not provided) dominates the search-term dimension. Linking Search Console to GA4 takes around 30 minutes and unlocks the actual organic queries reaching the sites.