Cross-property journeys and account-level visibility
GSI and ProDir share one GA4 property and the cross-domain stitching is working; BoardConnex sits on a separate property and cannot be stitched today. For account-level visibility we have three options ranked by effort and payoff.
In the 12 months from May 2025 to April 2026, the GSI/ProDir GA4 property recorded 112,536 sessions and 90,002 users; the per-host sum across 13 hostnames is 112,048 sessions and 89,931 users. The two numbers reconcile within tolerance, which is the diagnostic for working stitching.
Stitching diagnostic
| Metric | Property total | Sum per host | Ratio | Stitching |
|---|---|---|---|---|
| Sessions | 112,536 | 112,048 | 0.9957 | Working |
| Users | 90,002 | 89,931 | 0.9992 | Working |
Reading
If stitching had been broken, the per-host sum would have exceeded the property total by 5–15% as the same human got counted as new on each domain. The 0.4% session gap and 0.08% user gap reflect normal "(not set)" rows. The same person visiting both governancesolutions.ca and professionaldirector.com is correctly de-duplicated to one user.
Per-host totals
The two sites in scope account for nearly all the volume. BrownGovernance receives a thin trickle. FinancialLiteracyCheck records a 25% conversion rate against very small volume — small but striking, and the right place for a clarification call.
| Hostname | Sessions | Users | Key events |
|---|---|---|---|
www.governancesolutions.ca | 90,620 | 71,473 | 1,168 |
www.professionaldirector.com | 20,992 | 17,858 | 210 |
www.browngovernance.com | 332 | 333 | 2 |
financialliteracycheck.com | 32 | 28 | 8 |
FinancialLiteracyCheck's 8 key events on 32 sessions is a 25% conversion rate, which is unusually high for any of these properties. The status of that brand site is one of the items routed to §11 for a clarification call. Nine additional hostnames (development environments, www-less variants, two test referrers) appear in the property at trace volume and are not relevant to the analysis.
First-user source per hostname
The cross-property funnel between GSI and ProDir is real and measurable. ProDir's second-largest first-user source is governancesolutions.ca / referral — 1,562 first-user sessions and 61 first-user key events. GSI is by far ProDir's largest external referrer.
Top first-user sources
| Source / Medium | Sessions | Key events |
|---|---|---|
| (direct) / (none) | 69,411 | 475 |
| google / organic | 6,059 | 103 |
| google / cpc (Display) | 5,693 | 497 |
| fb / paid | 1,625 | 0 |
| bing / organic | 1,529 | 23 |
| facebook.com / referral | 390 | 0 |
| an / paid | 314 | 0 |
| linkedin.com / referral | 246 | 1 |
Top first-user sources
| Source / Medium | Sessions | Key events |
|---|---|---|
| (direct) / (none) | 17,328 | 106 |
| governancesolutions.ca / referral | 1,562 | 61 |
| google / organic | 1,388 | 33 |
| bing / organic | 266 | 2 |
| RD Station / email | 109 | 0 |
| facebook.com / referral | 89 | 0 |
| statics.teams.cdn.office.net / referral | 18 | 3 |
BrownGovernance receives only Direct traffic — 332 first-user sessions and 2 key events, with no SEO or campaigns landing on it. The MS Teams referrer (statics.teams.cdn.office.net) appears on both sites, which is internal-stakeholder activity from Teams chat link previews.
BoardConnex correlation
BoardConnex sits on a separate GA4 property. User-id stitching across the two properties is not configured, so we cannot answer "what share of GSI visitors also reach the BoardConnex marketing site." Closing that gap is the work in §10-P1: either move BoardConnex onto the same property, or configure cross-property user_id reporting via BigQuery.
Account-level visibility
GA4 does not see companies. It sees anonymous browsers. To get account-level visibility we offer two indirect signals from the existing data, then three options for installing real ABM tracking.
Indirect signal A — top referrals
Aggregating referral source/medium across both sites surfaces three operationally meaningful patterns: the GSI ↔ ProDir cross-link, the MS Teams referrer, and the first measurable evidence of LLM-driven traffic.
| Source | Medium | Sessions | Users | Key events |
|---|---|---|---|---|
| governancesolutions.ca | referral | 1,856 | 790 | 74 |
| statics.teams.cdn.office.net | referral | 821 | 87 | 19 |
| linkedin.com | referral | 782 | 191 | 5 |
| professionaldirector.com | referral | 452 | — | 10 |
| facebook.com | referral | 450 | — | 0 |
| chatgpt.com | referral | 179 | — | 2 |
The MS Teams referrer at 821 sessions, 87 users, and 19 key events is internal-stakeholder activity. Stakeholders inside partner organizations and the GSI internal team are sharing GSI links over Teams chat, and the chat link previews surface as a referrer. The chatgpt.com row at 179 sessions is small but is the first measurable evidence of LLM-driven traffic reaching the sites.
Indirect signal B — city concentration
Cross-referencing GA4 city against a seed list of named accounts produces a rough proxy for account presence, with a hard ceiling on usefulness.
| Account name (seed) | City | Country | Sessions | Users | Key events |
|---|---|---|---|---|---|
| Manulife (HQ Toronto) | Toronto | Canada | 17,688 | 14,599 | 157 |
| Air Canada (HQ Montreal) | Montreal | Canada | 1,380 | 1,058 | 53 |
| Pacific Coast University (HQ Port Alberni) | Port Alberni | Canada | 27 | 20 | 1 |
The proxy is noisy. Toronto traffic is every Toronto-area company and resident, so 17,688 Toronto sessions tell us almost nothing specific about Manulife. The Pacific Coast University row at 27 sessions in Port Alberni is closer to a meaningful PCU signal than the Toronto count is to Manulife — the smaller and more geographically concentrated the company, the more usable the proxy.
Branded search terms
The seed list of named brands returned zero matches against the search-term dimension because (not provided) and (not set) dominate Google's organic-search column. Top branded queries reaching the sites today are mostly internal site-search and redacted Google rows. To recover real organic queries the next step is to link Search Console to GA4 (see §10-P3).
What we cannot observe
The current setup leaves four blind spots that no amount of GA4 reporting will fill on its own.
- Individual company browsing on the website. GA4 does not resolve IPs to company names.
- Which executives or board members from PCU, Air Canada, Manulife, or any other named account visited.
- Cross-channel attribution per company, mapping a paid → organic → consultation-form journey to a logo.
- Whether the LinkedIn ABM list
2025_01_09 - Corporate Secretariesproduced post-click site activity. The LinkedIn pixel is not measuring conversions today, as covered in §06.
ABM tracking options
If named-account behavior is a priority for the GTM strategy, there are three options ranked by effort against payoff.
RB2B / Leadfeeder install
A reverse-IP or cookie-based service that resolves anonymous visitors to company names. RB2B works on US visitors via residential identity graphs; Leadfeeder works on B2B IP ranges. Effort is 1–2 hours of dev to add a script tag to the head. Within 1–2 weeks the team can read sentences like "Manulife visited /governance-solutions/events-and-education/26w-the-governance-professional-certificate-program four times in the last seven days." Resolution rate runs 25–60% on Canadian B2B traffic. Cost is $200–$1,000 USD per month depending on volume tier. The tradeoff is privacy disclosure under PIPEDA and Quebec Law 25; RB2B's identity-graph approach is more invasive than Leadfeeder's IP-only approach, so the choice depends on legal posture.
user_id sync from CRM to GA4
When a user identifies themselves through a form submit or login, push the CRM contact ID into GA4 as user_id. Combined with BigQuery export, this allows full per-account behavior reporting. Effort is 5–10 days of dev plus CRM integration plus BigQuery setup. Payoff is the highest fidelity available — the team can answer "show me every ProDir page view by Manulife employees in the last 90 days" if the CRM holds the matching email domains. The hard requirement is a CRM with reasonable contact data; this option does not cover anonymous pre-form visitors.
UTM-based segmentation per ABM list
Tag every paid-ad URL aimed at a named-account list with a unique utm_audience parameter, then segment GA4 by that parameter. Effort is 1–2 hours, mostly UTM-template work and ad-trafficking discipline. Payoff is modest because it only captures the slice of named accounts that click on a paid ad — visitors arriving via SEO, Direct, or referrals from those same accounts are missed.
Option 1 plus Option 3 as the first wave
Run Option 1 and Option 3 in parallel for immediate company-level visibility across paid and unpaid traffic. Build toward Option 2 once a CRM is in place and integration capacity is available.