[ADD] google_tag_manager_advanced_tracking: GA4 API Secret placeholder field - #483
Open
fw-bot-adhoc wants to merge 1 commit into
Open
[ADD] google_tag_manager_advanced_tracking: GA4 API Secret placeholder field#483fw-bot-adhoc wants to merge 1 commit into
fw-bot-adhoc wants to merge 1 commit into
Conversation
…r field Add a dummy `ga4_api_secret` Char on website (+ res.config.settings related field and its setting under Website > Tracking & SEO), mirroring the v19 field defined by website_sale_google_analytics_4. In v18 the field only stores the value: it lets clients generate and load their GA4 Measurement Protocol API Secret (server-side) before the v18->v19 upgrade. The GTM-deprecation Upgrade Line migrates the value to the homonymous field of website_sale_google_analytics_4 during the upgrade. Task #66923. X-original-commit: ee833fc
Contributor
|
|
Author
|
@JrAdhoc @augusto-weiss cherrypicking of pull request #481 failed. stdout: Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).
More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
you can use 
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Qué
Agrega un campo
ga4_api_secret(Char) enwebsite, su related enres.config.settingsy el setting correspondiente bajo Website → Tracking &SEO, justo debajo del setting nativo de Google Analytics.
Espeja el campo homónimo que en 19.0 define
website_sale_google_analytics_4.Por qué
En v18 el campo es un placeholder: solo almacena el valor. Permite que los
clientes que hoy están en 18.0 generen y carguen su GA4 Measurement Protocol
API Secret (server-side) antes de actualizar a 19.0, donde
website_sale_google_analytics_4lo consume para los eventos server-side(purchase, refund).
Durante el pase v18→v19, el Upgrade Line de deprecación del stack GTM migra el
valor al campo homónimo del módulo nuevo. Mantener el mismo nombre técnico
(
website.ga4_api_secret) es lo que hace que la columna sea reutilizable y eldato no se pierda.
Test plan
google_tag_manager_advanced_trackingen una base 18.0.aparece GA4 API Secret (Server-side) con su input.
website.ga4_api_secret.Task: https://www.adhoc.inc/odoo/project.task/66923
Forward-Port-Of: #481