All work

Enterprise campaign · Capabilities demo · Illustrative data

Demo: enterprise-level demand-gen engine at product launch

Using the launch of my clinical art program as the framework, I present this case study of a full demand-generation campaign wired so every whitepaper, email, and webinar traces to pipeline. Marketo runs execution, Salesforce holds the people and revenue, and Tableau reads it all.

Stack
Marketo · Salesforce · Tableau
Scope
Full demand generation
Data
Illustrative demo
This is a capabilities demonstration. It shows how I would architect and wire an enterprise launch. Figures are sample data to illustrate structure, not reported results.

Strategy

One objective, three audiences, one CTA each

The launch promotes the clinical art program using its real asset: a deep, peer-reviewed evidence base for art in clinical settings. The goal is qualified pipeline, not reach. Three audiences enter the same campaign and each is routed to a single, appropriate next step. This is the three-limb email split, defined as data before a single send is built.

SegmentWho they areMessageThe one CTA
AwarenessIndependent-practice office managers, early research stageThe research case for calming clinical artDownload whitepaper
ConsiderationPractice directors comparing options, closer to buyingMatched sets, room by room, ready to hangVisit product page
DecisionMulti-location and DSO ops leaders, highest valueConsistent art across every location, one programBook a program call

Content map: three whitepapers (the evidence case, HIPAA-neutral imagery and install guidance, and the multi-location program brief), three buyer-intent blogs, one 90-second launch video, a landing page and product pages, and a 30-minute on-demand webinar on evidence-based design for clinical groups.

The wiring

The plumbing: how one person's actions travel across every tool

Each tool holds one kind of information; the value is in the connections that let a single person be recognized in all of them, so the reporting at the end is true. Everything hangs on one shared label.

The join key
A single Campaign ID plus asset codes, carried in every link as UTM tags, threaded through every tool. ?utm_campaign=FY26-Q3-LAUNCH&utm_content=WP1

The Campaign ID and UTM naming is the thread through every tool. Consistent everywhere, the pipes carry clean data. Before launch, one test person is pushed through the whole chain to confirm nothing drops.

In the tools

What the wiring produces

With the plumbing in place, each tool shows its part of one connected story.

Production runs in Asana on the same Campaign ID, so on-time asset delivery and cost per asset sit in the same reporting layer as pipeline. The full stack: Asana for production, Marketo for execution, Salesforce for people and revenue, GA4 for web, Tableau for the picture.

Summary

The challenge in connecting the data doesn't sit in any single tool but in the plumbing that connects them. The above is a good all-purpose approach; if you are curious what this would look like in your organization, contact me at katy@pegmastudio.com.

Tools

MarketoSalesforceTableau AsanaGA4Data integration & UTM governance