{"_id":"562014128a05d7230006ffdf","parentDoc":null,"user":"54861b9f3681d914006992a4","__v":3,"project":"54861bb654b3ce0b00367292","version":{"_id":"5620140f8a05d7230006ffac","project":"54861bb654b3ce0b00367292","__v":3,"createdAt":"2015-10-15T21:01:03.908Z","releaseDate":"2015-10-15T21:01:03.908Z","categories":["562014108a05d7230006ffad","562014108a05d7230006ffae","562014108a05d7230006ffaf","562014108a05d7230006ffb0","562014108a05d7230006ffb1","562014108a05d7230006ffb2","562014108a05d7230006ffb3","562014108a05d7230006ffb4","562014108a05d7230006ffb5","5666f7f5d784a70d00397bff","56967935b6d61f0d00acfb0b"],"is_deprecated":true,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"Moments","version_clean":"2.0.0","version":"2.0"},"category":{"_id":"56967935b6d61f0d00acfb0b","version":"5620140f8a05d7230006ffac","__v":0,"project":"54861bb654b3ce0b00367292","pages":[],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-01-13T16:20:05.396Z","from_sync":false,"order":4,"slug":"personalization","title":"Personalization"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2014-12-12T07:02:24.868Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"never","params":[],"url":""},"isReference":false,"order":1,"body":"At the heart of audiences is Adding a new audience that consists of three main actions \n\n1. Choose the right filter(s)\n2. Choose the right experience for that specific audience you have created ( if it's single or an A/B testing )\n3. Save, choose it's relevant position ( among other audiences ) and move to production\n\n\nWhen you first create a audience you are prompted to choose filter, you van actually do a keyword search or focus on a specific type of filters using the tags on the top left\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/I9eosPtwRGIGuAOjPYKS_segmentationPower:::at:::2x.jpg\",\n        \"segmentationPower@2x.jpg\",\n        \"1500\",\n        \"788\",\n        \"#169be4\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nOnce you choose a specific filter, you are now prompt to configure that specific filter, weather it's installed apps, specific events or even battery percentage, etc ... \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Not all filters need configuration\",\n  \"body\": \"There are some filters that do not require configuration, like \\\"Apply to all\\\" and other specific sub filters like high/low retention, but most do require specific configuration\"\n}\n[/block]\nOnce you added your your filter(s), at least one filter that is, you can create a **connection** between the filters that consists of a OR/AND logic between those filters.  \nYou can see that correlation on the top left toggle banner (enabled only if there is more than one filter active) \n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/uQMyVHkEQq6M3q32jkXm_Screen-Shot-2014-12-14-at-7.26.26-PM.jpg\",\n        \"Screen-Shot-2014-12-14-at-7.26.26-PM.jpg\",\n        \"994\",\n        \"160\",\n        \"#24506b\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nBest practices on building audiences with filters\n\n1. **Try not to overlap/contradict between filters **  \nIt will not make sense to use a filter that either fully contradicts another filter and enable an \"AND\" logic between them, or on the flip side create filters that overlap (include one or another) \n\n2. **Build filters base on your experience or based on Elasticode's Insights**   \nTry to make sense out of the audience groups you create and the relevant experience you would like to provide them, adapt your offering based on data, not hunches (see more about insights [here](doc:33-insights))\n\n3. **By default audiences are created in to \"Draft\" mode**   \nRemember that once you create a new audience and apply it, it automatically goes down to the bottom of the list on the audience list and is in \"Draft\" mode, in order to bring it to \"life\", move him to \"Production\" mode (see more on that in the [next section](doc:segments-in-productiondraft-mode))\n\n4. **\"Naming\" is important**   \nTry to provide a meaningful name to your audience, you would use that information later on when it comes to review, audit and analytics\n\n\nAs an example, this is how a full audience might look (with relevant filters, assigning the right experience and relevant name) \n\n\n##State/Value (Chosen experience)\n\nOnce you do create the list of relevant filters that defines your audience you can choose the relevant experience and correlate to your goals \n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"A/B testing mode\",\n  \"body\": \"You can define more than one State/Value for this audience under A/B testing mode ( the toggle resides  on the top right section above the experiences combo box)\"\n}\n[/block]","excerpt":"","slug":"23-working-with-filters","type":"basic","title":"Working with filters"}

Working with filters


At the heart of audiences is Adding a new audience that consists of three main actions 1. Choose the right filter(s) 2. Choose the right experience for that specific audience you have created ( if it's single or an A/B testing ) 3. Save, choose it's relevant position ( among other audiences ) and move to production When you first create a audience you are prompted to choose filter, you van actually do a keyword search or focus on a specific type of filters using the tags on the top left [block:image] { "images": [ { "image": [ "https://files.readme.io/I9eosPtwRGIGuAOjPYKS_segmentationPower@2x.jpg", "segmentationPower@2x.jpg", "1500", "788", "#169be4", "" ] } ] } [/block] Once you choose a specific filter, you are now prompt to configure that specific filter, weather it's installed apps, specific events or even battery percentage, etc ... [block:callout] { "type": "warning", "title": "Not all filters need configuration", "body": "There are some filters that do not require configuration, like \"Apply to all\" and other specific sub filters like high/low retention, but most do require specific configuration" } [/block] Once you added your your filter(s), at least one filter that is, you can create a **connection** between the filters that consists of a OR/AND logic between those filters. You can see that correlation on the top left toggle banner (enabled only if there is more than one filter active) [block:image] { "images": [ { "image": [ "https://files.readme.io/uQMyVHkEQq6M3q32jkXm_Screen-Shot-2014-12-14-at-7.26.26-PM.jpg", "Screen-Shot-2014-12-14-at-7.26.26-PM.jpg", "994", "160", "#24506b", "" ] } ] } [/block] Best practices on building audiences with filters 1. **Try not to overlap/contradict between filters ** It will not make sense to use a filter that either fully contradicts another filter and enable an "AND" logic between them, or on the flip side create filters that overlap (include one or another) 2. **Build filters base on your experience or based on Elasticode's Insights** Try to make sense out of the audience groups you create and the relevant experience you would like to provide them, adapt your offering based on data, not hunches (see more about insights [here](doc:33-insights)) 3. **By default audiences are created in to "Draft" mode** Remember that once you create a new audience and apply it, it automatically goes down to the bottom of the list on the audience list and is in "Draft" mode, in order to bring it to "life", move him to "Production" mode (see more on that in the [next section](doc:segments-in-productiondraft-mode)) 4. **"Naming" is important** Try to provide a meaningful name to your audience, you would use that information later on when it comes to review, audit and analytics As an example, this is how a full audience might look (with relevant filters, assigning the right experience and relevant name) ##State/Value (Chosen experience) Once you do create the list of relevant filters that defines your audience you can choose the relevant experience and correlate to your goals [block:callout] { "type": "info", "title": "A/B testing mode", "body": "You can define more than one State/Value for this audience under A/B testing mode ( the toggle resides on the top right section above the experiences combo box)" } [/block]