[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2024-02-06 UTC。"],[[["\u003cp\u003eThis article guides developers on hosting server-side tagging in a first-party context for enhanced security and cookie durability.\u003c/p\u003e\n"],["\u003cp\u003eAchieving same-origin serving involves configuring your tagging server and website to run on the same domain, which can be done using a subdomain or by forwarding requests to a specific path on your main domain.\u003c/p\u003e\n"],["\u003cp\u003eServer-side tagging hosted on the default domain lacks access to crucial server-set cookie benefits, unlike same-origin setups.\u003c/p\u003e\n"],["\u003cp\u003eSetting up same-origin serving requires updating DNS entries or configuring a CDN/load balancer, depending on the chosen method.\u003c/p\u003e\n"],["\u003cp\u003eBefore implementing same-origin serving, ensure you've established a server container in Tag Manager and set up a tagging server.\u003c/p\u003e\n"]]],["To leverage server-set cookie benefits, host your tagging server in the same first-party context as your website. Options include using the same origin (e.g., `www.example.com/metrics`) or a subdomain (e.g., `metrics.example.com`). Both allow full cookie access, unlike the default provider-hosted domain. Implementing same-origin requires a CDN/load balancer and potential DNS updates, while subdomains only need DNS adjustments. Pre-setup of a server container and tagging server is required.\n"],null,[]]