Document the purpose of the Developer ID property in code and elsewhere?

It seems good to document this in the README or in the code. Right?

It's just an identifier Google provided to attribute the integration. There is no account anyone can access, per the Google Tag docs.

Are folks thinking module maintainers are getting their analytics?

It's something new that's never been seen before on our team and there is precious little information available on this other than one page from Google explaining how, but nothing beyond that.

The developer ID request form is seemingly bound to a Google account of an individual.

Matt, can you link to any google.com hosted documentation that confirms what is said in #5 about access policies?

Sorry, I thought it had explained it more on that page. I'm not actively on the team which built this anymore, but I'll raise it and see if we can get the Google folks to chime in.

For the purpose of this issue: They generated the ID and gave it to us. Most of the times these IDs are used to attribute partners and usage of their implementation. Not for aggregated analytics. Basically, Drupal can be actually represented as a platform of users for Google Tag whereas it was unknown what platforms were being used.

For example, Mangeto has one as well: https://github.com/magento/magento2/blob/e6fc0ca2d4f380951f606f15715c904...

There may be some level of difference being that the Magento developer ID is likely under the umbrella of the Adobe Corporation whereas the google_tag module module doesn't really have a well known "legal entity" -- for lack of a better term -- behind it.

I appreciate anything you can dig up on this. Thanks

There really isn't anything I can add to what Matt said above. The developer id is generated by google (manually, you submit a form. We didn't do this because Google reached out to us looking to add these features to the official drupal module).

If it is associated with an account, it isn't one that Acquia, the Drupal Association, or any of the module maintainers owns or manages. All framework level applications are supposed to have this developer_id associated with it. Its in the google site kit, woocommerce, and every other officially supported integration by google.

https://github.com/woocommerce/woocommerce-google-analytics-integration/...

Updated I.S. with answers (best that can be done with known information).

@mglaman -

Sorry, I thought it had explained it more on that page.

Which page?

I agree with the issue summary as written. It would be nice if Google could document this program more to confirm the behavior for some of the unknowns. Since you're in contact with them I assume you're in a good position to negotiate that.

@japerry this is the second time (between the private issue and this public issue) where you have closed things out prematurely. Please let the conversation unfold before adjusting status.

Your module users are confused in a way that makes them think your module is malware. That should be a huge warning sign that something in the module can be improved to reduce that concern and instead you cavalierly close it out with a dismissive comment? That is not appropriate collaborative behavior.

Thanks, @greggles.

Which page?

https://developers.google.com/tag-platform/devguides/gtag-integration

For the record, I wholeheartedly believe that the use of the developer_id property is innocuous here on the part of the module maintainers. I was simply seeking more information on it.

The Google documentation uses language like "your customers", which implies somewhat of a different relationship with end-users than is traditionally implied by FOSS Drupal modules that have fluid maintainers.