A custom trigger is created, with a number of attributes. The custom trigger is used within a Real-Time Marketing journey and the attributes are mapped to respective source fields. In the case of one/more of the source fields being empty, the custom trigger is failing to execute. Certain records tend to have some fields, as blank. This is impacting the execution of those records through the custom trigger.

It would be great if an inbuilt mechanism is available at the journey level to populate a default value, in case of the source field being empty. This particular feature is available for e-mails. When a personalization is added in the e-mail body, there is an option to add a default value, in case of the personalization field being empty.