Skip click rewriting and the open-tracking pixel on HTTP send with trackLinks and trackOpens.
On HTTP send (POST /transactional-email), Routee instruments HTML by default:
- Click tracking rewrites HTML anchor
hrefs so Routee can record clicks. - Open tracking injects a tracking pixel so Routee can record opens.
Use these optional booleans to skip that instrumentation. Both default to true.
Request fields
| Path | Type | Description |
|---|---|---|
trackLinks | Boolean | When false, click tracking on HTML anchor hrefs is disabled. Default true. Optional. |
trackOpens | Boolean | When false, open tracking via the tracking pixel is disabled. Default true. Optional. |
Example
{
"from": { "address": "[email protected]" },
"to": [{ "address": "[email protected]" }],
"subject": "Order confirmed",
"content": { "html": "<p>Thanks. <a href=\"https://example.com/order\">View order</a></p>" },
"trackLinks": false,
"trackOpens": false
}What these flags do not control
callback.eventCallback (onOpen / onClick) is a webhook setting. It tells Routee where to POST if an open or click occurs. It does not turn instrumentation on or off.
| Goal | What to set |
|---|---|
| Leave original links; no click wrapping | "trackLinks": false |
| Do not inject an open pixel | "trackOpens": false |
| Receive open/click webhooks | callback.eventCallback.onOpen / onClick |
| Skip webhooks but still record opens/clicks in logs | Omit eventCallback; leave trackLinks / trackOpens at default true |
HTTP vs SMTP
These fields exist only on the HTTP JSON send body. SMTP relay has no equivalent MIME headers. Use the HTTP API when you need to skip link or open tracking.
Send reference: Send a transactional email