<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-XXXXXX');</script>
<!-- End Google Tag Manager -->
<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-XXXXXX"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
[null,null,["最后更新时间 (UTC)：2024-04-17。"],[[["\u003cp\u003eGoogle Tag Manager container tag uses HTTPS by default for enhanced security.\u003c/p\u003e\n"],["\u003cp\u003eYou can switch to a protocol-relative URL (//) for flexible loading based on the page's protocol (HTTP or HTTPS).\u003c/p\u003e\n"],["\u003cp\u003eExisting protocol-relative implementations of Tag Manager containers will continue to function.\u003c/p\u003e\n"],["\u003cp\u003eEnsure custom tags on secure pages are set up with protocol-relative or secure URLs for consistent security.\u003c/p\u003e\n"]]],["Google Tag Manager uses HTTPS to load resources for security. Users can opt for protocol-relative loading by changing the container code's protocol to `//` instead of `https://`. This method ensures the container loads via HTTP or HTTPS depending on the page's protocol. Older container codes used protocol-relative URLs and remain functional. Custom tags firing on secure pages should also be protocol-relative or secure. The example codes are provided to implement this.\n"],null,["# Configure Tag Manager to use protocol-relative URLs\n\nTo help secure tag data, the Google Tag Manager container tag uses HTTPS to\nload resources (i.e. `https://www.googletagmanager.com`).\n\nIf you need to load your Tag Manager containers in a protocol-relative manner,\nyou may do so by adjusting the protocol in your container code to be `//`\ninstead of `https://`. \n\n \u003c!-- Google Tag Manager --\u003e\n \u003cscript\u003e(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':\n new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],\n j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=\n '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);\n })(window,document,'script','dataLayer','GTM-XXXXXX');\u003c/script\u003e\n \u003c!-- End Google Tag Manager --\u003e\n \u003c!-- Google Tag Manager (noscript) --\u003e\n \u003cnoscript\u003e\u003ciframe src=\"//www.googletagmanager.com/ns.html?id=GTM-XXXXXX\"\n height=\"0\" width=\"0\" style=\"display:none;visibility:hidden\"\u003e\u003c/iframe\u003e\u003c/noscript\u003e\n \u003c!-- End Google Tag Manager (noscript) --\u003e\n\nWhen you use a protocol-relative URL, the container is loaded via HTTP on pages\nthat use `http://`, and via HTTPS on pages that use `https://`.\n\nOlder versions of the Tag Manager container code used a\nprotocol-relative URL to load containers (i.e., `//www.googletagmanager.com`).\nThese older protocol-relative versions of the Tag Manager container\ncode will continue to work.\n| **Note:** While most of the tag templates in Tag Manager are also protocol relative, it's important to make sure that when you set up custom tags to fire on secure pages, those tags are also configured to be either protocol-relative or secure."]]