Hi @david--garcia  that option looks like, is for the email sending validity period and not the actual DM expiry which I am looking for.

Hi @david--garcia  could you please help me further on this.

its actually showing in logs of the delivery.  this is what we want to pick up ahead of time.

 @david--garcia   can you guide me on which one would be appropriate?

to elaborate my ask, currently when we set up deliveries , we prepare them in advance but they expire before deployment .as the STR_NMSOPTION_DELIVERY_PENDING_CANCELDELAY is configured to 30 days, the clean up task cancels our deliveries and it is causing a problem.so we are looking for a some repor...

Hi @david--garcia  Thank you for your assistance on this, instead of campaigns, I can use the target dimension as deliveries correct to filter out just the delivery labels?

Hi Team, I am looking for some help in getting a daily report of deliveries that are going to expire with the next 7days, I don't see any OOB feature available in ACS for this one. can someone please guide me further on this.

Hi Team,I am looking for some solution which can help me in setting up monitoring for the developer console UI, can I achieve this via some workflow or  monitoring tool like zabbix?I want to check if the page loads and also login using my email and passwd to ensure the site is up and running.

Yes, i do have the names for the events unique. Profile and realtime.

 for the first event the publication worked fine but when I tried for next it gives me the error described in my question. I already have transactional message events linked to realtime, these new events are profile based. I don't need to do publication correct after importing my package?