Link trackingnew

Link tracking rewrites every URL in an outbound text — sent by a teammate, by the AI texting agent, by Astra during a call, or by your code through POST /messages — into a short link.ody.co/<code> link before it leaves (scheme-less in the text so it reads cleanly in a bubble; trackedLinks[].shortUrl and the link.clicked webhook carry the absolute https://link.ody.co/<code>). Tapping it 302s to the original URL with the workspace's UTM template appended, so the business's own website analytics attribute the visit to an Ody text. Human clicks are counted; previewers, scanners and prefetchers are filtered out so a click always means a person.

On by default (since 2026-11-07; PATCH { "enabled": false } opts a workspace out and that choice sticks). It is a workspace preference — the same three switches the app shows under Settings → Analytics — and this page is how you read or change them from code. Changes are immediate (the next text follows the new setting); texts already sent are unaffected either way and their short links keep working.

#The settings object

Template placeholders:

Every response also carries defaults.utmTemplate (what null resolves to), baseUrl (https://link.ody.co) and placeholders.

curl https://api.ody.co/v1/api/link-tracking \
  -H "Authorization: Bearer $ODY_API_KEY"

const lt = await ody.linkTracking.get();
console.log(lt.settings.enabled, lt.settings.utmTemplate ?? lt.defaults.utmTemplate);

lt = client.link_tracking.get()
print(lt["settings"]["enabled"], lt["settings"]["utmTemplate"] or lt["defaults"]["utmTemplate"])

{
  "settings": { "enabled": true, "showInThread": true, "utmTemplate": null },
  "defaults": { "utmTemplate": "utm_source=ody&utm_medium=sms&utm_campaign={source}&utm_content=c_{contactRef}" },
  "baseUrl": "https://link.ody.co",
  "placeholders": ["source", "contactRef", "workspaceRef", "line", "code"]
}

curl -X PATCH https://api.ody.co/v1/api/link-tracking \
  -H "Authorization: Bearer $ODY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "enabled": false }'

await ody.linkTracking.update({ enabled: false });    // opt the workspace out
await ody.linkTracking.update({ enabled: true });     // back on
await ody.linkTracking.update({ utmTemplate: "utm_source=ody&utm_medium=sms&utm_campaign=spring_{source}" });
await ody.linkTracking.update({ showInThread: false });   // keep counting, hide the thread line
await ody.linkTracking.update({ utmTemplate: null });     // back to the default

client.link_tracking.update(enabled=False)  # opt the workspace out
client.link_tracking.update(enabled=True)   # back on
client.link_tracking.update(utm_template="utm_source=ody&utm_medium=sms&utm_campaign=spring_{source}")
client.link_tracking.update(show_in_thread=False)
client.link_tracking.update(utm_template=None)  # back to the default

{
  "settings": { "enabled": false, "showInThread": true, "utmTemplate": null },
  "defaults": { "utmTemplate": "utm_source=ody&utm_medium=sms&utm_campaign={source}&utm_content=c_{contactRef}" },
  "baseUrl": "https://link.ody.co",
  "placeholders": ["source", "contactRef", "workspaceRef", "line", "code"]
}

#What is — and isn't — rewritten

• Outbound only. Links in texts your customers send are never changed.
• Explicit http(s)://… URLs and bare domains with a recognised TLD (farmdogs.com/book); up to 5 links per text. Email addresses are not links.
• Links to Ody itself (link.ody.co, api.ody.co) are left alone.
• Codes are 7 random base62 characters — never sequential, so a code can't be used to enumerate the pages a business sends.
• The redirect is always a 302 with Cache-Control: no-store and X-Robots-Tag: noindex; a cached or indexed redirect would hide clicks and leak destinations.
• Test keys (ody_test_…) rewrite links too, and the short links resolve — you can watch the whole loop without texting anyone.

#Privacy

The click record stores the time, the device class (mobile / desktop / other), the country when the edge supplies it, and a daily-salted hash of the IP — never the IP itself. The attribution parameters identify the contact only by {contactRef}; no phone number ever reaches the destination.

#MCP

The same two operations are MCP tools: get_link_tracking and configure_link_tracking, gated by the same workspace:manage scope.