Hi @urskai,
Sorry to hear about your experience, please know that we would be happy to help you though.
As you have “versions” in your Tag Manager container, you should be able to revert to a previous state of the container before those changes. You will find this functionality under “Versions” in Tag Manager.

Please know that the article mentions that you can either override, or merge the imported container with your existing container (https://complianz.io/importing-tag-manager-container/), whereby you would likely want to select “Merge” in your case.
Let me know if you have any further questions.
Kind regards, Jarno
Thread Starter
urskai
(@urskai)
Hi @jarnovos,
It’s interesting that it takes you half a day to respond to a customer review, and in more then a day you still have not replied to a single of my support tickets (and as I mentioned in my review, it took 1 day after purchasing the 5 sites premium version of your product) for me to be able to submit the support ticket, because the support form was not active before. I have also asked for a full refund (2nd day after purchasing), and have not received a reply from your team.
But since you have apparently chosen this as a channel to actually reply to the customers, I will write everything here.
The article, which is the only form of instructions you offer for Consent v2 implementation (so there is no proper documentation tutorials or anything), starts with you need to import the container into your container. Yes the article say that Google Tag Manager gives you an option to override or merge the container. In both cases you can retrieve the version, but your settings remove triggers from all the tags, so when you have a little bit more complex container, you are left with 4 hours of work.
And I will write down the instructions – which again you failed to do in your answer: you need to retrieve the old version, and then in the overview tab in the left navigation click on 3 dots next to every item you want to restore and click “abandon change”. It’s best to start with variables, then continue with triggers, and then tags. This will most likely not automatically restore all your settings and you will probably still need to manually add variables to some triggers and triggers to the variable. To fully restore the container to the previous settings, you will also need to manually check all the folders, tags, triggers, and variables and manually delete them – your company of course does not provide any documentation to what s*** was actually imported.
So that’s just the problems you cause user in the first step of this article, not to mention you don’t actually provide any instructions on what user need to do on their own to set everything in a way that it’s compliant to Consent v2. So take a look at you competitors, see how instructions are prepared correctly (scenario—> solution, click-by-click instructions accompanied with images). And on top of what triggers and variables user needs to have in their tag (and written instructions on how to do them instead of dumping some BS container on them), you should at least cover the most common scenarios – like how to combine your consent option with tags that use custom triggers, and similar.
So overall, absolutely awful product, no support (not even in documentation, let alone receiving any answers to submitted tickets).
You could have a slogan: Complianz: Buy Solution, Get Problems.
Hi @urskai,
I am very sorry to read about your experience. Please know that this is not the experience that we envision for either Free or Premium users.
We are experiencing a major support increase due to Consent Mode V2, which is part of the Premium plugin. That’s no excuse, but it is a challenge to provide in-depth feedback and instructions on every Consent Mode implementation.
If you are still open to receiving our help with your implementation, please email us directly at support(at)Complianz.io. We will do our very best to address your questions to the best of our ability.
Kind regards,
Leon