Merge pull request #4243 from segmentio/prigiattiperrut-patch-2

stayseesong · web-flow · commit 9e97af2a52a7 · 2023-03-01T15:07:15.000-08:00
Update custom-proxy.md
diff --git a/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md b/src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md
@@ -30,7 +30,11 @@ You need to set up two important parts, regardless of the CDN provider you use:
 
 ## Set up
 
-Follow the directions listed for CloudFront or use your own CDN setup. Once you complete those steps and verify that your proxy works for both `cdn.segment.com` and `api.segment.io`, [contact Segment Product Support](https://segment.com/help/contact/) with the following template email:
+There are 2 options you can choose from when you set up your custom domain proxy.
+1. [CloudFront](#cloudfront)
+2. [Custom CDN or API proxy](#custom-cdn--api-proxy)
+
+Follow the directions listed for [CloudFront](#cloudfront) or [use your own CDN setup](#custom-cdn--api-proxy). Once you complete those steps and verify that your proxy works for both `cdn.segment.com` and `api.segment.io`, [contact Segment Product Support](https://segment.com/help/contact/) with the following template email:
 
 ```text
 Hi,
@@ -51,6 +55,58 @@ A Segment Customer Success team member will respond that they have enabled this
 > info ""
 > The **Host Address** field does not appear in source settings until it's enabled by Segment Customer Success.
 
+
+## Custom CDN / API Proxy
+
+### Snippet instructions
+If you're a snippet user, you need to modify the [analytics snippet](/docs/getting-started/02-simple-install/#step-1-copy-the-snippet) that's inside your `<head>`. 
+
+To proxy settings and destination requests that typically go to `http://cdn.segment.com`, replace: 
+```diff
+- t.src="https://cdn.segment.com/analytics.js/v1/" + key + "/analytics.min.js"
++ t.src="https://MY-CUSTOM-CDN-PROXY.com" + key + "/analytics.min.js"
+```
+
+To proxy tracking calls that typically go to `api.segment.io/v1`, replace:
+```diff
+- analytics.load("<MY_WRITE_KEY>")
++ analytics.load("<MY_WRITE_KEY>", { integrations: { "Segment.io": { apiHost:  "MY-CUSTOM-API-PROXY.com" }}})
+```
+
+### npm instructions
+See the [`npm` library-users instructions](https://www.npmjs.com/package/@segment/analytics-next){:target="_blank"} for more information.
+
+Proxy settings and destination requests that typically go to `http://cdn.segment.com` through a custom proxy.
+
+```ts
+const analytics = AnalyticsBrowser.load({
+  writeKey,
+  // GET http://cdn.segment.com/v1/projects/<writekey>/settings ->
+  // https://MY-CUSTOM-CDN-PROXY.com/v1/project/<writekey>/settings
+  // GET https://cdn.segment.com/next-integrations/actions/...js ->
+  // https://MY-CUSTOM-CDN-PROXY.com/next-integrations/actions/...js
+  cdnURL: 'https://MY-CUSTOM-CDN-PROXY.com' 
+ })
+```
+
+Proxy tracking calls that typically go to `api.segment.io/v1` by configuring `integrations['Segment.io'].apiHost`.
+```ts
+const analytics = AnalyticsBrowser.load(
+    {
+      writeKey,
+      cdnURL: 'https://MY-CUSTOM-CDN-PROXY.com'
+    },
+    {
+      integrations: {
+        'Segment.io': {
+          // POST https://api.segment.io/v1/t -> https://MY-CUSTOM-API-PROXY.com/t
+          apiHost: 'MY-CUSTOM-API-PROXY.com' // omit the protocol (http/https) e.g. "api.segment.io/v1" rather than "https://api.segment.io/v1" 
+        }
+      }
+    }
+  )
+```
+
 ## CloudFront
 
 These instructions refer to Amazon CloudFront, but apply more generally to other providers as well.
