{"_id":"5705662a794c940e00a9f2bc","parentDoc":null,"__v":4,"user":"5661cc12f183880d004d3193","version":{"_id":"5661bda7f5a87e0d00db3288","project":"5661bda6f5a87e0d00db3285","__v":9,"createdAt":"2015-12-04T16:21:59.490Z","releaseDate":"2015-12-04T16:21:59.490Z","categories":["5661bda8f5a87e0d00db3289","5661cd4bf183880d004d3195","5666281e3fcf5a0d000ef16b","56902d2e18c3920d00be8b5f","56afc7545b1f01170014dc31","56f9a06a4d2b4f3400edb648","5761c2fe207db7170022fc51","5925d868feb3f90f000a7595","5925db7af33cb40f007604fa"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"Learning the PushSpring UI","version_clean":"1.0.0","version":"1.0"},"githubsync":"","project":"5661bda6f5a87e0d00db3285","category":{"_id":"5925db7af33cb40f007604fa","project":"5661bda6f5a87e0d00db3285","version":"5661bda7f5a87e0d00db3288","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-05-24T19:14:02.619Z","from_sync":false,"order":2,"slug":"best-practices","title":"Best Practices"},"metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-04-06T19:40:26.192Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/bTykRnQ0qr0zXAvYaezw_PushSpring_white%20background.png\",\n        \"PushSpring_white background.png\",\n        \"184\",\n        \"35\",\n        \"#31a2ba\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nHave a question? Check out some of our most frequently asked questions below and reach out if there is something more we can answer for you. We are always around: hello:::at:::pushspring.com \n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"\"\n}\n[/block]\n**What types of targeting data does PushSpring offer?**\n\nPushSpring provides device-level targeting data for verified, non-fraudulent, iOS and Android mobile app audiences.  Use PushSpring data to target in-app users by IDFA and Android Advertising ID across Personas informed by device signals such as app ownership, location, and device settings. PushSpring audiences can also be used to target cross-device campaigns. \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**How does PushSpring collect data?**\n\nPushSpring audience data is collected from trusted, compliant sources, including PushSpring SDK implementations with mobile app publishers and strategic 3rd party partnerships.  PushSpring does not collect any personally identifiable information, only anonymous data tied to resettable device advertising identifiers.  PushSpring is a member of the [IAB](http://www.iab.net/) and the [DAA Self-Regulatory Program](http://www.aboutads.info/), and we take numerous steps to ensure that all data collection is performed in compliance with posted [Self-Regulatory Principals for Online Behavioral Advertising](http://www.aboutads.info/obaprinciples) and [Self-Regulatory Principles to the Mobile Environment.](http://www.aboutads.info/DAA_Mobile_Guidance.pdf)  \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**What IDs does PushSpring collect / use for targeting audiences?**\n\nPushSpring data is tied to anonymous, resettable, and opt-out enabled advertising IDs associated with user devices (IDFA for iOS and Android Advertising ID for Android) to create fully permissioned, aggregated and anonymous behavioral audience segments.  \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**From which mobile platforms does PushSpring collect data?**\n\nPushSpring currently offers targeting data for both iOS and Android app audiences. \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**How does PushSpring differ from other mobile data providers?**\n\n  * Device-Level Data – PushSpring provides deterministic device-level targeting data for iOS and Android mobile app audiences.  Target cross-device using Personas curated from IDFA and Android Advertising ID and created audiences informed by device signals such as app ownership, location, and device settings. \n\n  * App-Originated Audiences - PushSpring audience data is sourced from mobile apps.  Target users based on their true mobile app interests and behaviors, not by a probabilistic ID match to offline or browser-based interests.\n\n  * Fraud-Free Mobile Targeting  - All PushSpring data is processed to eliminate IDs associated with fraudulent traffic or app ownership patterns that are inconsistent with actual devices.  Remove fraud from mobile campaigns by layering the entire PushSpring audience data set in your targeting criteria. \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**Can I use PushSpring data to:** \n\n**Target mobile web and desktop browser audiences?**\n \nYes. PushSpring works with mapping partners to translate mobile in-app audiences to mobile web and desktop browser audiences.  \n\n**Target in-app audiences?**\n\nYes.  Use PushSpring data to target in-app users by IDFA and Android Advertising ID across Personas informed by device signals such as app ownership, location, and device settings. \n\n**Target on tablets?**\n\nYes.  Use PushSpring data to target in-app users by IDFA and Android Advertising ID across all iOS and Android mobile devices, including tablets.\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**How many targeting audiences does PushSpring offer?**\n\nPushSpring offers over 250 standard Personas along dimensions of Life Stage, Interest & Activity, and Intent.  Additionally, PushSpring App Genre audiences classify users by the count of apps owned by genre, across 19 genres, and within Games, 19 sub-genres. Demographic and custom audiences are also available.\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**How many unique users does PushSpring offer?**\n\nPushSpring offers over 200M unique mobile IDs, across the United States, Canada and Australia.\n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**Does PushSpring offer custom audiences?**\n\nYes.  PushSpring offers custom audience creation by attribute, including:\n\n  * Apps Owned\n  * Personas\n  * ComScore Demographics \n  * Apps Owned by Genre\n  * Manufacturer\n  * Location\n  * Carrier \n  * Platform \n  * Imported Audiences\n  * Device Language\n  * Cuebiq Retail Visits \n[block:api-header]\n{\n  \"type\": \"basic\"\n}\n[/block]\n**More questions? **\nContact Us hello@pushspring.com","excerpt":"","slug":"faq","type":"basic","title":"FAQ"}
[block:image] { "images": [ { "image": [ "https://files.readme.io/bTykRnQ0qr0zXAvYaezw_PushSpring_white%20background.png", "PushSpring_white background.png", "184", "35", "#31a2ba", "" ] } ] } [/block] Have a question? Check out some of our most frequently asked questions below and reach out if there is something more we can answer for you. We are always around: hello@pushspring.com [block:api-header] { "type": "basic", "title": "" } [/block] **What types of targeting data does PushSpring offer?** PushSpring provides device-level targeting data for verified, non-fraudulent, iOS and Android mobile app audiences. Use PushSpring data to target in-app users by IDFA and Android Advertising ID across Personas informed by device signals such as app ownership, location, and device settings. PushSpring audiences can also be used to target cross-device campaigns. [block:api-header] { "type": "basic" } [/block] **How does PushSpring collect data?** PushSpring audience data is collected from trusted, compliant sources, including PushSpring SDK implementations with mobile app publishers and strategic 3rd party partnerships. PushSpring does not collect any personally identifiable information, only anonymous data tied to resettable device advertising identifiers.  PushSpring is a member of the [IAB](http://www.iab.net/) and the [DAA Self-Regulatory Program](http://www.aboutads.info/), and we take numerous steps to ensure that all data collection is performed in compliance with posted [Self-Regulatory Principals for Online Behavioral Advertising](http://www.aboutads.info/obaprinciples) and [Self-Regulatory Principles to the Mobile Environment.](http://www.aboutads.info/DAA_Mobile_Guidance.pdf)  [block:api-header] { "type": "basic" } [/block] **What IDs does PushSpring collect / use for targeting audiences?** PushSpring data is tied to anonymous, resettable, and opt-out enabled advertising IDs associated with user devices (IDFA for iOS and Android Advertising ID for Android) to create fully permissioned, aggregated and anonymous behavioral audience segments. [block:api-header] { "type": "basic" } [/block] **From which mobile platforms does PushSpring collect data?** PushSpring currently offers targeting data for both iOS and Android app audiences. [block:api-header] { "type": "basic" } [/block] **How does PushSpring differ from other mobile data providers?** * Device-Level Data – PushSpring provides deterministic device-level targeting data for iOS and Android mobile app audiences. Target cross-device using Personas curated from IDFA and Android Advertising ID and created audiences informed by device signals such as app ownership, location, and device settings. * App-Originated Audiences - PushSpring audience data is sourced from mobile apps. Target users based on their true mobile app interests and behaviors, not by a probabilistic ID match to offline or browser-based interests. * Fraud-Free Mobile Targeting - All PushSpring data is processed to eliminate IDs associated with fraudulent traffic or app ownership patterns that are inconsistent with actual devices. Remove fraud from mobile campaigns by layering the entire PushSpring audience data set in your targeting criteria. [block:api-header] { "type": "basic" } [/block] **Can I use PushSpring data to:** **Target mobile web and desktop browser audiences?** Yes. PushSpring works with mapping partners to translate mobile in-app audiences to mobile web and desktop browser audiences. **Target in-app audiences?** Yes. Use PushSpring data to target in-app users by IDFA and Android Advertising ID across Personas informed by device signals such as app ownership, location, and device settings. **Target on tablets?** Yes. Use PushSpring data to target in-app users by IDFA and Android Advertising ID across all iOS and Android mobile devices, including tablets. [block:api-header] { "type": "basic" } [/block] **How many targeting audiences does PushSpring offer?** PushSpring offers over 250 standard Personas along dimensions of Life Stage, Interest & Activity, and Intent. Additionally, PushSpring App Genre audiences classify users by the count of apps owned by genre, across 19 genres, and within Games, 19 sub-genres. Demographic and custom audiences are also available. [block:api-header] { "type": "basic" } [/block] **How many unique users does PushSpring offer?** PushSpring offers over 200M unique mobile IDs, across the United States, Canada and Australia. [block:api-header] { "type": "basic" } [/block] **Does PushSpring offer custom audiences?** Yes. PushSpring offers custom audience creation by attribute, including: * Apps Owned * Personas * ComScore Demographics * Apps Owned by Genre * Manufacturer * Location * Carrier * Platform * Imported Audiences * Device Language * Cuebiq Retail Visits [block:api-header] { "type": "basic" } [/block] **More questions? ** Contact Us hello@pushspring.com