{"version":"2.1.232","anchor":"message-delivery-telemetry-records-how-the-recipient-was-res","canonical_anchor":"message-delivery-telemetry-records-how-the-recipient-was-res","heading":"Message delivery telemetry records how the recipient was resolved","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/message-delivery-telemetry-records-how-the-recipient-was-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Message delivery telemetry records how the recipient was resolved\n\nMessage delivery records whether the recipient matched exactly or was already pinned.\n\n**What**\n\nThe send_message delivery event can now carry whether there was a single exact match and whether the recipient was already pinned, alongside the existing route, duration, blocked wait and via fields.\n\n**Evidence**\n\n`exact_unique`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}