{"__v":4,"_id":"56f4331d54c3ff2000533fff","category":{"project":"568af724176a6c0d00a29ec4","version":"568af725176a6c0d00a29ec7","_id":"56f424307ea0091700f63ac5","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-03-24T17:30:24.236Z","from_sync":false,"order":4,"slug":"advanced-revenue-tracking","title":"Advanced Revenue Tracking"},"parentDoc":null,"project":"568af724176a6c0d00a29ec4","user":"568af6d197d8960d0012ab7d","version":{"__v":9,"_id":"568af725176a6c0d00a29ec7","project":"568af724176a6c0d00a29ec4","createdAt":"2016-01-04T22:50:13.289Z","releaseDate":"2016-01-04T22:50:13.289Z","categories":["568af725176a6c0d00a29ec8","56d9d397337fd11300d6a3e3","56d9d4287222d50b0070160b","56f424307ea0091700f63ac5","56f45babcb0dce29005a8e85","5739e5836c5ba134007a197d","57717aee3dd24019004c9122","5771b5d8c755ca0e00617d7d","579639964913990e001a5911"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"createdAt":"2016-03-24T18:34:05.021Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"ADVANCED REVENUE TRACKING\"\n}\n[/block]\n\nVigLink provides two means of tracking revenue individually for each of your users: [CUID](https://viglink-merchant-api.readme.io/docs/cuid-revenue-tracking) or SubID.\n[block:parameters]\n{\n  \"data\": {\n    \"h-1\": \"CUID\",\n    \"h-2\": \"SUBID\",\n    \"0-0\": \"Integration\",\n    \"1-0\": \"Account Ownership\",\n    \"2-0\": \"Reporting\",\n    \"3-0\": \"Payment\",\n    \"0-1\": \"Lightweight, self-serve setup via the JavaScript bootstrap, the HTTP API or the redirect service.\",\n    \"1-1\": \"Payments and data remain associated with the original VigLink account.\",\n    \"2-1\": \"Revenue reports only, provided via HTTP API. Any reporting to end users is handled outside of VigLink, by the account owner.\",\n    \"3-1\": \"The VigLink account owner handles payment to their end users.\",\n    \"0-2\": \"VigLink approval is required. Complexity varies, depending on payment needs.\",\n    \"1-2\": \"End users may claim their account, which then behaves like any other full-blown VigLink account.\",\n    \"2-2\": \"Full analytics via user-specific VigLink dashboards. Users can see their dashboard once the account is claimed.\",\n    \"3-2\": \"VigLink directly pays users who’ve claimed their account.\"\n  },\n  \"cols\": 3,\n  \"rows\": 4\n}\n[/block]","excerpt":"VigLink offers a couple different options for advanced revenue tracking.","slug":"overview","type":"basic","title":"Overview"}

Overview

VigLink offers a couple different options for advanced revenue tracking.

[block:api-header] { "type": "basic", "title": "ADVANCED REVENUE TRACKING" } [/block] VigLink provides two means of tracking revenue individually for each of your users: [CUID](https://viglink-merchant-api.readme.io/docs/cuid-revenue-tracking) or SubID. [block:parameters] { "data": { "h-1": "CUID", "h-2": "SUBID", "0-0": "Integration", "1-0": "Account Ownership", "2-0": "Reporting", "3-0": "Payment", "0-1": "Lightweight, self-serve setup via the JavaScript bootstrap, the HTTP API or the redirect service.", "1-1": "Payments and data remain associated with the original VigLink account.", "2-1": "Revenue reports only, provided via HTTP API. Any reporting to end users is handled outside of VigLink, by the account owner.", "3-1": "The VigLink account owner handles payment to their end users.", "0-2": "VigLink approval is required. Complexity varies, depending on payment needs.", "1-2": "End users may claim their account, which then behaves like any other full-blown VigLink account.", "2-2": "Full analytics via user-specific VigLink dashboards. Users can see their dashboard once the account is claimed.", "3-2": "VigLink directly pays users who’ve claimed their account." }, "cols": 3, "rows": 4 } [/block]