{"id":17368,"date":"2026-08-14T20:15:40","date_gmt":"2026-08-14T20:15:40","guid":{"rendered":"https:\/\/e-dialog.group\/blog\/piwik-pro-tag-manager-how-to-publish-changes\/"},"modified":"2026-08-14T20:18:47","modified_gmt":"2026-08-14T20:18:47","slug":"piwik-pro-tag-manager-how-to-publish-changes","status":"publish","type":"post","link":"https:\/\/e-dialog.group\/en\/blog\/piwik-pro-tag-manager-how-to-publish-changes\/","title":{"rendered":"Piwik Pro Tag Manager \u2013 How to Publish Changes"},"content":{"rendered":"
\n
\n

Piwik Pro has established itself as one of the leading privacy-compliant analytics alternatives, which is why switching to it is currently a top priority for many marketing and data teams. If you’re already familiar with Google Tag Manager, you’ll notice that version management in Piwik Pro works a little differently than you’re used to. <\/p>\n

The main difference from Google Tag Manager<\/h2>\n

In Piwik Pro Tag Manager, you can prepare all changes to tags, triggers, and variables in a single area. You can save changes up to a specific point in time in what’s called a “snapshot.” <\/p>\n

In GTM, you can use parallel workspaces to prepare changes for different tasks and then choose when the various changes should go live. In Piwik, you prepare all changes in a single workspace and can then save your changes in a snapshot until a specific point in time. <\/p>\n

Specifically, this means: If, for example, you want to implement tracking for a click on the website’s new call-to-action button, you can prepare these changes and save them in a snapshot.<\/p>\n

Let’s say you want to make an urgent adjustment to the “add_to_cart” tracking the next day. You want to do this right away, but you haven’t yet finished setting up the tracking for the new button. In that case, it’s good to know: As soon as you’re ready to publish the changes, all changes will go live. So make sure the half-finished button tracking is in a state where it can be published. <\/p>\n

How Snapshots Work in Piwik Pro<\/h2>\n

What might that look like when you’re preparing changes to different sets of tags? Here’s an example of what that might look like: <\/p>\n

First, we have our current configuration with a few tags and triggers; then we’ll add a tag and a trigger for LinkedIn tracking:<\/p>\n <\/div>\n<\/div>

\n
\n \"\" \"\" <\/div>\n<\/div>
\n
\n

Image: Adding tags & triggers. Source: e-dialog<\/small><\/p>\n

When we switch to the “Changelog”<\/strong> tab, we can see the new changes in the “Unpublished Changes”<\/strong> snapshot.<\/p>\n <\/div>\n<\/div>

\n
\n \"\" \"\" <\/div>\n<\/div>
\n
\n

Image: The changes to LinkedIn that have not yet been released. Source: e-dialog<\/small><\/p>\n

If you save the changes as a new snapshot, they will be displayed as Snapshot 14.1.<\/p>\n <\/div>\n<\/div>

\n
\n \"\" \"\" <\/div>\n<\/div>
\n
\n

Image: An overview of the new changes to LinkedIn. Source: e-dialog<\/small><\/p>\n

The new, as-yet-unreleased changes were moved from the “Unpublished”<\/strong> snapshot, which is now empty.<\/p>\n <\/div>\n<\/div>

\n
\n \"\" \"\" <\/div>\n<\/div>
\n
\n

Image: The snapshot of the unpublished changes is empty. Source: e-dialog <\/small><\/p>\n

Example: Publish New Tags and Triggers<\/h3>\n

Next, we’ll add a new tag for form tracking and create a snapshot for it. On the “Tags” tab, both the new LinkedIn tag and the new form tracking tag are marked as “unpublished.” When we look at the snapshot of the unpublished changes, there are no changes listed there, and it’s also not possible to publish this snapshot. <\/p>\n <\/div>\n<\/div>

\n
\n
\n
\n