Pushing vs Loading Snapshot Updates in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Push Updates syncs refreshed snapshot changes to sub-accounts that previously loaded that snapshot. Load Snapshot adds items to an existing sub-account without deleting anything.

Two different actions, two different outcomes. Use the right one for the job.

Pushing Updates sends changes from a refreshed snapshot to sub-accounts that previously loaded it.
Loading a Snapshot adds snapshot items into an existing sub-account without deleting or modifying existing content.

Part 1: Push updates to sub-accounts

Use this when you have updated the source sub-account, refreshed the snapshot, and want to sync those updates to sub-accounts that already use it.

Always refresh the snapshot first so the latest changes are included in the push.

How to push updates

Go to Agency View > Account Snapshots.
Find the snapshot and click the Refresh icon to pull recent changes.
Click the Push Updates icon next to the snapshot.
Confirm the prompt by clicking OK.
Select which sub-accounts to update.
Choose which assets to push (for example, workflows, funnels, forms).

What happens during a push

New assets added via refresh are added to the sub-accounts.
Existing assets are overwritten with the latest snapshot version.
Custom changes a client made to snapshot-linked assets will be lost unless those assets were duplicated first.

Behavior reference

Item	Outcome
Items originally created by the snapshot	Overwritten during push
Items edited manually in the sub-account	Reverted if included in push
Items duplicated by the user (e.g., copy of a campaign)	Untouched
Custom values	Never edited or deleted
Users assigned in campaigns	Not modified
External agency accounts	Cannot receive push updates — must re-import via shared link

Prevent overwrites for client customization

If you want a client to be able to customize an asset without losing edits during the next push:

Create a copy of the original item (for example, Campaign X (Copy)).
Have the client edit the copy instead of the original.
Update connected automations to use the copy.

The copy is not tracked by the snapshot and stays untouched during pushes.

Part 2: Load snapshots into existing accounts

Use this when you want to add snapshot content to a live sub-account manually.

Nothing gets deleted.
Snapshot items are added on top of existing content.
Loading the same snapshot multiple times duplicates items.

Bulk loads: for agencies loading snapshots into 100+ accounts, the first 100 are processed immediately, the next 100 after 10 minutes, then every 10 minutes thereafter in batches of 100.

Use Load Snapshot for new client onboarding. Use Push Update when an onboarded client needs synced changes.

Frequently Asked Questions

What's the difference between pushing updates and loading a snapshot?

Pushing updates syncs refreshed snapshot changes to sub-accounts that already loaded that snapshot, overwriting matching items. Loading a snapshot adds items to a sub-account without deleting anything that's already there.

Will a push delete a client's custom edits?

Push will overwrite items that were originally created by the snapshot, including any client edits to those items. Items the client duplicated themselves are untouched, and custom values, users, and unrelated assets are preserved.

How do I let clients customize assets safely?

Have them duplicate the original snapshot-linked asset and edit the copy. The duplicate isn't tracked by the snapshot, so future pushes won't overwrite it.

Can I push updates to external agencies?

No. Push updates only work inside your own agency. External agencies must re-import a fresh share link to receive updates.