{"_id":"59e70b9ee027ae002e7d2ee5","category":{"_id":"59e70b9ee027ae002e7d2ed8","version":"59e70b9ee027ae002e7d2ed2","project":"5496d393f52a630b00519cdd","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-12-26T11:41:35.509Z","from_sync":false,"order":5,"slug":"batch","title":"Batch"},"parentDoc":null,"user":"5496d353f52a630b00519cdc","project":"5496d393f52a630b00519cdd","version":{"_id":"59e70b9ee027ae002e7d2ed2","project":"5496d393f52a630b00519cdd","__v":2,"createdAt":"2017-10-18T08:06:54.462Z","releaseDate":"2017-10-18T08:06:54.462Z","categories":["59e70b9ee027ae002e7d2ed3","59e70b9ee027ae002e7d2ed4","59e70b9ee027ae002e7d2ed5","59e70b9ee027ae002e7d2ed6","59e70b9ee027ae002e7d2ed7","59e70b9ee027ae002e7d2ed8","59e70b9ee027ae002e7d2ed9","59e70b9ee027ae002e7d2eda","59e70b9ee027ae002e7d2edb","59e70b9ee027ae002e7d2edc","59e70b9ee027ae002e7d2edd","59e70b9ee027ae002e7d2ede","59e70b9ee027ae002e7d2edf","5b8661ccdd19310003a3fa0b"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"2.0.10","version":"2.0.10"},"githubsync":"","__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-08-24T07:05:32.359Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"The Check-in-stream export is used to fetch and load user timeline data to your systems on a large scale.\nThe Check-in-stream bucket export generates a JSON line file every hour. Each line can be either a user [visit](visit) or [transit](transit). Data is provided in a [Check-in Export structure](doc:check-in-export)  which includes the User ID.\n\nFiles will be stored under your [export bucket](doc:data-export) in the 'check-in-stream' folder. File names are a UTC timestamp of export end time.\n\n**For example:**\nVisits and transits of between 19:00 to 20:00 of June 1st 2016 will be stored at the following path:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"gs://<CLIENT_NAME>/results/<APP_KEY>/2016-06-01/stream/20160601-2000.gz\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Notes\",\n  \"body\": \"- Only visits and transits that have ended will be exported ('on-going' visits will be exported only when they are closed).\\n- The export rate default configuration is set to file per hour which may be reduced during peak hours.\\n- If a file reaches 5,000,000 lines it will be closed regardless of the default export rate configuration. File name will be the export end time.\\n- In case the system is down for maintenance, export files will be delayed up to 24 hours and their filenames will be changed accordingly.\"\n}\n[/block]","excerpt":"","slug":"check-in-stream-export","type":"basic","title":"Check-in-stream - export"}

Check-in-stream - export


The Check-in-stream export is used to fetch and load user timeline data to your systems on a large scale. The Check-in-stream bucket export generates a JSON line file every hour. Each line can be either a user [visit](visit) or [transit](transit). Data is provided in a [Check-in Export structure](doc:check-in-export) which includes the User ID. Files will be stored under your [export bucket](doc:data-export) in the 'check-in-stream' folder. File names are a UTC timestamp of export end time. **For example:** Visits and transits of between 19:00 to 20:00 of June 1st 2016 will be stored at the following path: [block:code] { "codes": [ { "code": "gs://<CLIENT_NAME>/results/<APP_KEY>/2016-06-01/stream/20160601-2000.gz", "language": "shell" } ] } [/block] [block:callout] { "type": "info", "title": "Notes", "body": "- Only visits and transits that have ended will be exported ('on-going' visits will be exported only when they are closed).\n- The export rate default configuration is set to file per hour which may be reduced during peak hours.\n- If a file reaches 5,000,000 lines it will be closed regardless of the default export rate configuration. File name will be the export end time.\n- In case the system is down for maintenance, export files will be delayed up to 24 hours and their filenames will be changed accordingly." } [/block]