Expand my Community achievements bar.

SOLVED

SMS API call from Adobe campaign classic v7 to 3rd party

Avatar

Level 1

Hi All,

 

Need some idea to solve below :

 

Curent Approach:

1. Via campaign WF in Adobe campaign sharing the flat file with mobile number and message to a 3rd party vender, and 3rd party is mobile company who use this info and send the SMS

 

Problem: 3rd party vender has difficulty and complex internal process to process these file 

 

Thoughts: looking forward to automating and remove the flat-file integration and replace with  API calls

or any other solution.

 

Does anyone have some solutions or ideas to share?

 

Thanks.

 

1 Accepted Solution

Avatar

Correct answer by
Level 3

Is there any reason why you can't create an external account for this to connect Adobe Campaign directly to the SMS provider?

Not only does this allow you to create and send SMS messages from Adobe Campaign, but it also writes the messages to the delivery logs so you can see the history of SMS sends to each recipient.

Ext account (requires configuration/authentication):

taplondon_josh_0-1622187969564.png

SMS delivery in a campaign workflow:

taplondon_josh_1-1622188162127.png

Thanks,

Josh

View solution in original post

8 Replies

Avatar

Community Advisor

Hello @DigitalMarket 

 

You can use the javascript code to send the data directly to SMS API.

 

Here is a sample code for Bitly API call. You may have to change the API endpoint and credentials to set this up. Also, some alternation will be required depending on how your SMS provider is handing the authentication.

 

https://www.slideshare.net/DavidGarcia1264/adobe-campaign-classic-shortening-links-with-bitly-api 

Code by: @david--garcia 

 


     Manoj
     Find me on LinkedIn

Avatar

Correct answer by
Level 3

Is there any reason why you can't create an external account for this to connect Adobe Campaign directly to the SMS provider?

Not only does this allow you to create and send SMS messages from Adobe Campaign, but it also writes the messages to the delivery logs so you can see the history of SMS sends to each recipient.

Ext account (requires configuration/authentication):

taplondon_josh_0-1622187969564.png

SMS delivery in a campaign workflow:

taplondon_josh_1-1622188162127.png

Thanks,

Josh

Avatar

Level 1
Currently SMS provider is sending the SMS delivery, they want us to send the data and they will be sending the SMS delivery.

Avatar

Level 3

The SMS provider still sends the messages for you, the connector just means you don't need to worry about sending flat-files or making API calls to them.


Here's the documentation describing how to connect Adobe Campaign to a SMPP provider:

https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/sending-messages-on-...

Avatar

Level 6
the other avantage to use standard or extended SMPP connector is also to do not have to build a dedicated workflow to retrieve SMS status in order to update broadlogs...

Avatar

Level 1

Thanks, both, this sounds good, I have checked the spec, have one question:

1. Any IP whitelisting required either from the campaign side or SMS server-side? if yes which are the IPs that can be used? 

2. Any other configuration from the SMS server vendor side needs to be done before we or after integration?

Avatar

Administrator
Hi @tapcxm_josh & @LaurentLam, Can any of you please help @DigitalMarket further with their query? Thanks!


Sukrity Wadhwa

Avatar

Level 6

In fact that depends of the implementation architecture: in Adobe hosted environment, you'll get informations from Adobe and they'll ask you SMS provider informations. The IP address to be whitelist is the one from AC Server. You'll get informations here:

https://experienceleague.adobe.com/docs/campaign-classic/using/sending-messages/sending-messages-on-...

 

keywords to search in the doc: TCP, Port