# Usage reports started showing encoded emails

**URL:** <https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291>\
**Category:** API and Webhooks\
**Created:** [July 27, 2020, 7:03am UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291 "2020-07-27T07:03:55Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nacho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nacho/32/12437_2.png) [@nacho](https://devforum.zoom.us/u/nacho)\
**Post date:** [July 27, 2020, 7:03am UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/1 "2020-07-27T07:03:55Z")

</div>

Yesterday (2020-07-26), for the first time I received a recording.complete webhook with **encoded emails**. Something like `K06knwsWtnxKwNo31kYO1zxAJZLqQ6HgqPKo3bIQVrEW.uFwIv1wbAQMD7OhX@me.com`.

I see the same behavior when I go to Active Host | Usage reports.

I found [this post](https://devforum.zoom.us/t/urgent-email-encoded-surprise-how-to-get-real-email/15021) saying that this was the default back in April, but I’ve been handling webhooks for months and this is the first time this has happened.

These are my questions:

1. Did I misconfigure something?

2. Is there a way to go back to plain emails?

3. If not, is there a way to decode the emails?

4. If not, is there a way I can go the other way and encode the email address I have so they match the encoded ones?

---

<div class="post-metadata">

**Author:** ![smachado](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@smachado](https://devforum.zoom.us/u/smachado)\
**Post date:** [July 27, 2020, 3:12pm UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/3 "2020-07-27T15:12:26Z")

</div>

We noticed the same issue- hashed email addresses in the attendance report API (/v2/report/meetings/{{webinarId}}/participants).

This is breaking our integration since we used the email to link the registered participant with the attended participant; the participantID cannot be trusted for match (sometimes it’s blank and sometimes its the attendee’s private zoom account id, which does not match participantID returned in registration response)

Can we disable this feature in the account?

---

<div class="post-metadata">

**Author:** ![nacho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nacho/32/12437_2.png) [@nacho](https://devforum.zoom.us/u/nacho)\
**Post date:** [July 28, 2020, 5:03pm UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/4 "2020-07-28T17:03:39Z")

</div>

It seems this has been fixed for new meetings. Do you see plain emails now?

I wish someone from Zoom would confirm/explain these changes. 😅

---

<div class="post-metadata">

**Author:** ![smachado](https://avatars.discourse-cdn.com/v4/letter/s/82dd89/32.png) [@smachado](https://devforum.zoom.us/u/smachado)\
**Post date:** [July 29, 2020, 3:55pm UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/5 "2020-07-29T15:55:04Z")

</div>

Thanks Nacho for updating the thread,  
Yes, attendance for meetings that have happened yesterday onwards are showing plain text emails. Attendance re-pull for the meetings that had hashed emails, still show hashed emails. Looks like content is cached and caches are not refreshed.

---

<div class="post-metadata">

**Author:** ![nacho](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nacho/32/12437_2.png) [@nacho](https://devforum.zoom.us/u/nacho)\
**Post date:** [July 29, 2020, 4:34pm UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/6 "2020-07-29T16:34:05Z")

</div>

> [@smachado](#):
>
> the meetings that had hashed emails, still show hashed emails.

That’s correct.

Several months ago, all my users appeared with `**` at the end of their names (`Jo** Smi**`) and at some point it went back to normal, but those never went away. 🤷🏻‍♂

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [July 31, 2020, 6:55pm UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/7 "2020-07-31T18:55:52Z")

</div>

Hey @nacho, @smachado,

The participant email being encoded should be fixed now.

Please let me know if you are still seeing the issue. (ZOOM-180418)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [August 7, 2020, 6:55pm UTC](https://devforum.zoom.us/t/usage-reports-started-showing-encoded-emails/25291/8 "2020-08-07T18:55:53Z")

</div>

Closed on August 7, 2020, 6:55pm UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
