Managed proxy

Route MetricRaven through a subdomain of your website without running any proxy code. You add one DNS record; MetricRaven serves the script and receives events there, with its own TLS certificate.

Why use a proxy?

Ad blockers often block known analytics domains. A subdomain of your own website is blocked less often, so you see more of your visits and more of your revenue attribution. You don't need a proxy to start; add one before a launch or when you want more complete data.

Without a proxy, the script and its events go to metricraven.com. With the managed proxy they go to your subdomain instead, for example a.example.com/js/script.js and a.example.com/api/v1/collect.

Set it up

1. Enable the managed proxy

   • Open Settings → Tracking & install → Managed proxy on your website's dashboard.
   • Enter a subdomain of your website, such as a.example.com, and select Enable.

   Pick a short, neutral name such as a or cdn. Blocklists often target names like analytics, tracking, stats or metrics. Use a subdomain, not your main site's hostname. Admins and the owner can set it up; each website has one managed proxy.

2. Add the DNS record

   The dashboard shows the exact record. For a subdomain it's one CNAME:

   DNS field	Value
   Type	CNAME
   Name / Host	a
   Target / Value	proxy.metricraven.com
   TTL	Auto (or 300 seconds)
   Proxy status	DNS only, proxy off (Cloudflare: grey cloud)

   The dashboard looks up where your domain's DNS is hosted and, for the providers below, shows that provider's steps, its own field names, a link to its DNS page and a copy button for each field.

   a is only an example: for cdn.example.com the name is cdn. If the dashboard also shows a TXT record, add it only when the status stays on Waiting for DNS for more than 10 minutes. You can delete the TXT record once the proxy is active.

   DNS changes usually show up within 1–10 minutes. MetricRaven checks automatically (every minute at first) and issues the certificate as soon as the record is in place. Select Check again to look right away.

3. Update your script tag

   When the status is Active, replace your MetricRaven tag with this one. The Install card in Settings shows it with your site ID filled in.

   Your website's shared layout

   Copy

   1

   <script defer src="https://a.example.com/js/script.js" data-site-id="YOUR_SITE_ID"></script>

   The tracker sends its events to the host it was loaded from, so there's no separate events URL to set. If your tag has a data-api attribute from a self-hosted proxy, remove it.

Steps by DNS provider

Add the record where your domain's DNS is hosted, which isn't always where you bought the domain. The dashboard detects it from your domain's nameservers. Field names differ by provider:

Any other provider works the same way: add a CNAME with the name and target from the dashboard, keep the default TTL, and keep any proxy, CDN, forwarding or redirect option off for this record.

Why it matters: the record has to point straight at proxy.metricraven.com. The certificate for your subdomain is issued only once the name resolves there, and that's how requests to your subdomain reach MetricRaven.

Statuses

If no record appears within 7 days, MetricRaven stops checking and the status becomes Needs attention. Add the record and select Check again to start over. Active proxies are rechecked every few hours.

Troubleshooting

Remove the managed proxy

First point your script tag back at https://metricraven.com/js/script.js. Then, in Settings → Tracking & install → Managed proxy, select Remove; the subdomain stops serving the script at once. Finally delete the DNS record.

API, CLI and MCP

With an account token and ?site= (changes need the write scope and an admin or the owner):

CLI: metricraven proxy status, proxy enable a.example.com, proxy check and proxy remove. MCP: get_managed_proxy.

Managed or self-hosted?

For self-hosted setups, see the proxy recipes.