Configurare la modalità di consenso per le pagine AMP
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Le opzioni di personalizzazione per i parametri della modalità di consenso nei tag di analisi AMP sono limitate. AMP offre una gestione del consenso integrata, ad esempio il ritardo dei tag di analisi fino al momento in cui viene fornito il consenso, come descritto in Mostrare messaggi relativi ai regolamenti europei nelle pagine AMP e amp-consent.
Impostazioni della gestione del consenso per le pagine AMP
Puoi configurare le seguenti impostazioni di gestione del consenso:
Specificare i servizi Google che possono ricevere i dati per i quali è stato dato il consenso
Per impostazione predefinita, il consenso per l'invio dei dati utente a Google per scopi pubblicitari
è considerato concesso per tutti i servizi Google. Puoi ignorare questa impostazione
specificando i servizi Google che possono ricevere dati etichettati con il consenso.
Utilizzando il tag amp-analytics
standard, fornendo l'elenco dma_cps
:
"vars": {
"clientId": "CLIENT_ID(custom_cookie)",
"gtag_id": "UA-1234-5",
"dma_cps": "ads,maps,playstore,search,shopping,youtube",
"config": {
"AW-2222": {...},
"G-12345678": {...}
}
}
Utilizzo di Google Tag Manager:
<!-- Google Tag Manager -->
<amp-analytics
config="https://www.googletagmanager.com/amp.json?id=GTM-WC8J58F>m.url=SOURCE_URL&dma_cps=ads%2Cmaps%2Cplaystore%2Csearch%2Cshopping%2Cyoutube"
data-credentials="include"></amp-analytics>
Utilizzare il tag amp-analytics
Per impostazione predefinita, il consenso ad_personalization
viene negato agli utenti che risiedono nello Spazio economico europeo (SEE). Puoi sostituire la personalizzazione degli annunci utilizzando il tagamp-analytics
:
<script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>
<amp-analytics type="gtag" data-credentials="include">
<script type="application/json">
{
"vars" : {
"gtag_id": "<DESTINATION_ID>",
"config" : {
"<DESTINATION_ID>": {
"groups": "default",
"allow_ad_personalization_signals": [true|false]
}
}
}
}
</script>
</amp-analytics>
Salvo quando diversamente specificato, i contenuti di questa pagina sono concessi in base alla licenza Creative Commons Attribution 4.0, mentre gli esempi di codice sono concessi in base alla licenza Apache 2.0. Per ulteriori dettagli, consulta le norme del sito di Google Developers. Java è un marchio registrato di Oracle e/o delle sue consociate.
Ultimo aggiornamento 2024-11-09 UTC.
[null,null,["Ultimo aggiornamento 2024-11-09 UTC."],[[["\u003cp\u003eAMP analytics tags have limited customization for consent mode parameters, relying on built-in AMP consent management.\u003c/p\u003e\n"],["\u003cp\u003eYou can specify which Google services (like ads, maps, or youtube) receive consented user data using the \u003ccode\u003edma_cps\u003c/code\u003e list within your \u003ccode\u003eamp-analytics\u003c/code\u003e tag or Google Tag Manager configuration.\u003c/p\u003e\n"],["\u003cp\u003eBy default, ad personalization is denied for EEA users, but you can override this within your \u003ccode\u003eamp-analytics\u003c/code\u003e tag using \u003ccode\u003eallow_ad_personalization_signals\u003c/code\u003e.\u003c/p\u003e\n"]]],["AMP provides limited consent mode parameter customization for analytics tags. Consent management settings allow specifying which Google services receive consented data, overriding the default. This is achieved using the `dma_cps` list in the `amp-analytics` tag or via Google Tag Manager. `ad_personalization` consent is denied by default for EEA users, but this can be overridden within the `amp-analytics` tag using the `allow_ad_personalization_signals` parameter. Built in consent management, delays analytics tags until consent is provided.\n"],null,["# Set up consent mode for AMP pages\n\nThe customization options for consent mode parameters in AMP analytics tags are\nlimited. AMP offers built-in consent management, like delaying analytics tags\nuntil consent is given, as detailed in\n[Displaying European regulations messages on AMP pages](https://support.google.com/admanager/answer/11136005) and [amp-consent](https://amp.dev/documentation/components/amp-consent).\n\nConsent management settings for AMP pages\n-----------------------------------------\n\nYou can configure the following consent management settings:\n\n### Specify which Google services can receive consented data\n\nBy default, consent for sending user data to Google for advertising purposes\nis considered granted for all Google services. You can override this by\nspecifying which Google services can receive data labeled with consent.\n\n- Using the standard `amp-analytics` tag, by providing the `dma_cps` list:\n\n \"vars\": {\n \"clientId\": \"CLIENT_ID(custom_cookie)\",\n \"gtag_id\": \"UA-1234-5\",\n \"dma_cps\": \"ads,maps,playstore,search,shopping,youtube\",\n \"config\": {\n \"AW-2222\": {...},\n \"G-12345678\": {...}\n }\n }\n\n- Using Google Tag Manager:\n\n \u003c!-- Google Tag Manager --\u003e\n \u003camp-analytics\n config=\"https://www.googletagmanager.com/amp.json?id=GTM-WC8J58F>m.url=SOURCE_URL&dma_cps=ads%2Cmaps%2Cplaystore%2Csearch%2Cshopping%2Cyoutube\"\n data-credentials=\"include\"\u003e\u003c/amp-analytics\u003e\n\n### Use your `amp-analytics` tag\n\nBy default, `ad_personalization` consent is denied for users based in the\nEuropean Economic Area (EEA). You can override ad personalization using your\n`amp-analytics` tag: \n\n \u003cscript async custom-element=\"amp-analytics\" src=\"https://cdn.ampproject.org/v0/amp-analytics-0.1.js\"\u003e\u003c/script\u003e\n \u003camp-analytics type=\"gtag\" data-credentials=\"include\"\u003e\n \u003cscript type=\"application/json\"\u003e\n {\n \"vars\" : {\n \"gtag_id\": \"\u003cDESTINATION_ID\u003e\",\n \"config\" : {\n \"\u003cDESTINATION_ID\u003e\": {\n \"groups\": \"default\",\n \"allow_ad_personalization_signals\": [true|false]\n }\n }\n }\n }\n \u003c/script\u003e\n \u003c/amp-analytics\u003e"]]