Tag Concierge

Dear JSL,

Thank you for your feedback. I understand your frustration, but I’d like to clarify that only 4 days have passed since your support request was submitted on February 22nd in the evening.

The free version of the plugin is indeed supported by the developer, but as it is a free product, support is provided during the developer’s free time. If you require more immediate assistance, you may want to consider purchasing the Pro version, which includes priority support.

I apologize for the delay in responding to your ticket. I can assure you that your support request, along with other pending tickets, will be addressed during the upcoming weekend.

Regarding the styling issues you’ve mentioned, your feedback is valuable and will be taken into consideration for future updates.

Thank you for your patience and understanding.

Hi @dannyfoo ,

the latest release 1.12.4 should resolve that error.

Let me know if it doesn’t or if you have any other issues.

All the best,

Hi @dannyfoo,

thanks for reporting. Can you confirm is that happening on a website where WooCommerce is not installed or activated? If yes, this is a known problem which wasn’t fixed before since our plugin is dedicated for Woo, but we are going to patch that in the very next release.

Let me know, all the best,

Micha?

That’s great to hear! I’m glad the update resolved the issue. Thank you for letting me know.

Have a great day as well!

@matt09238509235802 version 1.12.2 that fixes this issue has just been released. Please let me know if the problem is now resolved. I sincerely apologize for any inconvenience caused.

All the best,
Micha? from Tag Concierge

Hello @matt09238509235802, thank you for reporting and detailed description. We are working on it.

All the best,
Micha? from Tag Concierge

Great, I am glad the problem has been solved.

All the best,
Micha? from Tag Concierge

Hello @maginem, sorry for delayed reply. I would need your store url and GTM debug preview url in order to debug this issue. If you don’t want to disclose it here, please contact us at [email protected].

All the best,
Micha? from Tag Concierge

Hello @maginem, thank you for reaching out.

I apologise for the confusing description of the setting options. You can check “Yes, I inject GTM snippets differently”, that option will prevent doubled GTM injection.

Nevertheless it’s highly recommended to inject GTM snippets via our plugin, especially when you use our Consent Mode Banner plugin, which easily integrates with tracking plugin.

All the best,
Micha? from Tag Concierge

• This reply was modified 7 months ago by Tag Concierge.

Perfect! If you need anything else you know where to find us ??

All the best,

Hello @filipblomqvistb

thanks for your feedback. We are still working out all the rough edges of this plugin. We appreciate your patience as we continue to refine it.

Regarding the consent withdrawal there is a basic feature for that (we will add this information to the documentation soon).
You can drop anywhere on the page (for instance in the footer as WordPress widget) a link with following “href” param: “#consent-banner-settings” like this:

<a href="#consent-banner-settings">Consent Preferences</a>

This will open the same settings view, so user can modify and save their preferences.

Let me know if that helps or if you have any other issues with the plugin ??

All the best,

Thanks @alexgraphicd for getting back to us.

I will close this thread but please don’t hesitate to open another one or reach out in case of other issues or comments.

All the best,

Hey again ??

@alexgraphicd @filipblomqvistb can you try running updated version 1.0.1?

The ordering for initial script that should optionally create gtag JS function wasn’t correct.

Let me know, if any other issue persist I would be happy to fix it.

Thank you both for reporting the issue.

The gtag is not required, this is a bug related to the order of all JS files and inline code.

Let us quickly refine a fix and share with you a patched version soon.

All the best

Hey @saracoming,

nice, great to hear that you solved it. Do you read the product variant details from HTML directly?