You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sendgrid just sent us an email about a change to their webhook and am curious if/how this will impact our plugin to Rock. I've copied the email we received from them below as a reference.
We’re emailing to inform you of an upcoming change to SendGrid’s Event Webhook. In order to optimize the efficiency of our infrastructure, we’ll be updating the length and format specification of the sg_event_id, part of the JSON object included with each webhook post. This identifier is used by some customers to identify unique events received by the webhook to deduplicate them.
What exactly is changing?
We currently specify the sg_event_id length to either 22 or 48 characters and decode to UUIDv4. Starting on January 17th, 2019, the sg_event_id will be limited to 100 characters, will be URL safe, and will no longer have a specified format.
How will this change impact me?
If you've set up local restrictions on the field length or format for the sg_event_id in your database for webhook events, this change could break your webhook integration. We recommend removing or adjusting your local restrictions to account for up to 100 characters for the sg_event_id. If you do not have local restrictions on the field length or format for the sg_event_id, this change should not impact you.
Please feel free to reach out to our Support team if you have any additional questions.
The text was updated successfully, but these errors were encountered:
The Sendgrid click tracking in Rock is no longer working properly-- it does not show the address that is clicked. Not sure if this related or if there is a needed update to the plugin.
Sendgrid just sent us an email about a change to their webhook and am curious if/how this will impact our plugin to Rock. I've copied the email we received from them below as a reference.
We’re emailing to inform you of an upcoming change to SendGrid’s Event Webhook. In order to optimize the efficiency of our infrastructure, we’ll be updating the length and format specification of the sg_event_id, part of the JSON object included with each webhook post. This identifier is used by some customers to identify unique events received by the webhook to deduplicate them.
What exactly is changing?
We currently specify the sg_event_id length to either 22 or 48 characters and decode to UUIDv4. Starting on January 17th, 2019, the sg_event_id will be limited to 100 characters, will be URL safe, and will no longer have a specified format.
How will this change impact me?
If you've set up local restrictions on the field length or format for the sg_event_id in your database for webhook events, this change could break your webhook integration. We recommend removing or adjusting your local restrictions to account for up to 100 characters for the sg_event_id. If you do not have local restrictions on the field length or format for the sg_event_id, this change should not impact you.
Please feel free to reach out to our Support team if you have any additional questions.
The text was updated successfully, but these errors were encountered: