BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
israelmndz
Calcite | Level 5

Hi.

I am developing a campaign in SAS RTDM and I need to send SMS notifications to clients that apply to the campaign. I have already added the email and sms response channel but I am not sure that they can be sent from SAS or have to use other software.

 

I hope you can help me.

 

I would appreciate it

1 ACCEPTED SOLUTION

Accepted Solutions
Dmitry_Alergant
Pyrite | Level 9

The most appropriate way to do that is outside of SAS RTDM.   For real-time triggered outbound campaigns with SAS RTDM, normally you'd have some sort of middleware or an integration adapter that processes events and makes a request to SAS RTDM campaign.

You will need to implement an integration capability into that middleware or adapter. Make it interpret SAS RTDM's response ("Email" and "SMS" response channels) and act accordingly to that response - actually trigger channel APIs to send these messages.

 

That is a simplified vision of architecture that we normally build for our clients, and done it successfully on many projects (we even have a reusable Java framework we use to building these "integration adapters").

 

Screen Shot 2019-11-18 at 1.10.56 PM.png

 

 

If you are using SAS ESP for initial events processing and trigger SAS RTDM (not everyone does), then it is possible to leverage an out-of-the-box REST subscriber adapter to have ESP making a call to RTDM, and then having RTDM response sent back to ESP (into another source window) - so that SAS ESP could then process the response, and initiate the actual SMS or Email communication using its adapters.  This allows minimizing custom coding (you may not need that customized "integration adapter" component in this case) but it comes with a separate set of complexities and limitations. Some of our clients decided to implement a customized integration adapter even though they used SAS ESP for initial event processing. There are tradeoffs and choices to be made.

 

Another option you can hear about is to use the Process Node (written in DS2 or Groovy language) to initiate an outbound API call from within the RTDM diagram (before the Reply node). Which I don't recommend. Before the processing has reached a Reply node on a diagram, you don't have Treatments assigned,  don't yet have important identifiers (response tracking code, treatment tracking code) required to track this contact and correlate it with the Contact and Response history in CDM, etc.  It can be used to send an email or SMS as a quick prototype, but we do not recommend this as part of an integrated production solution.       

 

The proper way is to rely on Reply nodes and then having something outside of RTDM (the "integration adapter", or SAS ESP) processing the response and acting accordingly (actually sending the communication, etc.).

 

Hope this helps!

 

 

-------
Dmitriy Alergant, Tier One Analytics

View solution in original post

2 REPLIES 2
Dmitry_Alergant
Pyrite | Level 9

The most appropriate way to do that is outside of SAS RTDM.   For real-time triggered outbound campaigns with SAS RTDM, normally you'd have some sort of middleware or an integration adapter that processes events and makes a request to SAS RTDM campaign.

You will need to implement an integration capability into that middleware or adapter. Make it interpret SAS RTDM's response ("Email" and "SMS" response channels) and act accordingly to that response - actually trigger channel APIs to send these messages.

 

That is a simplified vision of architecture that we normally build for our clients, and done it successfully on many projects (we even have a reusable Java framework we use to building these "integration adapters").

 

Screen Shot 2019-11-18 at 1.10.56 PM.png

 

 

If you are using SAS ESP for initial events processing and trigger SAS RTDM (not everyone does), then it is possible to leverage an out-of-the-box REST subscriber adapter to have ESP making a call to RTDM, and then having RTDM response sent back to ESP (into another source window) - so that SAS ESP could then process the response, and initiate the actual SMS or Email communication using its adapters.  This allows minimizing custom coding (you may not need that customized "integration adapter" component in this case) but it comes with a separate set of complexities and limitations. Some of our clients decided to implement a customized integration adapter even though they used SAS ESP for initial event processing. There are tradeoffs and choices to be made.

 

Another option you can hear about is to use the Process Node (written in DS2 or Groovy language) to initiate an outbound API call from within the RTDM diagram (before the Reply node). Which I don't recommend. Before the processing has reached a Reply node on a diagram, you don't have Treatments assigned,  don't yet have important identifiers (response tracking code, treatment tracking code) required to track this contact and correlate it with the Contact and Response history in CDM, etc.  It can be used to send an email or SMS as a quick prototype, but we do not recommend this as part of an integrated production solution.       

 

The proper way is to rely on Reply nodes and then having something outside of RTDM (the "integration adapter", or SAS ESP) processing the response and acting accordingly (actually sending the communication, etc.).

 

Hope this helps!

 

 

-------
Dmitriy Alergant, Tier One Analytics
Dmitry_Alergant
Pyrite | Level 9

Obviously, in order to make all of that work, you need to know who your channel providers are and what APIs they provide. You need an Email Marketing Service Provider, and an SMS service provider (or possibly the same service if it supports both channels) to provide you an API allowing you to initiate these communications in real-time.     Email marketing service provider service is where you manage your email templates, unsubscribe capabilities, response tracking, spam filters bypasses, etc. -  most organizations are already using one or multiple of such services for their batch email campaign needs. 


SAS CI 360 Engage Email is one of the options for the email channel needs (though obviously not the only one) - and it can also be used to send real-time event-driven email messages originated from SAS RTDM campaigns. 

 

As of today, SMS needs to be covered by a third-party service provider. There are many providers available on the market.

 

 

 

-------
Dmitriy Alergant, Tier One Analytics

Review SAS CI360 now.png

 

Want to review SAS CI360? G2 is offering a gift card or charitable donation for each accepted review. Use this link to opt out of receiving anything of value for your review.

 

 

 

 

SAS Customer Intelligence 360

Get started with CI 360

Review CI 360 Release Notes

Open a Technical Support case

Suggest software enhancements

Listen to the Reimagine Marketing podcast

Assess your marketing efforts with a free tool

 

Training Resources

SAS Customer Intelligence Learning Subscription (login required)

Access free tutorials

Refer to documentation

Latest hot fixes

Compatibility notice re: SAS 9.4M8 (TS1M8) or later

 

 

How to improve email deliverability

SAS' Peter Ansbacher shows you how to use the dashboard in SAS Customer Intelligence 360 for better results.

Find more tutorials on the SAS Users YouTube channel.

Review SAS CI360 now.png

 

Want to review SAS CI360? G2 is offering a gift card or charitable donation for each accepted review. Use this link to opt out of receiving anything of value for your review.

 

 

 

 

SAS Customer Intelligence 360

Get started with CI 360

Review CI 360 Release Notes

Open a Technical Support case

Suggest software enhancements

Listen to the Reimagine Marketing podcast

Assess your marketing efforts with a free tool

 

Training Resources

SAS Customer Intelligence Learning Subscription (login required)

Access free tutorials

Refer to documentation

Latest hot fixes

Compatibility notice re: SAS 9.4M8 (TS1M8) or later

 

 

Discussion stats
  • 2 replies
  • 2248 views
  • 7 likes
  • 2 in conversation