Snapshot Version Management for Sparkforge Agencies

Snapshot Version Management is part of the Snapshot asset viewer in Sparkforge. Each successful refresh creates a new version with a chronological history and per-version detail of what changed. Agencies use this to audit templates and keep clients aligned on the exact build.

What you get with versioning

• Audit trail: Chronological list of versions with high-level change summaries.
• Faster troubleshooting: Compare versions to verify exactly what shipped between a share and an import.
• Team alignment: Confirm everyone is on the same version before pushing or sharing.
• Operational accuracy: Product category labels point you to the right area in the sub-account to locate assets.
• Less busywork: Built-in source-of-truth history replaces manual change spreadsheets.

Version History panel

The Version History panel lists every version created by a successful refresh.

• Chronological list of versions with date and time.
• Concise change summary per version: Added, Removed, and Synced counts versus the previous version.
• Click any version to open the detailed summary.

Version detail (Added, Removed, Synced)

Opening a version shows assets grouped by type (Funnels, Workflows, Emails, and so on).

• Added: assets new in this version.
• Removed: assets no longer present.
• Synced: assets included in both the previous and current version with no change.

Where version references appear

Version references show up across snapshot lists so you can confirm which version was shared or imported.

• My Snapshots
• Imported Snapshots
• Shared Snapshots

How to use Snapshot Version Management

1. Go to Agency view → Account Snapshots → My Snapshots.
2. Click a snapshot name to open the Snapshot asset viewer.
3. Switch to the Version History tab to see all recorded versions.
4. Click any version row to open the detailed Added/Removed/Synced summary.
5. After updating assets, click Refresh Snapshot in My Snapshots. A new version is created when the refresh succeeds.
6. Before sharing or importing, use the version reference in the snapshot lists to confirm everyone is aligned.

Practical use cases

Decide what to push at scale

Before pushing updates to many sub-accounts, confirm the intended version in Version History and scan the delta to avoid pushing incomplete changes.

Pre-share QA

After updating assets, open Version History and review the latest Added/Removed/Synced summary to confirm only the intended changes are included.

Align with partners and clients

Compare the version reference in My Snapshots with what collaborators see in Imported or Shared Snapshots so everyone works from the same build.

Troubleshoot missing assets after import

If a sub-account reports a missing funnel or workflow, open the Version Details for the version they imported to confirm whether the asset was Removed or Synced.

Verify cleanup of deprecated assets

Refresh the snapshot and confirm retired assets appear under Removed in the latest version.