1

Microsoft – Campaign/Journey ID Table Feature


Background:

My client is transitioning from Marketo to CI-J. In Marketo, a Program/Container model exists where all related campaign items (emails, forms, landing pages, events, etc.) are linked together under a single parent. This enables easy grouping, reporting, and comparison across campaigns.


Gap in CI-J:

In CI-J, assets (emails, forms, events, journeys, SMS, push, etc.) exist as separate entities without a unifying Campaign ID. This creates challenges for reporting, governance, and cross-asset analysis, particularly for enterprise-scale clients running multiple campaigns at once.


Proposed Solution – Campaign/Journey Table with Campaign/Journey ID:

  • Create a Campaign/Journey record → automatically generates a unique Campaign/Journey ID.
  • Assets link to Campaign → Emails, Forms, Event Registrations, Events, Journeys, SMS, Push, Custom Channels, Activities.
  • Centralized Reporting at the Campaign level:
  • Emails: Opens, Clicks, Opt-outs, Heatmaps, etc
  • Forms: Submissions, Visits, Conversions, etc
  • Event Registration: Submissions, Check-ins, Unregistered, Attendance, etc
  • Events: Speakers, Sponsors, Payments, Goals, Event Type, Venue, Layout, Vendors, etc
  • Journeys: All journeys linked to the campaign + analytics, etc
  • Other Channels: Push, SMS, Custom Channels, and logged activities , etc
  • Referrer URL: See where a contact came from (e.g., social link → registration), etc
  • Comparisons between campaigns, including the ability to compare 2–6 events side by side


Business Benefits:

  • Enables holistic campaign/journey reporting — one place to view multi-asset performance.
  • Allows apples-to-apples comparisons between campaigns (e.g., 2–6 events).
  • Simplifies governance by enforcing campaign alignment across assets.
  • Replicates a familiar Marketo “container” concept, easing migration for enterprise clients.


STATUS DETAILS
New