Additional consent mode options

For reference, this came up implementing the suggested configuration for Osano.

https://docs.osano.com/hc/en-us/articles/22469433444372-Google-Consent-M...

Unfortunately I don't think there is a public api to retrieve all of the consent mode options, so they'd have to be hardcoded into the google tag form.

Fortunately, I think using the existing advanced options, under consent mode, you could enable more checkboxes to explicitly set other ones.

Ok, probably makes sense to have some support for the privacy stuff that is documented. "functionality_storage" "personalization_storage" "security_storage"

As far as doing this in the current advanced settings, I don't see a way atm. Are you suggesting adding something to the advanced settings to support it?

Since ad_storage, analytics_storage, ad_user_data and ad_personalization are already hardcoded, I just added the suggested configuration mentioned in https://docs.osano.com/hc/en-us/articles/22469433444372-Google-Consent-M...

However I do agree this should be configurable in the advanced settings form. (not only through checkboxes, but also with a textarea where one can add custom consent items)

Careful about that Osanto article, it contains a substantial amount of false information. (Now I know why this Module has so many problems).

Osanto is in the business to sell software, and they want to make themselves seem more important than they really are to people who don't know better. Plus, they don't know what they're talking about in places, which allowed me to get my fill of laughs for the day. They're not an impartial source to be cited as authoritative. The same applies to Google.

The "suggested" default configuration is a great example of false information. Nobody should tell you what your Default Consent settings should be; that's the job of your attorneys because your company will be held responsible....not clueless Osanto or deceptive self-serving Google. That's problem #1.

Their suggested default configuration of Denied is becomes problem #2 because this could cause senseless gaps in analytics data for some users.

Osanto reveals that they don't have a good grasp on the underlying subject matter by advising users to place that code snippet.

That configuaration codeblock is only intended to be used by people who won't be using Google Tag Manager to initiate the CMP. For those people who are using GTM to initialize consent, that default code tag is unnecessary.