<?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 Engage Email Event passed as an API to another end point in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928975#M2013</link>
    <description>Hi.&lt;BR /&gt;In theory, you can define a Custom Type of Task that is triggered by the Email Event and makes a REST API call to a Connector endpoint.&lt;BR /&gt;I'm not sure what information is in the payload by default, I'd have to try it.&lt;BR /&gt;See: &lt;A href="https://documentation.sas.com/doc/en/cintcdc/production.a/cintag/ch-connectors-custom-setup.htm" target="_blank"&gt;https://documentation.sas.com/doc/en/cintcdc/production.a/cintag/ch-connectors-custom-setup.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 20 May 2024 04:08:55 GMT</pubDate>
    <dc:creator>t_charlesworth</dc:creator>
    <dc:date>2024-05-20T04:08:55Z</dc:date>
    <item>
      <title>SAS Engage Email Event passed as an API to another end point</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928972#M2012</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;SAS CI360 engage email captures email opt-outs as events. Could this be passed as part of API call from CI360 to another system instead of the option of using an agent to stream the events?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 03:21:50 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928972#M2012</guid>
      <dc:creator>jontpg</dc:creator>
      <dc:date>2024-05-20T03:21:50Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Engage Email Event passed as an API to another end point</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928975#M2013</link>
      <description>Hi.&lt;BR /&gt;In theory, you can define a Custom Type of Task that is triggered by the Email Event and makes a REST API call to a Connector endpoint.&lt;BR /&gt;I'm not sure what information is in the payload by default, I'd have to try it.&lt;BR /&gt;See: &lt;A href="https://documentation.sas.com/doc/en/cintcdc/production.a/cintag/ch-connectors-custom-setup.htm" target="_blank"&gt;https://documentation.sas.com/doc/en/cintcdc/production.a/cintag/ch-connectors-custom-setup.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 20 May 2024 04:08:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928975#M2013</guid>
      <dc:creator>t_charlesworth</dc:creator>
      <dc:date>2024-05-20T04:08:55Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Engage Email Event passed as an API to another end point</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928976#M2014</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be basic info like &amp;lt;email id&amp;gt;, &amp;lt;Opt-Out Flag value&amp;gt;.&amp;nbsp; Looking at option for our CRM to get this information straightaway when the opt-out happens.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then other option is create an agent which will get the opt-outs in a stream and that can be pushed to another systems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Assume with all this work some customization needs to be done and its not just out of the box.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks Tim.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 04:30:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928976#M2014</guid>
      <dc:creator>jontpg</dc:creator>
      <dc:date>2024-05-20T04:30:30Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Engage Email Event passed as an API to another end point</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928977#M2015</link>
      <description>Probably just some light configuration in defining the Connector... but at least you have a path to investigate.&lt;BR /&gt;</description>
      <pubDate>Mon, 20 May 2024 04:32:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/SAS-Engage-Email-Event-passed-as-an-API-to-another-end-point/m-p/928977#M2015</guid>
      <dc:creator>t_charlesworth</dc:creator>
      <dc:date>2024-05-20T04:32:55Z</dc:date>
    </item>
  </channel>
</rss>

