Mobile Commons: How to allow MC to capture the UTM parameters for web-generated opt-ins, calls, etc?

Mobile Commons

Web-form generated calls, opt-ins, etc

How to allow MC to capture the UTM parameters for webgenerated opt-ins, calls, etc?

• When a POST request is made to MC, we pull the source information from an HTTP header called “referer”.
• There is another HTTP header that controls how much information is sent with the “referer” which is called “referrer-policy”.
• The “Referrer-policy” is an HTTP header that you can set the correct value for to allow passing the full source URL and path including the UTM parameters. There are multiple ways to set this header (on the server side, in the HTML code of the page, etc)
• When this header is not set by the sender/client side, the browsers use a default value for it which is “strict-origin-when-cross-origin”. This value/policy results in sending ONLY the origin/base URL (ie https://example.com) when making cross-origin requests (from one domain to another). Which is the case here.
• Based on the online references below, this header should be set to "unsafe-url".