SMS Sendlog doesn't write custom Key value from API request payload for non-personalised message content
Last updated 2021-06-01 ·Reference W-9311452 ·Reported By 0 users
We have noticed that due to a known bug in the system causing failure to write custom key value from API request payload to the SMS Sendlog if the actual message content is a plain text(without personalisation).
1) Enable Send and create SMS Send Logging Data Extesion with at least one custom field in the sendlog DE
2) Create two API messages. One with personalise content (like %%FIRSTNAME%%) and the other one with a plain text
3) Using messageContact perform a send to the above two messages. Ensure that the custom field matches with sendlog DE.
As result the sendlog will only populate the values for customfield where personalization is present but fail to do so for the plaintext(without personalisation) SMS record even if the custom field is mapped with the API payload value.
As of now, we recommend using the personalisation text in the SMS body to populate the sendlog for SMS
Reported By (0)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.