Salesforce Marketing Cloud Data Views: _JourneyActivity (Journey Builder)

Posted on by admin

The _JourneyActivity data view in Salesforce Marketing Cloud (SFMC) provides detailed metadata about each activity within Journey Builder journeys. It’s essential for joining journey activity records to email tracking data views and analyzing how individual journey components behave.

In this blog, we’ll explore the structure and purpose of the _JourneyActivity data view, describe its key fields, and provide example SQL queries for real-world use cases like performance tracking and join operations.

What is the _JourneyActivity Data View?

The _JourneyActivity data view logs details about all activities that make up a journey, such as Email Sends, Waits, Splits, or Decision elements. It includes activity names, types, and keys, making it easy to identify and report on specific components within a journey.

Key Benefits of _JourneyActivity Data View

  • Join to Tracking Data: Link activities to _Sent, _Open, _Click using the JourneyActivityObjectID.
  • Identify Email Definitions: Match activity to Triggered Send Definitions.
  • Understand Journey Design: Analyze how different activities are used across journeys.
  • Audit Journey Structure: Ensure compliance and documentation of all actions.

Fields in _JourneyActivity Data View & Their Uses

FieldTypeDescription & Use Case
VersionIDText(36)Unique identifier for the version of the journey. Used to join with _Journey.
ActivityIDText(36)Unique identifier for each activity within the journey version.
ActivityNameText(200)Friendly name of the activity (e.g., “Welcome Email”). Useful for reporting.
ActivityExternalKeyText(200)External identifier for the activity, often used in API calls or external integrations.
JourneyActivityObjectIDText(36)Used to join with tracking data views such as _Sent, _Click, _Open, _Bounce.
ActivityTypeText(512)Type of activity (e.g., Email, Wait, Decision Split, Update Contact). Used for filtering and categorization.

When and Why to Use _JourneyActivity Data View?

When to Use?

  • When building performance dashboards by journey activity.
  • To join email events to specific Journey Builder activities.
  • For compliance reporting on journey structure.
  • To identify all activities used across multiple journeys.

Why Use It?

  • Deep Analysis: Isolate results of specific emails or decisions within a journey.
  • Operational Insight: Track journey complexity and frequency of certain actions.
  • Effective Debugging: Identify which activities might be underperforming.
  • Powerful Reporting: Connect journey structure with engagement metrics.

10 Example Scenarios and Queries

1. List All Email Activities in Journeys

SELECT ActivityName, VersionID, ActivityType 
FROM _JourneyActivity 
WHERE ActivityType = 'EMAIL'

Use Case: Audit all email sends across journeys.

2. Count of Activities by Type

SELECT ActivityType, COUNT(*) AS Total 
FROM _JourneyActivity 
GROUP BY ActivityType

Use Case: Understand most-used components in Journey Builder.

3. Activities by Journey Version

SELECT VersionID, ActivityName, ActivityType 
FROM _JourneyActivity 
WHERE VersionID = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'

Use Case: Retrieve components for a specific journey version.

4. Join to _Sent Using JourneyActivityObjectID

SELECT s.SubscriberKey, s.EventDate, j.ActivityName 
FROM _Sent s 
JOIN _JourneyActivity j 
ON s.JourneyActivityObjectID = j.JourneyActivityObjectID

Use Case: Identify which email activity generated the send.

5. Recently Modified Activities

SELECT ActivityName, ActivityType, VersionID 
FROM _JourneyActivity 
WHERE VersionID IN (SELECT VersionID FROM _Journey WHERE ModifiedDate >= DATEADD(day, -30, GETDATE()))

Use Case: Find activities within recently updated journeys.

6. Group Activity Types by Journey

SELECT j.JourneyName, a.ActivityType, COUNT(*) AS Count 
FROM _JourneyActivity a 
JOIN _Journey j ON a.VersionID = j.VersionID 
GROUP BY j.JourneyName, a.ActivityType

Use Case: Analyze usage of activity types per journey.

7. Retrieve Unique Activity Names by Type

SELECT DISTINCT ActivityName 
FROM _JourneyActivity 
WHERE ActivityType = 'WAIT'

Use Case: List all unique Wait activities.

8. Identify Triggered Sends by Activity External Key

SELECT ActivityName, ActivityExternalKey 
FROM _JourneyActivity 
WHERE ActivityType = 'EMAIL'

Use Case: Map email activities to triggered definitions.

9. Join Journey and Activity for a Full Map

SELECT j.JourneyName, a.ActivityName, a.ActivityType 
FROM _Journey j 
JOIN _JourneyActivity a ON j.VersionID = a.VersionID

Use Case: Visualize all journeys and their components.

10. Email Performance by Activity in a Journey

SELECT j.ActivityName, s.SubscriberKey, s.EventDate, s.JobID 
FROM _JourneyActivity j 
JOIN _Sent s 
ON j.JourneyActivityObjectID = s.JourneyActivityObjectID 
WHERE j.ActivityType = 'EMAIL'

Use Case: Track engagement at the email activity level.

Conclusion

The _JourneyActivity data view offers a clear lens into your Journey Builder architecture, giving you the ability to link activity-level detail with subscriber-level behavior. When used with _Journey, _Sent, _Click, and _Open, it becomes a cornerstone for comprehensive journey reporting and optimization.

Related Posts