{"_id":"562014128a05d7230006ffdd","parentDoc":null,"__v":12,"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"},"user":"54861b9f3681d914006992a4","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"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2014-12-12T10:34:45.424Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"never","params":[],"url":""},"isReference":false,"order":0,"body":"Audiences are the heart of personalization, Now we can apply different experiences ( a.k.a Onboarding, moments experiences, states and values ) to different audiences \n\nHere's how it works:\n\n\n* You create [Onboarding](doc:sdk-intro)  , or a [Moment](doc:moments)  experience,   [Cases](doc:cases)  and / or [Dynamic objects](doc:creating-dynamic-objects) \n* Review them...\n* And now ... you can build and apply audiences, in the [next section](doc:23-building-segments) you would learn how to apply new segments\n* Each Experience/Case/Dynamic-object has it's own audience list.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/IJXmHPguQwunYK5jkOVr_magnify.jpg\",\n        \"magnify.jpg\",\n        \"941\",\n        \"400\",\n        \"#9e5a57\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Segment list\",\n  \"body\": \"The Audience list is relevant to each Experience/Case/Dynamic-object, this means that if you do not have any audience applied just yet, it will revert to a default​ option\"\n}\n[/block]\nIn the audience list, you might see a call to action button indicating you still haven't created any audience just yet ... Or you can see the list of all available audiences. \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Order matters!\",\n  \"body\": \"On the right top bar there is a button that allows you to re-order the audiences, this makes sense because order matters! the algorithm that manages the decision works on a \\\"First-come-first-serve\\\" basis, so the top audience is addressed first, then the 2nd and on and on.\"\n}\n[/block]\n##Real time interaction##\nOnce you click on the plus button, the row would expand and you could see all live interaction around that segment \n\n##Editing a audience\nOnce you click on the edit button, you would be redirected to the segment studio where you could change content and parameters that built this segment, more about that  [in two sections](doc:23-working-with-filters) \n\n##Deleting a audience ##\nOnce you delete a segment, you will not have the capability to reproduce it \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Analytics for terminated segments\",\n  \"body\": \"In some cases (if the platform indicated \\\"traffic\\\" that went through that segment) we will preserve all history analytical data that was related to this segment.\"\n}\n[/block]\n\n\n##Production/Draft mode##\nA Segment could be in \"Production\" or in \"Draft\" mode ( [More info](doc:production-vs-draft) )\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Draft mode\",\n  \"body\": \"Draft mode only applies to end users that are in development mode  (SDK flag in development mode) and will not affect end users in production.\"\n}\n[/block]\n\n\n##Reading a row in the segment list:##\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/omF65nC5QZKaG9D81LJb_Screen-Shot-2014-12-12-at-3.44.54-PM.jpg\",\n        \"Screen-Shot-2014-12-12-at-3.44.54-PM.jpg\",\n        \"1194\",\n        \"319\",\n        \"#0e94cf\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"22-segments","type":"basic","title":"Audiences"}
Audiences are the heart of personalization, Now we can apply different experiences ( a.k.a Onboarding, moments experiences, states and values ) to different audiences Here's how it works: * You create [Onboarding](doc:sdk-intro) , or a [Moment](doc:moments) experience, [Cases](doc:cases) and / or [Dynamic objects](doc:creating-dynamic-objects) * Review them... * And now ... you can build and apply audiences, in the [next section](doc:23-building-segments) you would learn how to apply new segments * Each Experience/Case/Dynamic-object has it's own audience list. [block:image] { "images": [ { "image": [ "https://files.readme.io/IJXmHPguQwunYK5jkOVr_magnify.jpg", "magnify.jpg", "941", "400", "#9e5a57", "" ] } ] } [/block] [block:callout] { "type": "info", "title": "Segment list", "body": "The Audience list is relevant to each Experience/Case/Dynamic-object, this means that if you do not have any audience applied just yet, it will revert to a default​ option" } [/block] In the audience list, you might see a call to action button indicating you still haven't created any audience just yet ... Or you can see the list of all available audiences. [block:callout] { "type": "warning", "title": "Order matters!", "body": "On the right top bar there is a button that allows you to re-order the audiences, this makes sense because order matters! the algorithm that manages the decision works on a \"First-come-first-serve\" basis, so the top audience is addressed first, then the 2nd and on and on." } [/block] ##Real time interaction## Once you click on the plus button, the row would expand and you could see all live interaction around that segment ##Editing a audience Once you click on the edit button, you would be redirected to the segment studio where you could change content and parameters that built this segment, more about that [in two sections](doc:23-working-with-filters) ##Deleting a audience ## Once you delete a segment, you will not have the capability to reproduce it [block:callout] { "type": "warning", "title": "Analytics for terminated segments", "body": "In some cases (if the platform indicated \"traffic\" that went through that segment) we will preserve all history analytical data that was related to this segment." } [/block] ##Production/Draft mode## A Segment could be in "Production" or in "Draft" mode ( [More info](doc:production-vs-draft) ) [block:callout] { "type": "warning", "title": "Draft mode", "body": "Draft mode only applies to end users that are in development mode (SDK flag in development mode) and will not affect end users in production." } [/block] ##Reading a row in the segment list:## [block:image] { "images": [ { "image": [ "https://files.readme.io/omF65nC5QZKaG9D81LJb_Screen-Shot-2014-12-12-at-3.44.54-PM.jpg", "Screen-Shot-2014-12-12-at-3.44.54-PM.jpg", "1194", "319", "#0e94cf", "" ] } ] } [/block]