Tracking Preferences

Let recipients choose what you track

A hosted page where each recipient turns open and click tracking on or off without unsubscribing, in English, German, French, Italian and Spanish. Their choice is applied to every send, and you can read and sync it with the API.

  • Hosted page in 5 languages
  • No unsubscribe needed
  • Applied on every send
  • Consent history
  • Cursor sync
POSThttps://g.sendcorex.com/v1/privacyprivacy:read

How it works

A page you do not build

Campaigns with tracking add the link next to your unsubscribe link, in your style. In API and SMTP emails, put [tracking_preferences_url] where you want it. Every recipient gets their own link, the page uses your logo and colors, opens in the recipient's language, and is also linked from the unsubscribe page.

Refusal always wins

When a recipient turns tracking off, it stays off on every campaign and every email sent with "unsubscribe": true, even if the campaign or send asks for tracking. No pixel, no rewritten links.

Yours to sync

Read one recipient or 100 at once, poll every change with a cursor, get a webhook when a recipient changes it, and record consent you collected yourself.

Get started

Two steps and your recipients can manage their tracking.

  1. 1

    Add [tracking_preferences_url] to your emails

    Send with "unsubscribe": true and put [tracking_preferences_url] next to your unsubscribe link (aliases: [privacy_url], [preferences_url]). We replace it with the recipient's own link.

    Without "unsubscribe": true the placeholder is removed from the email and the API answers with a warning. Campaigns need nothing: the link is added for you when the campaign tracks opens or clicks.

  2. 2

    Create an API key with privacy:read

    In the dashboard, open Developers → API Keys and give a key privacy:read. Add privacy:write if you also record consent from your side.

  3. 3

    Keep your CRM in sync

    Subscribe to the tracking_preferences_updated webhook, and poll List Changes as the safety net.

The preference

Every command returns preferences in this shape.

{
  "email": "jane.doe@example.com",
  "track_opens": false,
  "track_clicks": true,
  "source": "page",
  "updated_at": "2026-10-24T07:20:12.031Z"
}
track_opens / track_clicks

true allowed, false refused, null never chose. false always wins on campaigns and on sends with "unsubscribe": true.

source

page when the recipient changed it, api when you did, dashboard when your team did.

updated_at

When the change was made. The full list of changes is in Get History.

Your first request

The preferences of two recipients before a send. Replace SENDCOREX_API_KEY with your API key.

curl -X POST 'https://g.sendcorex.com/v1/privacy' \
  -H "Authorization: $SENDCOREX_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "commands": [
    { "command": "get_many", "args": { "emails": ["jane.doe@example.com", "marc.dupont@example.fr"] } }
  ]
}'

Recipients missing from the answer never chose anything: your send decides for them. The same request in 8 languages is in Get Many.

Common tasks

Opt-in countries

Where tracking needs consent first, send with tracking off and turn it on only for recipients who allowed it.

Before sending

Sync with Salesforce

Write every change to the contact record with a cursor loop, and skip the changes you made yourself.

Sync with your CRM

Record consent from your forms

A recipient agreed in your signup form? Store it here so every send respects it.

Set Preferences

Prove consent in an audit

Show every change of one recipient: what they chose, when, and who changed it.

Get History

Full reference

Everything marked CMD is a command sent through POST /v1/privacy, up to 20 per request.