Skip to main content

#Mobile Push Notifications1 debatiendo

Hi everyone,

I'm working on a MobilePush Journey where customers can enter the Journey at different times. The Push is triggered when a customer arrives at a specific location, and the message should remain visible in the Inbox for 24 hours after the individual Push is sent.

The issue is that under Delivery Options → Send Copy to Inbox, I can only configure a fixed End Date and End Time.

What I need is essentially:

Expiration Date = Push Send Time + 24 hours

For example:

  • Customer A receives the Push at 10:00 → expires the next day at 10:00
  • Customer B receives the Push at 18:30 → expires the next day at 18:30

Since contacts enter the Journey at different times, a fixed End Date/Time doesn't work for this use case.

I also have an expirationDate custom key under Advanced Options → Add Custom Functionality. I tried calculating the value dynamically with AMPscript:

 

%%=FormatDate(DateAdd(Now(),1,"D"),"yyyy-MM-ddTHH:mm:ss")=%% 

 

However, I haven't been able to get this approach working.

Is there a supported way in MobilePush / Journey Builder to set the Inbox expiration dynamically to Send Time + 24 hours for each contact?

Alternatively, can the expirationDate custom key be dynamically populated based on the actual Push send time?

Thanks! 

 

#Marketing Cloud Engagement  #Mobile Push Notifications

Have a mobile app or thinking about adding 

location-based mobile push notifications in your marketing program? 

 

If so, you don’t want to miss the October 15th session! The product team will give a deep dive into all things Marketing Cloud Mobile Push as well as show you how to implement and activate it for your push notifications. They will also address questions around privacy, use cases for mobile push geolocation, and share a bit of the roadmap. Register Now: sforce.co/2GoxfvZ

Hi Alex, I saw your post about Mobile Push Notifications, Firebase/GCM migration. I'm learning about all of this for the first time and I'm a bit lost. Have you figured it out?

5 comentarios
  1. 10 jul 2018, 00:09
    Your firebase account has a legacy key, look under Project Settings -> Cloud Messaging