In the SMS message tracking data view, which values are currently represented as static GUIDs?

In the SMS message tracking data view, which values are currently represented as static GUIDs?

• A. Message IDs
• B. Phone numbers
• C. Send timestamps
• D. Code and keyword values

Answer: (D)

In the SMS message tracking data view, identifiers are used to link events to their originating elements. The values that appear as static GUIDs are the code and keyword values. These two fields serve as persistent keys for a given campaign code and its trigger keyword, so the system represents them with fixed GUIDs to ensure consistent references across all tracked messages and analytics. This stability makes it easy to join records and compare performance for the same code and keyword over time. Other fields—Message IDs, phone numbers, and send timestamps—are not GUIDs because they represent different kinds of data. Message IDs identify individual message instances and may be numeric or otherwise structured; phone numbers are actual contact numbers; send timestamps are date-time values indicating when the message was sent.

In the SMS message tracking data view, identifiers are used to link events to their originating elements. The values that appear as static GUIDs are the code and keyword values. These two fields serve as persistent keys for a given campaign code and its trigger keyword, so the system represents them with fixed GUIDs to ensure consistent references across all tracked messages and analytics. This stability makes it easy to join records and compare performance for the same code and keyword over time.

Other fields—Message IDs, phone numbers, and send timestamps—are not GUIDs because they represent different kinds of data. Message IDs identify individual message instances and may be numeric or otherwise structured; phone numbers are actual contact numbers; send timestamps are date-time values indicating when the message was sent.