{"_id":"59515d0ee706bd005ffba0e6","project":"5661bda6f5a87e0d00db3285","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"},"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"},"user":"5661cc12f183880d004d3193","githubsync":"","__v":0,"parentDoc":null,"metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-06-26T19:14:22.522Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"Are you just getting started using Custom Segments or data for targeting? We are happy to provide a few best practices to help you get started on the right foot! Check out the below suggestions, and as always, don't hesitate to reach out to hello:::at:::pushspring.com for immediate assistance. \n[block:api-header]\n{\n  \"title\": \"Segment Size\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/bf561eb-Estimated_Device_Count.png\",\n        \"Estimated Device Count.png\",\n        449,\n        92,\n        \"#e9e8e6\"\n      ]\n    }\n  ]\n}\n[/block]\nIdeal segments size for activation is between **2–50MM**, this size ensures both scale and targeting.\n\nA segment containing **over 50MM devices is very broad**, at this size you are approaching general population and you may want to try segmenting into multiple, narrower audiences. This will provide additional flexibility and optimization levers.\n\nIf looking at a few large apps with a similar focus (ie. Netflix and HBO Go, Pandora and Spotify, etc.) try single app segments for most granular insights.\n\nAre you working with niche audience? Aim for **a minimum of ~500K devices**\n\nAre you simply looking to learn more about an audience? For general analytics and insights, we suggest using an audience of **~30K** to get you started understanding your audience.\n\nSegment your target into a few, narrower audiences to provide additional flexibility and optimization levers.\n\n[block:api-header]\n{\n  \"title\": \"Using Personas\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/a08eb3a-Personas.png\",\n        \"Personas.png\",\n        298,\n        116,\n        \"#04b8bf\"\n      ]\n    }\n  ]\n}\n[/block]\nInclude a Persona to leverage recency data and help build a stronger segment. Recency is based on the app download date.\n\nFor instance, if you are looking to build a segment around user Intent, such as in-market auto buyers or home buyers, try Auto Shoppers or Home Shoppers Personas. \n\nIf you are looking to build a segment for a specific Life Stage, such as Expectant Parents or College Kids try Personas by those same names. \n\n[block:api-header]\n{\n  \"title\": \"Other Helpful Tips\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/fd879e1-Other_Tips.png\",\n        \"Other Tips.png\",\n        566,\n        123,\n        \"#e9edf0\"\n      ]\n    }\n  ]\n}\n[/block]\nTo make the best use of the PushSpring data set always include app ownership data in your audience. \n\nUse the “has none” option to create a suppression audience for your campaign. This allows you to either eliminate current customers or target customers with no related apps.  \n\nUse “And” statements to narrow audience size, use “Or” to broaden.\n\nUse the Related Apps feature to help ideate similar apps to include in your segment.","excerpt":"","slug":"custom-segment-success","type":"basic","title":"Custom Segment Success"}

Custom Segment Success


Are you just getting started using Custom Segments or data for targeting? We are happy to provide a few best practices to help you get started on the right foot! Check out the below suggestions, and as always, don't hesitate to reach out to hello@pushspring.com for immediate assistance. [block:api-header] { "title": "Segment Size" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/bf561eb-Estimated_Device_Count.png", "Estimated Device Count.png", 449, 92, "#e9e8e6" ] } ] } [/block] Ideal segments size for activation is between **2–50MM**, this size ensures both scale and targeting. A segment containing **over 50MM devices is very broad**, at this size you are approaching general population and you may want to try segmenting into multiple, narrower audiences. This will provide additional flexibility and optimization levers. If looking at a few large apps with a similar focus (ie. Netflix and HBO Go, Pandora and Spotify, etc.) try single app segments for most granular insights. Are you working with niche audience? Aim for **a minimum of ~500K devices** Are you simply looking to learn more about an audience? For general analytics and insights, we suggest using an audience of **~30K** to get you started understanding your audience. Segment your target into a few, narrower audiences to provide additional flexibility and optimization levers. [block:api-header] { "title": "Using Personas" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/a08eb3a-Personas.png", "Personas.png", 298, 116, "#04b8bf" ] } ] } [/block] Include a Persona to leverage recency data and help build a stronger segment. Recency is based on the app download date. For instance, if you are looking to build a segment around user Intent, such as in-market auto buyers or home buyers, try Auto Shoppers or Home Shoppers Personas. If you are looking to build a segment for a specific Life Stage, such as Expectant Parents or College Kids try Personas by those same names. [block:api-header] { "title": "Other Helpful Tips" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/fd879e1-Other_Tips.png", "Other Tips.png", 566, 123, "#e9edf0" ] } ] } [/block] To make the best use of the PushSpring data set always include app ownership data in your audience. Use the “has none” option to create a suppression audience for your campaign. This allows you to either eliminate current customers or target customers with no related apps. Use “And” statements to narrow audience size, use “Or” to broaden. Use the Related Apps feature to help ideate similar apps to include in your segment.