Reporting Snapshot Target Object
A Reporting Snapshot Target Object is the specific custom object that an administrator designates to store the data captured by a Reporting Snapshot (also called Analytic Snapshot).
Definition
A Reporting Snapshot Target Object is the specific custom object that an administrator designates to store the data captured by a Reporting Snapshot (also called Analytic Snapshot). When a Reporting Snapshot runs on its defined schedule, it takes a point-in-time snapshot of a source report's data and maps each report column to a corresponding field on the target custom object, creating one new record per report row. Over time, the target object accumulates historical records, enabling trend analysis and historical comparisons through reports and dashboards built on the target object's data.
In plain English
“A Reporting Snapshot Target Object is the custom object you designate to store the data captured by a Reporting Snapshot. When the snapshot runs, each report row becomes a new record on the target object with report columns mapped to fields. Over time, the target accumulates historical records for trend analysis.”
Worked example
When Bracken Software's admin sets up a daily Reporting Snapshot of pipeline data, she designates a custom object called PipelineSnapshot__c as the Reporting Snapshot Target Object. Each scheduled run inserts records into PipelineSnapshot__c, with each report row becoming one new record and the report's columns mapped to corresponding fields on the target. After 90 days the target object has 90 daily snapshots accumulated; trend reports built on PipelineSnapshot__c show stage conversion rates over time. The Target Object is where the snapshot data physically lives - a custom object purpose-built to receive scheduled report dumps.
Why Reporting Snapshot Target Object matters
A Reporting Snapshot Target Object is the specific custom object that an administrator designates to store the data captured by a Reporting Snapshot (also called Analytic Snapshot). When a Reporting Snapshot runs on its defined schedule, it takes a point-in-time snapshot of a source report's data and maps each report column to a corresponding field on the target custom object, creating one new record per report row.
Over time, the target object accumulates historical records, enabling trend analysis and historical comparisons through reports and dashboards built on the target object's data. Target object design is important: field types must match the source report column types, field names should be meaningful, and the object should be designed for reporting use rather than operational use. Mature snapshot implementations have dedicated target objects with clear names indicating their purpose.
How to create Reporting Snapshot Target Object
Reporting Snapshot Target Object is the Custom Object you create to receive snapshots of report data over time — "capture today's pipeline by stage every Friday." The target object stores the snapshot rows. Setup involves creating the Custom Object first, then configuring the Reporting Snapshot to write to it.
- Create a Custom Object to receive snapshots
Setup → Object Manager → Create → Custom Object. Name it after the snapshot purpose ("Pipeline Snapshot").
- Add fields matching the report's columns
For each report column you want to snapshot, add a matching field on the Custom Object — same data type, similar name.
- Add a Snapshot Date field
Date field. The snapshot job stamps today's date on each row written.
- Open Setup → Reporting Snapshots
Setup gear → Quick Find: Reporting Snapshots → Reporting Snapshots.
- Click New Reporting Snapshot
Wizard walks through source report, target object, field mapping, schedule.
- Pick the source report and target object
Source: a tabular Report. Target: the Custom Object you just created.
- Map source columns to target fields
For each report column, pick the matching field on the target object. Mismatches fail at save.
- Schedule the snapshot
Daily / Weekly / Monthly. The job runs and inserts a row per source-report row, with today's date.
Required as the target.
Recommended — without it, you can't tell snapshots apart by date.
Required. Source-to-target column mapping must cover the data you want to snapshot.
- Source report must be a Tabular report — not Summary or Matrix. Reporting Snapshots only support Tabular.
- Snapshots count against the target object's storage. Daily snapshots of a 100k-row report add up — plan retention / archival.
- If the source report changes columns after the snapshot is configured, the field mapping breaks. Edit the Reporting Snapshot to re-map after report changes.
How organizations use Reporting Snapshot Target Object
Created dedicated target objects for each snapshot purpose, with clear naming for easy identification.
Designs target object field types to match source report columns for clean data.
Maintains target objects purely for snapshot data, not operational use.
Trust & references
Straight from the source - Salesforce's reference material on Reporting Snapshot Target Object.
- Define a Reporting SnapshotSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Reporting Snapshot Target Object?
Q2. What happens when a snapshot runs?
Q3. What should target objects enable?
Discussion
Loading discussion…