I would like to formally raise an enhancement request related to the current behavior of the ECOSTRING field during SMS campaign execution via UBX.

What is ECOSTRING?

ECOSTRING is a field in the SMS database used for the Published to Exchange process. It contains a unique value for each campaign and each customer, enabling precise identification and tracking of communication data across systems.

Issue Summary:

Currently, the ECOSTRING value is not retained at the time of the SMS send event. Instead, the value that is logged reflects the most recent value available at the time of delivery. This design stems from the original UBX configuration, where it was assumed that messages (Email/SMS/Push) would be sent and delivered immediately, making the send and delivery events practically identical.

Business Impact:

This behavior causes potential data mismatches and reporting inconsistencies. For example:

If there is a delay in delivery, and another campaign is triggered shortly after with a different ECOSTRING value for the same customer, the delivery event may log the updated ECOSTRING instead of the one relevant to the original send.

This affects data accuracy, interferes with correct attribution, and can lead to confusion during audits or performance tracking.

Enhancement Request:

We request that UBX be enhanced to capture and retain the ECOSTRING value at the time of the SMS send event, so that this value remains consistent through to the delivery stage—even if there are delays or subsequent updates.

Implementing this change will ensure data consistency, improve integration with downstream systems, and maintain the integrity of campaign analytics.