The _Job data view in Salesforce Marketing Cloud (SFMC) provides comprehensive information about each email send job. This data view is crucial for tracking and reporting on the performance, configuration, and delivery of every email you send from your account.
In this blog, we’ll break down the fields in the _Job data view, explore its practical use cases, and share SQL queries to help you make the most of your send job data.
What is the _Job Data View?
The _Job data view tracks metadata related to email sends in SFMC. It includes timing details, user information, configuration data, and other attributes related to both standard and triggered email sends.
Key Benefits of _Job Data View
- Campaign Diagnostics: Review job status, send times, and email metadata.
- Advanced Reporting: Combine with engagement data for performance dashboards.
- Trigger & Automation Tracking: Analyze automated vs. one-off sends.
- Audit History: Track who scheduled and modified each job.
Fields in _Job Data View & Their Uses
| Field | Type | Description & Use Case |
|---|---|---|
| AccountID | Number | The SFMC account that initiated the job. Important for multi-account setups. |
| AccountUserID | Number | ID of the user who initiated the send. Use to track send origin. |
| JobID | Number | Unique identifier for each send job. Core field for joining with other data views. |
| EmailID | Number | Internal ID of the email content used. |
| FromName | Text(130) | The sender’s name used in the email. Used for compliance and branding review. |
| FromEmail | The sender’s email address. | |
| SchedTime | Date | The time the job was scheduled. Useful for comparing against actual delivery. |
| PickupTime | Date | The time the job began execution. |
| DeliveredTime | Date | The time the email was delivered. Used for performance tracking. |
| TriggererSendDefinitionObjectID | Text(36) | Triggered send object ID. Useful in Journey Builder and automation reporting. |
| TriggeredSendCustomerKey | Text(36) | Key used to identify the triggered send definition. |
| EventID | Text(50) | Unique event ID associated with the job. |
| IsMultipart | Boolean | Indicates if the email was sent as multipart MIME (HTML + plain text). |
| JobType | Text(50) | Type of job (e.g., TriggeredSend, SingleSend, GuidedSend). Helps classify campaign types. |
| JobStatus | Text(50) | Current status of the job (e.g., Complete, Cancelled). |
| ModifiedBy | Number | ID of the user who last modified the job. |
| ModifiedDate | Date | Date the job was last updated. |
| EmailName | Text(100) | The name of the email asset used in the job. |
| EmailSubject | Text(200) | Subject line of the email. |
| IsWrapped | Boolean | Indicates if links were wrapped for tracking purposes. |
| TestEmailAddr | Email used in test sends (if applicable). | |
| Category | Text(100) | Job category or label used for classification. |
| BccEmail | BCC email addresses used in the send. | |
| OriginalSchedTime | Date | The originally intended scheduled time. Useful for identifying delays. |
| CreatedDate | Date | The date the job was created. |
| CharacterSet | Text(30) | The character encoding used in the email. |
| IPAddress | Text(50) | Always returns null. Reserved for future use. |
| SalesForceTotalSubscriberCount | Number | Number of Salesforce CRM subscribers in the send. |
| SalesForceErrorSubscriberCount | Number | Number of Salesforce subscribers who encountered send errors. |
| SendType | Text(128) | Send mechanism used (e.g., triggered, batch, automation). |
| DynamicEmailSubject | Text | If applicable, the dynamic subject line generated for the job. |
| SuppressTracking | Boolean | Indicates if tracking was disabled for the job. |
| SendClassificationType | Text(32) | Type of classification applied to the job. |
| SendClassification | Text(36) | Send classification used (e.g., Commercial, Transactional). |
| ResolveLinksWithCurrentData | Boolean | Indicates whether dynamic links were resolved with live data. |
| EmailSendDefinition | Text(36) | Reference to the email send definition used. |
| DeduplicateByEmail | Boolean | Whether deduplication by email address was applied. |
When and Why to Use _Job Data View?
When to Use?
- After campaign launch for job diagnostics and performance audits.
- When analyzing automation and journey sends.
- When building dashboards and send summaries.
- To review send settings and metadata for compliance or optimization.
Why Use It?
- Complete Visibility: Access all send-level metadata.
- Performance Analysis: Compare job timing with engagement.
- Compliance and Governance: Validate job configurations.
- Troubleshooting: Investigate delivery delays and configuration errors.
10 Example Scenarios and Queries
1. Retrieve All Completed Jobs from the Last 30 Days
SELECT JobID, EmailName, EmailSubject, DeliveredTime
FROM _Job
WHERE JobStatus = 'Complete'
AND DeliveredTime >= DATEADD(day, -30, GETDATE())Use Case: Analyze recently completed email sends.
2. List Jobs with Dynamic Subject Lines
SELECT JobID, EmailName, DynamicEmailSubject
FROM _Job
WHERE DynamicEmailSubject IS NOT NULLUse Case: Track performance of dynamic content testing.
3. Compare Scheduled vs. Delivered Times
SELECT JobID, SchedTime, DeliveredTime
FROM _Job
WHERE DeliveredTime IS NOT NULLUse Case: Identify delivery delays.
4. Retrieve All Triggered Sends
SELECT JobID, TriggeredSendCustomerKey, EmailName
FROM _Job
WHERE JobType = 'TriggeredSend'Use Case: Filter for Journey Builder and triggered campaigns.
5. BCC Monitoring and Compliance
SELECT JobID, EmailName, BccEmail
FROM _Job
WHERE BccEmail IS NOT NULLUse Case: Track compliance with BCC use policies.
6. Count of Jobs by Status
SELECT JobStatus, COUNT(*) AS TotalJobs
FROM _Job
GROUP BY JobStatusUse Case: Understand current job statuses across your instance.
7. Email Send Volume by User
SELECT AccountUserID, COUNT(*) AS TotalJobs
FROM _Job
GROUP BY AccountUserIDUse Case: Attribute sends to users for accountability.
8. Track Jobs with Suppressed Tracking
SELECT JobID, EmailName
FROM _Job
WHERE SuppressTracking = 1Use Case: Identify jobs where engagement tracking is turned off.
9. Identify Jobs with Salesforce CRM Errors
SELECT JobID, SalesForceErrorSubscriberCount
FROM _Job
WHERE SalesForceErrorSubscriberCount > 0Use Case: Troubleshoot CRM integration issues.
10. Join _Job with _Sent for Job-Level Reporting
SELECT j.JobID, j.EmailName, s.SubscriberKey, s.EventDate
FROM _Job j
JOIN _Sent s
ON j.JobID = s.JobIDUse Case: Combine send metadata with engagement details.
Conclusion
The _Job data view in SFMC is an essential resource for email send tracking, diagnostics, and analysis. With detailed metadata on timing, configuration, classification, and email content, it enables marketers and analysts to deeply understand the setup and success of every send.
Use _Job in combination with _Sent, _Open, _Click, _Bounce, and _Complaint to create a full-funnel campaign performance dashboard.