@gaurav_chaturvedi
You have to reach out to the client care or you account manager to confirm interest for send-time optimization.
Then Adobe will proceed and turn it on for production.
Thanks,
David
@Poonam2024
It's the normal behavior. Auto response works only for exact match of the Keyword. You need to add some text for the OOTB SMPP connector.
You can develop a custom connector but then you'll need to bypass the mid because the mid returns the incoming SMS based on a scheduler.
Thanks,...
@rick_j_alexander
you can use this query as example and adding journey version Id in the criteria
SELECT
AE._experience.customerJourneyManagement.entities.journey.journeyActionName,
AE._experience.customerJourneyManagement.entities.journey.journeyActionID,
AE._experience.customerJourneyMana...
@mustufam5967803
Weekly and daily frequency cap was added in AJO release 24.1- You can now specify the maximum number of messages sent to a customer profile in a week or a day, in addition to month. The frequency cap is based on the selected calendar period and reset at the beginning of the corre...
@o_X
I don't think it's a good idea to use typology as It may not be scalable for big deliveries.
Easiest way is to create a workflow (scheduled or use post process in external account), collect new broadlogs and update your table 'cus:unsub' .
You can also do it in your campaign workflow in cas...
@Kumar_27
auto sequence were added to ACC to avoid OOTB sequence exhaustion when using autopk in schema.
It's allowing tables to have their own sequence and not use xtkID used by delivery logs tracking logs etc.
It was introduced because customers with big data volume were having issue with dat...
@SorenDP
The cryptString() function is salted with the time, so will never produce the specific value you've been asked to get.
If you encrypt same string with same password and without salt, you will get same result
Thanks,
David
Hi there,
I need help to get the data from a JSON object using SQL in AJO.
{
"consent": {
"idSpecific": {
"Phone": {
"75708": {
"marketing": {
"sms": {
"val": "y",
"time": "2023-12-06T17:22:46.118Z"
}
}
...