<?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: How to keep a count in Sales Email</title>
    <link>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018076#M9039</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/627412"&gt;@CDP2023&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is currently no way to do this via workflow, without custom development based on the HubSpot API, either via a custom code workflow action or a standalone application.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The reason why this is not possible via workflow is that re-enrollment based on sales emails sends is not possible. Neither do activity-based workflows exist which could trigger with each new activity. There are workarounds using re-enrollment based list membership but these limit re-enrollment to one time per day – making a counter inaccurate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;At the moment, this cannot be done out of the box.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
    <pubDate>Mon, 29 Jul 2024 12:48:30 GMT</pubDate>
    <dc:creator>karstenkoehler</dc:creator>
    <dc:date>2024-07-29T12:48:30Z</dc:date>
    <item>
      <title>How to keep a count</title>
      <link>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018045#M9038</link>
      <description>&lt;P&gt;Hi!&lt;BR /&gt;&lt;BR /&gt;I wanted to know whether it would be possible to have a workflow which could enroll contacts when they would have been sent a sales/1-1 email (not a marketing email specifically)?&lt;BR /&gt;&lt;BR /&gt;I spoke with Hubspot support and they mentioned these conditions:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CDP2023_0-1722253382590.png" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/123445i1D2D350A7228EE30/image-size/medium?v=v2&amp;amp;px=400" role="button" title="CDP2023_0-1722253382590.png" alt="CDP2023_0-1722253382590.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;But I can see if the user decides to open the same sales email twice then it is going to get enrolled again which could cause duplicates in out count.&lt;BR /&gt;The end goal what we need is to keep a count of how many sales email have been sent to a contact from a aparticular agent.&lt;BR /&gt;&lt;BR /&gt;Does any one have any idea with respect to this?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;&lt;P&gt;CDP&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 11:45:34 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018045#M9038</guid>
      <dc:creator>CDP2023</dc:creator>
      <dc:date>2024-07-29T11:45:34Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep a count</title>
      <link>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018076#M9039</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/627412"&gt;@CDP2023&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is currently no way to do this via workflow, without custom development based on the HubSpot API, either via a custom code workflow action or a standalone application.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The reason why this is not possible via workflow is that re-enrollment based on sales emails sends is not possible. Neither do activity-based workflows exist which could trigger with each new activity. There are workarounds using re-enrollment based list membership but these limit re-enrollment to one time per day – making a counter inaccurate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;At the moment, this cannot be done out of the box.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 12:48:30 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018076#M9039</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2024-07-29T12:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep a count</title>
      <link>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018147#M9041</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/111325"&gt;@karstenkoehler&lt;/a&gt;&amp;nbsp; Thanks for you response!&lt;BR /&gt;How do you see this to be done with using custom_code?&lt;BR /&gt;is there an api in Hubspot which gives only the sales emails or how do you envision this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;CDP&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 14:38:55 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018147#M9041</guid>
      <dc:creator>CDP2023</dc:creator>
      <dc:date>2024-07-29T14:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep a count</title>
      <link>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018155#M9042</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/627412"&gt;@CDP2023&lt;/a&gt;&amp;nbsp;I'm not a developer but I'd start by looking at the engagements API endpoint. An application could check whether engagements are sent emails and increase a property value.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2024 14:42:51 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Sales-Email/How-to-keep-a-count/m-p/1018155#M9042</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2024-07-29T14:42:51Z</dc:date>
    </item>
  </channel>
</rss>

