Acoustic Campaign Ideas

The Acoustic Ideas portal has moved! Please sign up for our new Ideas portal and submit your suggestions at

Provide proper tracking of Mobile Push sends when integrated with Unica

currently when you perform a mobile push from Unica there is no proper feedback loop to tell you what happened.

Through UBX we can get a Mobile Push Send update but that does not tell specifically which message was sent, just a messageID which is effectively a run instance.

WCA and UBX need to send back the actual message ID/Code so that you can tie the successful sending of a push notification to a specific message and device.

Any failed sends should also be provided (assuming this information is possible to obtain from Apple and Firebase)

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 11 2018
  • Needs More Information
How will this idea be used?

If you think that 10 messages were sent out then it's important to know that this actually happened.  Knowing that this happened means being able to link a known message to a known device.  The messageID does not link back to any known message so this is not useful for tracking from the Unica side.


Knowing that a specific message was sent means that contact history can be correctly maintained (this is important for certain campaign types).  It also means that devices that are known not to have a successful send could be followed up via an alternative channel.


Current use case for our customers are around service messages and legal messages.  Using for late payment notices for example, there are legal constraints on how often you contact a customer and remind them to pay - not knowing means we cannot ever be sure the message was sent.

What is your industry? Professional Services
What is the idea priority? Urgent
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    Diane Bowman commented
    July 11, 2018 13:52

    We are investigating this, and will respond once we have more information to post.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 14, 2018 16:47

    WCA has behavior events that are not published to UBX. There is Ibm Campaign Engage version independent integration that captures behavior events not published to UBX. Like hard / soft bounce. All behavior events available in WCA, Mobile,... should be published to UBX. 


    Platform 2.0 EDP should make it possible to work around these WCA limitations.  

  • Admin
    DAN GRIFFETH commented
    October 10, 2019 13:46

    as this is an older issue, perhaps this point is now moot as mobile engagement activities are passed into UBX now?