Skip to content

Commit 78700e8

Browse files
Update src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md
1 parent 29dce6c commit 78700e8

File tree

1 file changed

+2
-2
lines changed
  • src/connections/sources/catalog/libraries/website/javascript

1 file changed

+2
-2
lines changed

src/connections/sources/catalog/libraries/website/javascript/custom-proxy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ You need to set up two important parts, regardless of the CDN provider you use:
3838
> info ""
3939
> Segment only has the ability to enable the proxy setting for the Web (Analytics.js) source. Details for mobile source proxies are in the [Analytics-iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#proxy-https-calls) and [Analytics-Android](/docs/connections/sources/catalog/libraries/mobile/android/#proxying-http-calls) documentation. It is not currently possible to set up a proxy for server sources using the Segment UI.
4040
41-
>info ""
42-
> Any of Segment's integrations will be loaded via the proxy, however, we don't host 3rd party SDKs (with a few rare exceptions), so Fullstory's SDK for example would still be loaded by their own CDN.
41+
> info "Segment loads most integrations through the proxy, except for third-party SDKs"
42+
> Third-party SDKs are loaded by a partner's CDN, even with a Segment proxy configured. For example, if you have a Segment custom proxy enabled and send data to a FullStory destination, FullStory's CDN would load the FullStory SDK.
4343
4444
## Custom Proxy setup
4545

0 commit comments

Comments
 (0)