<?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>thread Customer Directory: smart group filters not working logically in Customer Engagement</title>
    <link>https://community.squareup.com/t5/Customer-Engagement/Customer-Directory-smart-group-filters-not-working-logically/m-p/769561#M1896</link>
    <description>&lt;P&gt;Help me figure out what I'm doing wrong!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a customer in my directory, Customer X, who has purchased Item A and Item B.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have defined two Smart Groups in my Customer Directory using filters:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Group A (Purchase Details: item or service WAS Item A)&lt;/LI&gt;&lt;LI&gt;Group B (Purchase Details: item or service WAS Item B; item or service WAS NOT Item A)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I expect Customer X to show up in Group A but &lt;STRONG&gt;not&lt;/STRONG&gt; Group B. However, she's showing up in both groups.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is going to mess up my email distribution when I send campaigns to Groups A and B — I don't want her to receive the email twice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I doing something wrong? Is this a bug? Thanks!&lt;/P&gt;</description>
    <pubDate>Sun, 21 Sep 2025 09:47:54 GMT</pubDate>
    <dc:creator>wool-friends</dc:creator>
    <dc:date>2025-09-21T09:47:54Z</dc:date>
    <item>
      <title>Customer Directory: smart group filters not working logically</title>
      <link>https://community.squareup.com/t5/Customer-Engagement/Customer-Directory-smart-group-filters-not-working-logically/m-p/769561#M1896</link>
      <description>&lt;P&gt;Help me figure out what I'm doing wrong!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a customer in my directory, Customer X, who has purchased Item A and Item B.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have defined two Smart Groups in my Customer Directory using filters:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Group A (Purchase Details: item or service WAS Item A)&lt;/LI&gt;&lt;LI&gt;Group B (Purchase Details: item or service WAS Item B; item or service WAS NOT Item A)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I expect Customer X to show up in Group A but &lt;STRONG&gt;not&lt;/STRONG&gt; Group B. However, she's showing up in both groups.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is going to mess up my email distribution when I send campaigns to Groups A and B — I don't want her to receive the email twice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I doing something wrong? Is this a bug? Thanks!&lt;/P&gt;</description>
      <pubDate>Sun, 21 Sep 2025 09:47:54 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Customer-Engagement/Customer-Directory-smart-group-filters-not-working-logically/m-p/769561#M1896</guid>
      <dc:creator>wool-friends</dc:creator>
      <dc:date>2025-09-21T09:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: Customer Directory: smart group filters not working logically</title>
      <link>https://community.squareup.com/t5/Customer-Engagement/Customer-Directory-smart-group-filters-not-working-logically/m-p/769864#M1897</link>
      <description>&lt;P&gt;It sounds like your Smart Groups are working as designed, but the filtering logic might need adjusting to achieve your desired result. Let’s break this down:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Why Customer X Appears in Both Groups&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For &lt;STRONG&gt;Group A&lt;/STRONG&gt;, the filter checks if the customer purchased Item A, which Customer X did—so she qualifies for this group.&lt;/LI&gt;&lt;LI&gt;For &lt;STRONG&gt;Group B&lt;/STRONG&gt;, the filter checks if the customer purchased Item B but not Item A. Since the condition “item or service WAS NOT Item A” might not exclude customers who also purchased Item A, it’s including Customer X.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Refining the Filters&lt;/STRONG&gt;:&lt;BR /&gt;To ensure Customer X doesn’t show up in both groups:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;For &lt;STRONG&gt;Group A&lt;/STRONG&gt;:&lt;BR /&gt;Keep the filter as is: Purchase Details: item or service WAS Item A.&lt;/LI&gt;&lt;LI&gt;For &lt;STRONG&gt;Group B&lt;/STRONG&gt;, modify the filter logic:&lt;BR /&gt;Purchase Details: item or service WAS Item B AND item or service WAS NOT Item A.&lt;BR /&gt;Using the logical "AND" ensures that only customers who purchased Item B &lt;STRONG&gt;and&lt;/STRONG&gt; didn’t purchase Item A will qualify.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Test Your Groups&lt;/STRONG&gt;:&lt;BR /&gt;After updating the filters, preview the groups in your Customer Directory to confirm the results.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Deduplicating Email Recipients&lt;/STRONG&gt;:&lt;BR /&gt;If you’re still concerned about customers receiving multiple emails, Square’s email campaigns automatically deduplicate recipients within a campaign. If a customer is in multiple groups used for the same campaign, they should only receive one email.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Submit Feedback&lt;/STRONG&gt;:&lt;BR /&gt;If the filters still don’t behave as expected, it’s worth contacting Square Support to verify if this is a bug or intended behavior. You can also suggest improving the filter logic for more precise group segmentation.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 03 Jan 2025 17:02:27 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Customer-Engagement/Customer-Directory-smart-group-filters-not-working-logically/m-p/769864#M1897</guid>
      <dc:creator>Stacelyn24</dc:creator>
      <dc:date>2025-01-03T17:02:27Z</dc:date>
    </item>
  </channel>
</rss>

