What this means for your store
Agencies often build tags in a sandbox container and hand you a JSON export. Merge import adds entities from that file into your current workspace without wiping what you already run. Unlike overwrite import, it keeps existing tags and surfaces naming conflicts so your team chooses what lands in production.
Scenario on a real storefront
Your performance agency built TikTok and Pinterest purchase tags in their sandbox. You merge their export into the governed production container and resolve conflicts before anything touches live traffic:
Admin → Import Container → Merge
Select: agency-sandbox-export.json
Workspace: Default Workspace
Conflict review:
- Skip agency "GA4 Config" (production already has GA4 Configuration)
- Import: TikTok - Purchase, Pinterest - Checkout
- Merge trigger "CE - purchase" only if equivalent to existing
Preview → Tag Assistant → test purchase on staging
Publish with version note: "Merged agency social tags Q2"What to do next
- Never merge straight to production without Preview on staging - duplicate triggers are the usual surprise.
- Prefix imported folders with agency slug + date so ownership is obvious six months later.
- Export your container before merge; rollback from saved JSON beats reconstructing from memory.
Bottom line
Merge import is how in-house teams absorb agency containers without losing consent and core analytics. Import selectively, resolve conflicts explicitly, preview on staging, then publish.