Merge branch 'master' into DOC-162_rate-limits

Author: markzegarelli

src/_layouts/default.html

@@ -83,7 +83,7 @@
     Production: https://app.segment.com/segment_prod/sources/segment_docs_v2_prod
     Everything else: https://app.segment.com/segment-engineering/sources/segment_docs
   {%- endcomment -%}
-  {%- if jekyll.environment == "production" -%}
+  {%- if site.env.CONTEXT == "production" -%}
     {%- assign write_key = "QAKKJEtNsXpsNfCCBeWCLNxkaaLO7pgp" -%}
   {%- else -%}
     {%- assign write_key = "f5c1iWVVwikUDoh5NuVq0G52EPFrMmrX" -%}
@@ -118,7 +118,6 @@
   {%- comment -%}
     Consent Manager
   {%- endcomment -%}
-
 <script>
   window.consentManagerConfig = function (exports) {
     var React = exports.React

src/connections/destinations/catalog/google-analytics/index.md

@@ -621,8 +621,16 @@ If you want to send UTM parameters to Google Analytics using one of the Segment
 
 Your UTM params need to be passed in the `context` object in `context.campaign`. For Google Analytics `campaign.name`, `campaign.source` and `campaign.medium` all need to be sent together for things to show up in reports. The other two params (`campaign.term` and `campaign.content`) are both optional, but will be forwarded to GA if you send them to Segment.
 
+### Measurement Protocol Parameters
 
----
+Google Analytics uses a reserved set of [Measurement Protocol Parameters](https://developers.google.com/analytics/devguides/collection/protocol/v1/parameters) which are automatically collected by the device-mode Google Analytics tracker. 
+
+To include Measurement Protocol Parameters when sending server-side events to Google Analytics:
+
+1. Collect the value of the parameter as a Segment trait or property
+2. Configure the Segment Google Analytics destination to [map the trait or property](#map-traits-or-properties-to-measurement-protocol-params) to a specific Measurement Protocol Parameter key
+
+Segment supports the `plt`, `pdt`, `gclid`, `dt`, and `cid` Measurement Protocol Parameters.
 
 
 ## Features