Status of sg_event_id #2667
Comments
Hi @emiel, I added this to our documentation backlog to clarify the different value types. In the meantime, if you haven't figured out your issue already, you can reach out to our support team through https://support.sendgrid.com and they should be able to help you more quickly than we can. |
Hello @ksigler7. Thanks for responding. Through observation and poking around we were able to decode the various forms of the sg_event_id. Though we understand the implementation the engineering trade-offs are a bit puzzling. :) It was an interesting exercise and I've gone ahead and documented what we learned in a blog post. https://emiel.github.io/decoding-the-sendgrid-event-id.html Feel free to pass it along and give feedback. |
@emiel wow, very cool. thanks for sharing this with me! |
@ksigler7 I would like to work on this issue. Should I add the type of |
@akshat14714 thanks for your additions! |
@ksigler7 should this be closed? I see that the PR was merged, but the ticket was reopened? Any additional information on this? |
@duncanleung - I've dug into this and I have no idea why I reopened it.... :( I am going Hacktoberfest crazy |
We are using the event webhook in our system and using
sg_event_id
to deduplicate events. We are curious what the format of this value is. From what I've found so far it is a base64 encoded UUID value and I'm able to decode it for the most part.My issue is that it seems there are various forms in use. For click/open events they are all base64 UUIDs. A couple of examples are:
Though for spamreport events the values are shorter. For example:
I'm unable to decode this value and must assume it is a different format.
Could someone please shed some light on the difference and hopefully put up some documentation.
Thanks!
The text was updated successfully, but these errors were encountered: