Current Limitation

• Pipeline Smart Tags can only be created and managed within individual sub-accounts.

• When pipelines are included in a snapshot, Smart Tags are not transferred into the target sub-account.

• As a result, workflows and automations referencing those tags break or require manual reconfiguration.

Expected Behaviour

When applying a snapshot to a sub-account:

• Pipeline Smart Tags should:

• Be automatically created in the sub-account

• Remain correctly mapped to their respective pipeline stages

• Retain references used by workflows and triggers

• All automations relying on these tags should function immediately post-deployment.

Why This Matters

• Snapshots are intended to enable repeatable, no-touch deployments.

• Manual Smart Tag recreation:

• Slows onboarding

• Introduces errors

• Undermines snapshot reliability for agencies and SaaS users