{"_id":"5a3254fec049430012f55876","category":{"_id":"5bbc98ba817d5b00038e914a","project":"5587ff91b3bcf52b0051314f","version":"5a3254fdc049430012f5586d","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2018-10-09T12:02:02.151Z","from_sync":false,"order":1,"slug":"graph-and-methodology","title":"Graph and Methodology"},"project":"5587ff91b3bcf52b0051314f","user":"5587ff84b3bcf52b0051314e","parentDoc":null,"version":{"_id":"5a3254fdc049430012f5586d","project":"5587ff91b3bcf52b0051314f","__v":3,"createdAt":"2017-12-14T10:39:57.964Z","releaseDate":"2017-12-14T10:39:57.964Z","categories":["5a3254fdc049430012f5586e","5a3255199a6f2000125c0d61","5bbc98ba817d5b00038e914a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.6.0","version":"1.6"},"githubsync":"","__v":1,"updates":["5ba35ff22a8b8f0003d39e88"],"next":{"pages":[],"description":""},"createdAt":"2015-06-22T12:54:26.727Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"Result data is available in two types of mapping tables: horizontal and vertical. They contain the same data, but the structure is different. You can indicate which format you prefer.\n\nThe mapping tables use *Match IDs* (shown below in GUID format). These are IDs that tie together clusters of User IDs that belong to the same person. [Read more about MatchIDs here](doc:match-ids).\n\nOptionally, mapping table may also include *Household IDs*. These are clusters of User IDs that belong to the same household. For more on Household IDs and how they are implemented in the result data [please go here](doc:household-ids) \n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"As Screen6 processes your data on a daily basis, you can ask us to only send updates to the mapping table in comparison to yesterdays results.\",\n  \"title\": \"Incremental (daily) updates\"\n}\n[/block]\nThe default content format is \"horizontal\", and the file delivery format is Tab Separated GZip.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Match ID Graph Extract Format\"\n}\n[/block]\n  * Horizontal: Each line starts with a Match ID followed by its related User IDs. \n  * Vertical: Each line starts with a MatchID followed by one of its related User IDs \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"bc00966f-e5a6-410c-97aa-93dfab936a6a\\t34302050,93436308,15420117\\ne5b06fdc-0f2c-447b-9f36-801c48f25517\\t53410606,59794190\",\n      \"language\": \"text\",\n      \"name\": \"Horizonal MatchID mapping table\"\n    },\n    {\n      \"code\": \"bc00966f-e5a6-410c-97aa-93dfab936a6a\\t34302050\\nbc00966f-e5a6-410c-97aa-93dfab936a6a\\t93436308\\nbc00966f-e5a6-410c-97aa-93dfab936a6a\\t15420117\\ne5b06fdc-0f2c-447b-9f36-801c48f25517\\t53410606\\ne5b06fdc-0f2c-447b-9f36-801c48f25517\\t59794190\",\n      \"language\": \"text\",\n      \"name\": \"Vertical Match ID format example\"\n    }\n  ]\n}\n[/block]\nSeparation characters can be customized on request. User IDs may be separated by comma even if the file format uses tab separation. \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Filtering and Prefixing IDs\"\n}\n[/block]\nIf your source data contains multiple types of User IDs (for example: cookie and MAID) then you can ask us to include just one or all types of IDs in the result data.\n\nOptionally, IDs may be prefixed with their type. For example:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"bc00966f-e5a6-410c-97aa-93dfab936a6a\\tcookie:34302050,cookie:93436308,ifa:15420117\\ne5b06fdc-0f2c-447b-9f36-801c48f25517\\tcookie:53410606,ifa:59794190\",\n      \"language\": \"text\",\n      \"name\": \"Example of prefixed User IDs\"\n    }\n  ]\n}\n[/block]\nSimilarly, Device Type associated with the ID  - for example: PC, mobile phone, tablet, TV, etc. - can also be included as an ID prefix.\n[block:api-header]\n{\n  \"title\": \"Household Graph Extract Format\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Household graphs contain all matches at the Match ID level, in addition to matching shared devices (such as game consoles, televisions, etc) that were not attributed to a specific profile.\"\n}\n[/block]\nWe can send results in one combined graph with Match ID, or two separate graphs for Household and Match IDs. Options are the same for vertical or horizontal user identifiers, prefixes, etc. \n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"Household ID\\tMatch ID\\tUser IDs\\ne5b06fdc\\t\\t\\t0f2c-447b\\t34302050,93436308,15420117\\ne5b06fdc\\t\\t\\te5a6-410c\\t34599960,84838884,12223444\\ne5b06fdc\\t\\t\\t<blank>\\t\\t15420117\",\n      \"language\": \"text\",\n      \"name\": \"Household Combined Horizontal\"\n    },\n    {\n      \"code\": \"Household ID\\tUser IDs\\ne5b06fdc\\t\\t\\t34302050,93436308,15420117,34599960,84838884,12223444,15420117\",\n      \"language\": \"text\",\n      \"name\": \"Household ID Horizontal\"\n    }\n  ]\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Graph Expiry Configuration\"\n}\n[/block]\nOnce matched, Screen6 keeps Identifiers in your graph for as long as they are active, and for a configurable length of time after their last seen activity.\n\nThe default length is 60 days for persistent identifiers and 30 days for non-persistent types. Expired IDs can be delivered daily to help you maintain your graph.","excerpt":"","slug":"result-data","type":"basic","title":"Graph delivery format"}

Graph delivery format


Result data is available in two types of mapping tables: horizontal and vertical. They contain the same data, but the structure is different. You can indicate which format you prefer. The mapping tables use *Match IDs* (shown below in GUID format). These are IDs that tie together clusters of User IDs that belong to the same person. [Read more about MatchIDs here](doc:match-ids). Optionally, mapping table may also include *Household IDs*. These are clusters of User IDs that belong to the same household. For more on Household IDs and how they are implemented in the result data [please go here](doc:household-ids) [block:callout] { "type": "info", "body": "As Screen6 processes your data on a daily basis, you can ask us to only send updates to the mapping table in comparison to yesterdays results.", "title": "Incremental (daily) updates" } [/block] The default content format is "horizontal", and the file delivery format is Tab Separated GZip. [block:api-header] { "type": "basic", "title": "Match ID Graph Extract Format" } [/block] * Horizontal: Each line starts with a Match ID followed by its related User IDs. * Vertical: Each line starts with a MatchID followed by one of its related User IDs [block:code] { "codes": [ { "code": "bc00966f-e5a6-410c-97aa-93dfab936a6a\t34302050,93436308,15420117\ne5b06fdc-0f2c-447b-9f36-801c48f25517\t53410606,59794190", "language": "text", "name": "Horizonal MatchID mapping table" }, { "code": "bc00966f-e5a6-410c-97aa-93dfab936a6a\t34302050\nbc00966f-e5a6-410c-97aa-93dfab936a6a\t93436308\nbc00966f-e5a6-410c-97aa-93dfab936a6a\t15420117\ne5b06fdc-0f2c-447b-9f36-801c48f25517\t53410606\ne5b06fdc-0f2c-447b-9f36-801c48f25517\t59794190", "language": "text", "name": "Vertical Match ID format example" } ] } [/block] Separation characters can be customized on request. User IDs may be separated by comma even if the file format uses tab separation. [block:api-header] { "type": "basic", "title": "Filtering and Prefixing IDs" } [/block] If your source data contains multiple types of User IDs (for example: cookie and MAID) then you can ask us to include just one or all types of IDs in the result data. Optionally, IDs may be prefixed with their type. For example: [block:code] { "codes": [ { "code": "bc00966f-e5a6-410c-97aa-93dfab936a6a\tcookie:34302050,cookie:93436308,ifa:15420117\ne5b06fdc-0f2c-447b-9f36-801c48f25517\tcookie:53410606,ifa:59794190", "language": "text", "name": "Example of prefixed User IDs" } ] } [/block] Similarly, Device Type associated with the ID - for example: PC, mobile phone, tablet, TV, etc. - can also be included as an ID prefix. [block:api-header] { "title": "Household Graph Extract Format" } [/block] [block:callout] { "type": "info", "body": "Household graphs contain all matches at the Match ID level, in addition to matching shared devices (such as game consoles, televisions, etc) that were not attributed to a specific profile." } [/block] We can send results in one combined graph with Match ID, or two separate graphs for Household and Match IDs. Options are the same for vertical or horizontal user identifiers, prefixes, etc. [block:code] { "codes": [ { "code": "Household ID\tMatch ID\tUser IDs\ne5b06fdc\t\t\t0f2c-447b\t34302050,93436308,15420117\ne5b06fdc\t\t\te5a6-410c\t34599960,84838884,12223444\ne5b06fdc\t\t\t<blank>\t\t15420117", "language": "text", "name": "Household Combined Horizontal" }, { "code": "Household ID\tUser IDs\ne5b06fdc\t\t\t34302050,93436308,15420117,34599960,84838884,12223444,15420117", "language": "text", "name": "Household ID Horizontal" } ] } [/block] [block:api-header] { "type": "basic", "title": "Graph Expiry Configuration" } [/block] Once matched, Screen6 keeps Identifiers in your graph for as long as they are active, and for a configurable length of time after their last seen activity. The default length is 60 days for persistent identifiers and 30 days for non-persistent types. Expired IDs can be delivered daily to help you maintain your graph.