Hi @stanciu , Please find the requested details Runtime namespace :
89800-acswebpushapp-stage API End point that returned 404 :
Please let us know if you need more information
Hi Akash,It is not doable from the OOB activities of ACC. As Craig
suggested you can split the audience and feed to individual deliveries
with different times. I feel that too will not help your cause 🙂
Consulting can assist you on a custom solution like timezone split or
Send time optimization. Please connect with your CSM to see if
Consulting can assist with your requirement. Another possibility is, if
the volumes are not too high, you can use Message Center. Prepare API
calls with the @sched...
We've created a simple Adobe I/O Runtime action, developed using NodeJS,
and successfully deployed our web push integration with Adobe Campaign
Standard.We used the Project Firefly template for the runtime project
and used the Campaign STAGE instance for this integration.The
application uses serverless deploy method.This is fine as expected and
we are able to send web push notifications from our ACS instance The
issue we're facing is that "wsk api create" commands generate API
endpoints that are...
Hi Marcel,Adobe Campaign can receive any asynchronous bounce even 6
months after sending. It depends upon how the target domain is sending
us the bounce messages.QUite possible that the user clicked on Report
Spam button on the delivery which comes to Adobe Campaign as a signal
via feedback loop. This is then processed by inMail module and the
delivery log gets updated. This is by design and hence the event date +
last modified field will get updated with the current date when the
bounce has bee...
Forecasting workflow is used on instances which only get the delivery
standard package. it helps with arbitration there. If you are seeing
Campaign Jobs workflow on your instance, it means you have deployed
Campaign standard package too. In that case you can stop Forecasting
workflow as it is not needed.