Bentley | AI Pillar Campaign Performance

AI Pillar Overview

Campaign performance reporting with traceable KPIs, sourced from the AI Pillar data layer

SAMPLE DATA · NOT LIVE

Date range

Audience

Channel / team

Region

Offering (sample)

Comparison

Executive Performance Eight headline KPIs · click a metric for its lineage

Data note: All displayed performance figures and comparisons are illustrative; actual production values require validated source connections.

Campaign Performance Trend

Weekly engaged known contacts and campaign MQLs · source-normalized and deduplicated

Engaged known contactsCampaign MQLs

Audience Journey

Distinct identified people, then qualified downstream stages

The progression numerator requires a later action after the initial qualified engagement.

Engaged Audience by Channel

Unique known contacts, assigned to a first qualifying engagement source

Visibility vs. Response

Different units shown separately — not summed

Leadership Interpretation

What the executive page is designed to answer

1 · Are we visible?Reach, SOV, discoverability

2 · Are we resonating?Engaged contacts, actions

3 · Are we advancing?Progression, MQLs

4 · Is it translating to demand?Intent, influenced pipeline

eStore orders and revenue remain separate commercial outcomes rather than being added to qualified intent.

Visibility & Reach People-based reach separated from exposure and traffic

Unique Identifiable Reach by Channel

De-duplicated contact IDs; excludes anonymous pageviews and impressions

Share of Voice Trend

Bentley AI-term mentions / Bentley plus monitored competitor mentions

Web Discoverability

GA4 AI Hub and AI blog activity (not unique people)

LLM Discoverability

AI mentions, citations and referrals as distinct components

PR / Analyst Context

Visibility diagnostics only; never part of unique-person reach

Content & Audience Engagement

Content Engagement Actions by Channel

Interaction count, including anonymous social interactions · separate from known contact counts

Qualified Engagement Over Time

Content actions versus distinct engaged contacts (two different measures)

Content / Experience Performance

Illustrative assets and event themes across linked touchpoints

Email & Event Diagnostics

Operational metrics feeding the journey without inflating the executive reach count

Audience Progression & Marketing Qualification

Reached → Engaged → Progressed → MQL

Contact-level sequence; MQLs deduplicated across Salesforce AI Pillar subcampaigns

Progression by First Engagement Source

Progressed contacts / engaged contacts in each source

Journey Conversion

Conversion rates are people-based, not counts of repeated activities

Required Business Rules

Proposed data-layer logic applied in this demo

Identity resolutionContact/Lead master ID

Progression sequenceLater action only

Attribution window (demo)90 days

MQL program roll-upAI Pillar parent campaign

Internal AAG contactsExcluded from external MQL

Commercial Impact

Qualified Intent by Request Type

Distinct people in the headline KPI; requests can appear in multiple diagnostic types

Influenced Pipeline by Opportunity Stage

One opportunity counted once after an eligible prior campaign touch

Example Salesforce Opportunities

Synthetic opportunity rows and campaign-influence links; dollar values are not actual pipeline

eStore / Completed Commercial Results

Separate from requests, campaign influence, and pipeline

Influenced pipeline is a strategic relationship indicator, not proof that the campaign solely created the opportunity.

How the Data Layer Comes Together Proposed end-to-end integration architecture

01 · Source Systems

Raw observations and transactional records

SalesforceCampaigns, members, contact/lead IDs, opportunities

Marketo + Event PlatformsEmail, forms, webinars, Cvent/Splash/ON24

GA4 + Search/LLMContent actions, sessions, referrals, web/AI visibility

PR, Social, PIKC, eStoreMentions, engagement, internal enablement, sales

→

02 · Standardized Staging

Common naming and mapping, no KPI arithmetic yet

raw_campaign_activityevent ID · timestamp · event type · source

raw_crm_campaign_memberCampaign ID · Contact/Lead ID · response status

raw_digital_visibilitydate · source · term/page · metric · value

raw_opp / raw_orderCommercial records with authoritative IDs

→

03 · Conformed Semantic Layer

Identity, audience, hierarchy, attribution guardrails

dim_contact + dim_campaignUnified person key · parent AI Pillar hierarchy

fact_campaign_touchpointone action / person / timestamp / campaign

fact_visibility_dailyaggregate reach-independent exposure measures

bridge_opp_campaign_influenceeligible touch → opportunity once

→

04 · Executive / Diagnostic Views

Measures in Power BI, consistent across pages

Reach & Visibilityunique known people; SOV; LLM; web

Engagement & Progressionqualified actions; known contacts; MQLs

Commercial Impactdistinct intent; influenced pipeline; revenue

Dashboard & drilldownsexecutive scorecard + channel / source pages

The uploaded workbook specifies *what to measure and how metrics map*, not production SQL tables or live data. Source-table names and field contracts shown here are proposed design conventions to confirm with Martech, Salesforce and DBE teams.

Data Model: Required Keys & Fact Grain

Trace a KPI from Source to Visual

Select an executive metric

Data Quality Gates Before Production

Campaign hierarchyEvery event/digital campaign maps to one AI Pillar child and parent Campaign ID. Avoid name-based matching when stable IDs exist.

Person resolution & dedupeMap Marketo lead, event registrant and Salesforce Contact/Lead to one governed person key; retain anonymous activity separately.

Response-status definitionNormalize registered vs attended, responded vs non-responded, known content engagement and qualified MQL transitions.

Timing & attributionProgression must follow first engagement; opportunity influence requires an earlier qualifying touch within a governed lookback window.

Different measure grainsPeople ≠ content actions ≠ pageviews ≠ media impressions ≠ opportunities ≠ orders. Never combine units in one sum.

Finance & cancellationsCompleted eStore sales use canonical order ID, completed status, net amount and the finance-approved revenue recognition date.

Sample Data Inspector See normalized records behind the illustrations

First 10 rows of the current filtered sample; data generated deterministically in the browser

Executive KPI Definitions

Individual Metrics → Executive Outcomes Directly mapped from the workbook’s KPI Mapping Detail tab

“Proposed / needs validation” means a business rule or integration has not been verified. The demo numbers reflect illustrative model behavior only; they do not imply data readiness.

Feedback summary Every comment left on this wireframe, by page

Reference design: Bentley Sale Week dashboard screenshot · KPI source: AI Pillar Campaign Metrics workbook (Sheet1, Executive Scorecard, KPI Mapping Detail) · All displayed numbers, products, opportunities, and accounts are synthetic. Filters affect simulated data and metric measures; nothing is queried from production systems.