<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS CMS universal Group in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575235#M1215</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Im not sure what you mean by a drop campaign - however this is the same approach used for exclusion diagrams to remove unwanted customers (for example Opt outs, Bad Debt, Do Not Contact, Suspended etc).&lt;BR /&gt;&lt;BR /&gt;In your diagram you need to add an AND node after the OR node and connect the Link node to the AND. The numbers on the link node look suspicious (15 million). It looks like your control group diagram is selecting customers who are not in the control group, rather than those that are.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;James&lt;BR /&gt;</description>
    <pubDate>Sun, 21 Jul 2019 22:59:37 GMT</pubDate>
    <dc:creator>JamesAnderson</dc:creator>
    <dc:date>2019-07-21T22:59:37Z</dc:date>
    <item>
      <title>SAS CMS universal Group</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/574560#M1211</link>
      <description>&lt;P&gt;I work in marketing department in telecom company, where we create campaigns to our base on SAS CMs, I tried to create a universal control group, where SAS can drop certain count of MSAISN in order to exclude them on our campaigns, I couldn't find a way to do it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I need help!&lt;/STRONG&gt; I know ho to do it per campaign, but not per SAS CMS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you.&amp;nbsp;&lt;img id="smileyvery-happy" class="emoticon emoticon-smileyvery-happy" src="https://communities.sas.com/i/smilies/16x16_smiley-very-happy.png" alt="Smiley Very Happy" title="Smiley Very Happy" /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2019 13:31:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/574560#M1211</guid>
      <dc:creator>Fdwa-Adwan</dc:creator>
      <dc:date>2019-07-18T13:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: SAS CMS universal Group</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/574869#M1212</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Unlike the “Hold-out Control Groups” within a communication node, there isn’t a specific function within CI Studio to define a "Universal Control Group", and enforce its usage in campaigns.&lt;/P&gt;
&lt;P&gt;However we can use other feature of the software to implement a universal control group. If you create another campaign diagram which selects customers who are members of the control group, you can configure the final Cell (which represents the control group population) as “make this cell available for linking” and configure the diagram as “Use the most current data when referenced by a link” to be No. This means you can run the selection for your universal control group once, and it wont change (until you decide to refresh it and run it again).&lt;/P&gt;
&lt;P&gt;Then in your campaigns you can use a link node to re-use the cell from other diagram and tick “Exclude these subjects”.&lt;/P&gt;
&lt;P&gt;All that remains is deciding how to choose customers to go into the universal control group (perhaps look at SAS’s PROC SURVEYSELECT to get a stratified sample of your customer base), and then deciding which campaigns should implement the universal control group.&lt;/P&gt;
&lt;P&gt;Regards&lt;BR /&gt;James&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 06:00:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/574869#M1212</guid>
      <dc:creator>JamesAnderson</dc:creator>
      <dc:date>2019-07-19T06:00:36Z</dc:date>
    </item>
    <item>
      <title>Re: SAS CMS universal Group</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575186#M1214</link>
      <description>&lt;P&gt;thank you fro your help, but t I have 2 questions:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1- is the below suggestion is the same as "drop campaign" ?&lt;/P&gt;&lt;P&gt;2- can you check k the below screenshot?&lt;STRONG&gt; I didn't know where to connect the link in the diagram.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="3.JPG" style="width: 452px;"&gt;&lt;img src="https://communities.sas.com/t5/image/serverpage/image-id/31174i076BED2B84317C2D/image-size/large?v=v2&amp;amp;px=999" role="button" title="3.JPG" alt="3.JPG" /&gt;&lt;/span&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 21 Jul 2019 09:00:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575186#M1214</guid>
      <dc:creator>Fdwa-Adwan</dc:creator>
      <dc:date>2019-07-21T09:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: SAS CMS universal Group</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575235#M1215</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Im not sure what you mean by a drop campaign - however this is the same approach used for exclusion diagrams to remove unwanted customers (for example Opt outs, Bad Debt, Do Not Contact, Suspended etc).&lt;BR /&gt;&lt;BR /&gt;In your diagram you need to add an AND node after the OR node and connect the Link node to the AND. The numbers on the link node look suspicious (15 million). It looks like your control group diagram is selecting customers who are not in the control group, rather than those that are.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;James&lt;BR /&gt;</description>
      <pubDate>Sun, 21 Jul 2019 22:59:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575235#M1215</guid>
      <dc:creator>JamesAnderson</dc:creator>
      <dc:date>2019-07-21T22:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: SAS CMS universal Group</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575633#M1218</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/195823"&gt;@JamesAnderson&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Respectfully disagree... I'd not use Cells / Links for Universal Control Groups functionality.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Typical marketing requirements for Universal (Global) Control Group - all that I have seen - would require, at a very least:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;1) That&amp;nbsp;it was persistent and stable over very long periods of time (6 month - 1 year - "forever / undefined"), an need to be robust -&amp;nbsp;accidentally losing and recreating a control group from scratch is absolutely unacceptable&lt;/P&gt;&lt;P&gt;2) That it allowed incremental additions from a portion of new customers, so it won't miss out its share of new customer population throughout the group's lifetime.&lt;/P&gt;&lt;P&gt;3) That it could be used for reporting. One needs to be able to build a report comparing long-term performance of Universal Control Group (as a whole) with Universal Target Group (as a whole).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Storing "static" diagram cells as storage for Universal Control Group in my view does not satisfy any of these 3 requirements...&amp;nbsp; &amp;nbsp; There are lots of ways how the contents of a cell can be cleared or lost, accidentally and not... It includes many kinds of upstream diagram modifications, accidental diagram reruns, using many kinds of MATables cleanup procedures, some scenarios to system restore after failure, etc. And once it's gone, there is essentially no way back. This is not something one can rely on to be a robust and guaranteed storage for 1 a year.&amp;nbsp; &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Requirements 2 and 3 will not be satisfied unless Universal Control Group is being materialized to the actual database table. One will need to introduce a customized database table (CDM or CMDM) for the Universal Control Group, and implement a mechanism to&lt;BR /&gt;store it there. At this point, it becomes easier to just add this table to the infomap... And there is no more need for a statically linked cell altogether...&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 04:07:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575633#M1218</guid>
      <dc:creator>Dmitry_Alergant</dc:creator>
      <dc:date>2019-07-23T04:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: SAS CMS universal Group</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575636#M1219</link>
      <description>Hi Dmitry,&lt;BR /&gt;The points you raise are all good ones, and I agree with them all. I didn't go into much detail about how to decide on the UCG membership, other than a suggestion about PROC SURVEYSELECT. I completely agree that the best approach is to use a table carefully populated with the UCG members.  In terms of excluding UCG members from a campaign, Id still argue that a linked cell back to a diagram that has selected everybody from the UCG table is the easiest and most consistent way to apply it across many campaigns, and allows you to control the execution of the query to refresh the cell (or not), in the same way we do for other types of "standard exclusions".  But it would also be valid to put a Select Node in each campaign and run the query against the UCG table every time.&lt;BR /&gt;Cheers&lt;BR /&gt;James&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Jul 2019 04:47:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-CMS-universal-Group/m-p/575636#M1219</guid>
      <dc:creator>JamesAnderson</dc:creator>
      <dc:date>2019-07-23T04:47:37Z</dc:date>
    </item>
  </channel>
</rss>

