{"_id":"5909210b4d3299250089690b","__v":0,"project":"55de06fa57f7b20d0097636b","user":"55de06e19db51a0d0064947d","version":{"_id":"55de06fa57f7b20d0097636e","project":"55de06fa57f7b20d0097636b","__v":14,"createdAt":"2015-08-26T18:35:38.642Z","releaseDate":"2015-08-26T18:35:38.642Z","categories":["55de06fb57f7b20d0097636f","55f1962e3936d52d00fb3c8f","55f1970339e3e8190068b2b8","55f1970d229b772300779a1f","55f1971cfd98c42300acc605","55f1d5c7fd98c42300acc69f","563cbfe4260dde0d00c5e9d4","5644cf437f1fff210078e690","57dc1bbd3ed3450e00dc9ea7","58a600a2243dd30f00fd8773","58ed1bdc068f780f00f64602","58f13b3a4f0ee50f00e24e81","58f173f792f9020f009cad16","591b42f8e633fd0f00077c5a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"58f173f792f9020f009cad16","project":"55de06fa57f7b20d0097636b","version":"55de06fa57f7b20d0097636e","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-04-15T01:14:31.085Z","from_sync":false,"order":9,"slug":"firstparty-data-ingestion","title":"First Party Data Ingest API"},"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-05-03T00:15:07.883Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"## Overview\nPushSpring ingests 1st Party data in the form of Mobile Advertising IDs (either Apple IDFA or Google Play Ad Id).  In addition, if your platform has event data associated with the advertising id's and the user wishes to export it to the PushSpring platform, you can send that as well.\n\n## Simple Advertising ID-only format\nIf you are just sending lists of Advertising IDs, they can be sent in a simple one-column CSV format, with no header row, id's forced to lower case:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"38b0852c-9673-4230-9b58-e0a336a348fe\\n4175f9fa-83db-4da7-95d6-62d1f2296c56\\n689626da-ebe3-4e01-a505-e36b09acae33\\n7f9e25cd-119b-44f3-8351-5c95ce3f8009\\n80b7407f-abee-42c2-86c2-00b49241c214\\n8d553fa4-1173-4263-b9b2-4ed33b6a5d60\\n964cf285-ee6a-4161-a291-3dbeda009a37\\n00026568-4479-4768-8aa1-42af920fefe5\\n000857c8-da88-4fd3-b853-1d919f982ff0\\n000c1019-f6cf-49d8-acc7-83ff7b1883f2\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]\n## Sending event data\nIf your platform captures events that have been performed or associated with each Advertising ID, you can specify those in an optional second column.\n\nIn general, you may send any event name you would like the user to see in the PushSpring Console UI associated with the Advertising IDs, however we do have three \"special\" event names which are handled in the PushSpring platform.  These events are commonly associated with advertising campaigns:\n* impression\n* click\n* conversion\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"38b0852c-9673-4230-9b58-e0a336a348fe, impression\\n4175f9fa-83db-4da7-95d6-62d1f2296c56, impression\\n689626da-ebe3-4e01-a505-e36b09acae33, impression\\n7f9e25cd-119b-44f3-8351-5c95ce3f8009, impression\\n80b7407f-abee-42c2-86c2-00b49241c214, impression\\n8d553fa4-1173-4263-b9b2-4ed33b6a5d60, impression\\n964cf285-ee6a-4161-a291-3dbeda009a37, impression\\n00026568-4479-4768-8aa1-42af920fefe5, impression\\n000857c8-da88-4fd3-b853-1d919f982ff0, impression\\n689626da-ebe3-4e01-a505-e36b09acae33, click\\n000c1019-f6cf-49d8-acc7-83ff7b1883f2, impression\\n964cf285-ee6a-4161-a291-3dbeda009a37, click\\n689626da-ebe3-4e01-a505-e36b09acae33, conversion\",\n      \"language\": \"text\"\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"audience-file-format-for-ingest","type":"basic","title":"Audience File Format for Ingest"}

Audience File Format for Ingest


## Overview PushSpring ingests 1st Party data in the form of Mobile Advertising IDs (either Apple IDFA or Google Play Ad Id). In addition, if your platform has event data associated with the advertising id's and the user wishes to export it to the PushSpring platform, you can send that as well. ## Simple Advertising ID-only format If you are just sending lists of Advertising IDs, they can be sent in a simple one-column CSV format, with no header row, id's forced to lower case: [block:code] { "codes": [ { "code": "38b0852c-9673-4230-9b58-e0a336a348fe\n4175f9fa-83db-4da7-95d6-62d1f2296c56\n689626da-ebe3-4e01-a505-e36b09acae33\n7f9e25cd-119b-44f3-8351-5c95ce3f8009\n80b7407f-abee-42c2-86c2-00b49241c214\n8d553fa4-1173-4263-b9b2-4ed33b6a5d60\n964cf285-ee6a-4161-a291-3dbeda009a37\n00026568-4479-4768-8aa1-42af920fefe5\n000857c8-da88-4fd3-b853-1d919f982ff0\n000c1019-f6cf-49d8-acc7-83ff7b1883f2", "language": "text" } ] } [/block] ## Sending event data If your platform captures events that have been performed or associated with each Advertising ID, you can specify those in an optional second column. In general, you may send any event name you would like the user to see in the PushSpring Console UI associated with the Advertising IDs, however we do have three "special" event names which are handled in the PushSpring platform. These events are commonly associated with advertising campaigns: * impression * click * conversion [block:code] { "codes": [ { "code": "38b0852c-9673-4230-9b58-e0a336a348fe, impression\n4175f9fa-83db-4da7-95d6-62d1f2296c56, impression\n689626da-ebe3-4e01-a505-e36b09acae33, impression\n7f9e25cd-119b-44f3-8351-5c95ce3f8009, impression\n80b7407f-abee-42c2-86c2-00b49241c214, impression\n8d553fa4-1173-4263-b9b2-4ed33b6a5d60, impression\n964cf285-ee6a-4161-a291-3dbeda009a37, impression\n00026568-4479-4768-8aa1-42af920fefe5, impression\n000857c8-da88-4fd3-b853-1d919f982ff0, impression\n689626da-ebe3-4e01-a505-e36b09acae33, click\n000c1019-f6cf-49d8-acc7-83ff7b1883f2, impression\n964cf285-ee6a-4161-a291-3dbeda009a37, click\n689626da-ebe3-4e01-a505-e36b09acae33, conversion", "language": "text" } ] } [/block]