Access to platforms
Some platforms can't be accessed through connectors you build yourself. This is due to partnership agreements and legal restrictions with those vendors, not a technical limitation. Supermetrics already offers native connectors for all of them, so you can get the same data through the official integration instead.
The following platforms are restricted:
| Platform | Includes | What to use instead |
|---|---|---|
| Salesforce | Salesforce services, Pardot (Account Engagement), Marketing Cloud, and Commerce Cloud | The native Supermetrics Salesforce connectors |
| Amazon | Amazon services, Amazon Ads, and Amazon Selling Partner / Vendor services | The native Supermetrics Amazon connectors |
| X (Twitter) | X and Twitter services, including shortened t.co links |
The native Supermetrics X (Twitter) connector |
The restriction covers each platform's API domains and their regional variants, so alternative hostnames for the same service are blocked as well.
Note: Connector Builder shows an error when you save a configuration that calls a restricted domain.
Restricted HTTP headers
While you can define the custom headers your connector's requests need, a small set of headers is reserved for security reasons.
These headers are stripped from the request before it is sent. The request itself still goes through — only the reserved header is removed — so a connector that sets one keeps working, but the header never reaches the data source. Matching is case-insensitive: host, Host, and HOST are all treated the same.
The following headers are restricted:
| Category | Headers |
|---|---|
| Routing and forwarding | Host, Forwarded, X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto, X-Forwarded-Port, X-Real-IP, Via |
| Request framing | Transfer-Encoding, Content-Length |
| Connection and proxy control | Connection, Upgrade, Keep-Alive, TE, Trailer, Proxy-Authorization, Proxy-Connection |
Note: Connector Builder shows an error when you save a configuration that uses reserved headers.