Updates: Check the release notes for new features and product updates.

Metrics

After your agent starts storing message hashes with Verified SMS, you can use the Verified SMS Analytics dashboard (available through the Business Communications Developer Console) to track aggregate verification outcomes of messages you sent.

Additionally, you can track successful, per-message verifications with verification receipts.

Track your own metrics

If you have different metrics preferences or require more in-depth information than is available in the dashboard, you can capture your own metrics data.

Here are some metrics that you might capture:

  • Messages hashed and sent. Capture details each time your agent hashes and sends a message.

    You might store message data already available to you, such as

    • phone number
    • destination carrier
    • postback data
  • Messages verified. Capture verification receipts to track which, and how many, messages were positively verified on user devices. Match verification receipts to messages based on postback data.

With your metrics captured, you can parse and organize them however best suits your business needs.

Improve your metrics

If you identify issues with your metrics, such as lower-than-expected verification rates, consider the following questions:

  • Can the user verify messages with Verified SMS? If a user isn't Verified SMS-enabled, their devices won't attempt to register messages, and you won't receive verification receipts for messages you send them.

    Solutions:

    • Use the Verified SMS Sample and SDK to hash and store messages. The Sample and SDK only hash and store messages for Verified SMS-enabled users.
    • Use enabledUsers.getBatchKey to confirm that users are Verified SMS-enabled before hashing, storing, and sending messages.
  • Did you hash and store message segments in addition to full message strings? It's the agent's responsibility to split message content into segments that fit fully within a single SMS message and store hashes based on those segments.

    Solution: Split messages into SMS-length segments, hash the segments, and store the segment hashes in the same API call (and therefore with the same postback data) as the main message hash.

  • Was the message content munged or transformed in transit? Was it split in an unexpected way, did it have text removed or appended, or were characters substituted?

    Solutions:

    • Use the Verified SMS Sample and SDK to hash and store messages. The Sample and SDK creates alternate messages (based on known character substitutions, message splitting patterns, and munging), hashes those alternate messages, and stores those hashes with the main message hash.
    • Identify common transformations, substitutions, message split patterns, and munging behaviors, then create message alternates based on all of the known patterns and changes, hash the alternate messages, and store those hashes in the same API call (and therefore with the same postback data) as the main message hash.