Skip to main content
PATCH
Configure Domain Tracking
Move tracked links and opens for a domain added before per-domain tracking (website.tracking.policy is legacy) to a subdomain of that domain, such as links.mail.example.com. Publish the returned website.tracking.cnameRecord. Links keep using their current tracking domain until the new subdomain verifies, and sending is never paused while it does. Once the subdomain verifies, the domain switches to per-domain tracking like newly added domains: tracking.policy becomes required, and links no longer fall back to the company tracking domain. A tracking subdomain cannot be changed once set. Sending the same value again changes nothing; a different value returns 400. Domains with tracking.policy: "required" chose their tracking subdomain when they were added, so any other value returns 400. This endpoint requires the websites:write scope.

Request

string
required
Configured sending domain.
string
required
Tracking subdomain label, for example links. Use one DNS label of 1 to 63 letters, numbers or hyphens, without a leading or trailing hyphen. It cannot be inbound or the label that holds the domain’s bounce records.
An invalid label returns 400. A missing or non-string trackingPrefix returns 422. An unexpected server error returns 500; retrying with the same value is safe.

Responses