@agneslesagegmailcom I am sorry for the delay in answering to you.
I am sorry but I am not sure to understand well the problem.
1> accept GA tracking a priori from first access and first page
Smart Cookie Kit should block a priori. GA should not be blocked only if it is anonymized.
If I don’t tick “Block Google Tag Manager”, then visits are tracked, even when user refuses cookies.
This is correct. If you don’t tick “Block GTM”, the way GA works depends on how you have configured GTM!
Please, read the next point to get more details about this.
If I tick both “Block Google Tag Manager”, and although I also ticked “Implicit consent on scroll”, visits are not tracked, even when scrolling, and even when clicking, unless I explicitly say “accept cookies”
The “implicit consent” works only the first time a user visits the site. To be more precise: it works only when there is not a previous cookie preference from the user. If a user refuses cookies, the implicit consent will be bypassed, as the user has choosed to get the cookies disabled. The “implicit consent” will trigger the acceptance only if the user ignores the banner and starts to scroll.
So, this issue could depend on the fact that, testing the plugin, you have previously refused cookies.
Would you say of there is anything special to take into account when using that Duracelltomi GTM plugin?
There is no need to take special configurations because I have solved that issue to make plugins work well togheter ??
Could you please outline what should be the proper setup to design in GTM?
GTM can be used to do a lot of work (tracking, customizations, …) with its tags, so I can’t decide to block GTM for all. Blocking GTM or not depends on how GTM is used on a specific site. If GTM fires only tracking codes, the site admin can decide to block GTM with my plugin. If GTM is used for stuffs that do not depend on cookie preferences, the site admin should manage the situation in a different way. The proper way, in this situation, is to trigger the GTM Tags that contains tracking codes when specific custom events occurs (“statisticsCookiesEnabled” and “profilingCookiesEnabled”): you can refer to this guide: https://support.google.com/tagmanager/answer/7679219).
In addition to the events that “tells” to GTM that cookies are accepted, the plugin fires others events when cookies are refused.
Is it a bit more clear? ??
Let me know. Nicola.