- Newest
- Most votes
- Most comments
- Check the overall configuration set settings using
GetConfigurationSet
aws sesv2 get-configuration-set --configuration-set-name <name> --region eu-north-1
Verify that TrackingOptions (custom redirect domains) and other tracking-related settings are configured as intended. In particular, it is worth checking for any tracking-enabled flags at the configuration set level that are distinct from the VDM options.
- Rule out region-specific issues
eu-north-1 (Stockholm) is a relatively small region. If possible, try replicating the same configuration in a major region like us-east-1 and check whether clicks and opens are recorded there. If it works correctly in a major region, this confirms the issue is a service-side problem specific to eu-north-1, which will significantly strengthen your case when opening a support ticket.
answered 18 days ago
After suggestions, I ran both.
1. GetConfigurationSet on the eu-north-1 configuration set
$ aws sesv2 get-configuration-set --configuration-set-name ieis-tracking --region eu-north-1
{
"ConfigurationSetName": "ieis-tracking",
"ReputationOptions": {
"ReputationMetricsEnabled": true
},
"SendingOptions": {
"SendingEnabled": true
},
"Tags": [],
"VdmOptions": {
"DashboardOptions": {
"EngagementMetrics": "ENABLED"
}
}
}
No TrackingOptions block at all, custom redirect domain was never configured (I hadn't set one), and per the docs a custom domain is optional, so this is expected. VdmOptions.DashboardOptions.EngagementMetrics is confirmed ENABLED at the configuration-set level, separate from and in addition to the account-level VDM setting. Nothing hidden or misconfigured that I can see.
2. Replicated in us-east-1, and this worked out
Set up the identical pipeline in us-east-1m verified a sender identity there, created a new configuration set with the same VdmOptions.DashboardOptions.EngagementMetrics: ENABLED, and an SNS event destination with the same MatchingEventTypes (SEND, DELIVERY, OPEN, CLICK, BOUNCE, COMPLAINT, REJECT).
Sent one test email through it, opened it, clicked the one link in it. Drained the SQS queue subscribed to that SNS topic:
Send, Delivery, Open
A real Open event was recorded and published, on a configuration set that was maybe 10 minutes old at that point. That's the first time any engagement event has shown up anywhere in this whole investigation, across 6+ real opens and 2 real clicks total in eu-north-1, we got exactly zero Open/Click events, whether checked via SNS, CloudWatch, or GetMessageInsights (which reads SES's internal log directly, bypassing event destinations entirely).
So this does look like a real, region specific issue with engagement event recording/publishing in eu-north-1, not a configuration problem on my end.
This is a puzzling situation since the click tracking redirect is clearly functioning (the link was rewritten and the redirect worked), but the event isn't being recorded. Let me walk through what should be happening and potential gaps.
When click tracking is enabled, Amazon SES modifies each link in the email body to route through an SES server before forwarding to the destination. Each redirect link is unique, allowing SES to determine which recipient clicked, when they clicked, and which email they came from. The fact that your link was rewritten to r.eu-north-1.awstrack.me and successfully redirected confirms the tracking mechanism is active.
However, there's an important architectural detail: enabling open or click tracking—whether through account-level settings, configuration set settings, or per-message overrides—does NOT automatically create an event destination. Amazon SES records open and click events in VDM (Virtual Deliverability Manager), where you can review them using VDM metrics and Message Insights. But to receive these events at a destination you own (like SNS or CloudWatch), the configuration set must have an event destination that explicitly publishes open and click events.
Based on your description, you have event destinations configured with CLICK in the MatchingEventTypes, which should be sufficient. However, the fact that GetMessageInsights shows no CLICK event is particularly telling—this API reads SES's internal per-message event log directly, independent of event publishing infrastructure.
A few things to verify:
-
Click tracking must work only with HTML emails. Since you're sending multipart messages with both text and HTML, this should be fine, but confirm the recipient is viewing the HTML version where link rewriting occurs.
-
Link encoding matters. If a link isn't properly encoded in the HTML, SES won't track it even if the redirect appears to work. Ensure your links are properly URL-encoded.
-
The 250-link limit: SES can track a maximum of 250 links per email. With only one link, this shouldn't be an issue, but it's worth noting.
-
Individual recipient tracking: If you send a single message to multiple recipients, each recipient saves the same click tracking link. To track individual recipients' click activity, you need to send email to one recipient per send operation. However, this affects attribution, not whether the event is recorded at all.
-
Metrics retention: Open and click metrics are collected for 60 days after each email is sent, so timing isn't your issue here.
Given that the redirect mechanism works but no event is recorded internally, I'd recommend double-checking that engagement metrics are truly enabled at both the account level and in your configuration set's VDM options. Also verify that there are no conflicting settings that might be disabling tracking at the message level (such as TrackingConfigurationOverrides set to DISABLED in the send request itself).
Since you're using the SESv1 send_email API, also confirm whether that API version fully supports the engagement tracking features you've configured—some newer VDM features may have better support through SESv2 APIs like SendEmail.
If all settings appear correct, this may warrant opening a support case, as the disconnect between a functioning redirect and no recorded event suggests a potential service-level issue specific to your configuration or region.
Sources
TrackingConfigurationOverrides (AWS SDK for Java - 2.54.1)
TrackingConfigurationOverrides.Builder (AWS SDK for Java - 2.54.1)
Amazon SES email sending metrics FAQs - Amazon Simple Email Service
TrackingConfigurationOverrides - Amazon Simple Email Service
Amazon SES email sending metrics FAQs - Amazon Simple Email Service
answered 18 days ago
Relevant content
asked 2 years ago
asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thanks for your answer! I checked GetConfigurationSet on the eu-north-1 config set. No TrackingOptions block at all, since I never set a custom redirect domain. VdmOptions shows DashboardOptions. EngagementMetrics is ENABLED at the configuration set level. Nothing hidden or misconfigured there as far as I can tell.
I also replicated the whole setup in us-east-1. Same kind of configuration set, same engagement tracking enabled, same SNS event destination with the same event types. Sent one test email through it, opened it, clicked the link.
This time SNS actually received a real Open event, seconds after I opened the email. That's the first time any engagement event has shown up anywhere. In eu-north-1 I had over six real opens and two real clicks across multiple tests, and got zero Open or Click events every single time, checked through SNS, CloudWatch, and GetMessageInsights directly.
Click didn't show up yet in the us-east-1 test, still not sure why, might just need more time. But the Open event alone is enough to show it works in us-east-1 and does not work in eu-north-1.
So it really does look like a region specific issue on eu-north-1, not something wrong on my end. Thanks again!