Core resources

Tracking Links

Issue the go.linkapprove.com redirect that turns a click into an attributed conversion.

Sub IDs and attribution

subId and subId2 are yours. We store them on the link and never interpret them. They are not sent to the network and are not attached to conversions; they exist so your click reporting can answer "which newsletter sent this traffic?" without guessing from link IDs.

  • Pick a scheme and keep it: 2026-08-newsletter, post-4471, sidebar-a.
  • Sub IDs are set at mint time and immutable afterwards. Mint a new link rather than rewriting one.
  • Group the performance report by subId to see clicks sliced your way rather than ours.
  • Do not put anything personal in a sub ID. It shows up in reports.

Sub IDs count clicks, not conversions

Sub IDs never reach the network, so conversions cannot be tied to them. A groupBy=subId row carries clicks only. conversions and conversionRate are null and earnings is empty.
Grouped by subId
{
  "success": true,
  "message": "Report fetched",
  "data": {
    "data": [
      {
        "subId": "spring-guide",
        "clicks": 2840,
        "conversions": null,
        "conversionRate": null,
        "earnings": []
      },
      {
        "subId": "post-4471",
        "clicks": 1102,
        "conversions": null,
        "conversionRate": null,
        "earnings": []
      },
      {
        "subId": "sidebar-a",
        "clicks": 238,
        "conversions": null,
        "conversionRate": null,
        "earnings": []
      }
    ],
    "count": 3,
    "pages": 1
  }
}