boulder/email
Samantha Frank a3eb6aa043
email-exporter: Use the upsert-by-email endpoint (#8297)
Prevent duplicate contacts in Pardot by using the upsert-by-email
endpoint.

Some background: In
https://github.com/letsencrypt/boulder/pull/7998#discussion_r1949702280
(later superseded by https://github.com/letsencrypt/boulder/pull/8016),
we discussed using this endpoint. It turns out I was wrong about Pardot
storing Prospects by email address; you can have multiple Prospects with
the same email. While subscribed newsletters won’t be sent to both
contacts, the onboarding process doesn’t deduplicate in this way and
will send to an email address each time it’s added, resulting in
duplicate onboarding messages.
2025-07-07 16:55:30 -07:00
..
proto Update protoc-gen-go to match updated grpc libraries (#8151) 2025-05-01 17:14:57 -07:00
cache.go email-exporter: Don't waste limited attempts on cached entries (#8262) 2025-06-23 14:55:53 -07:00
exporter.go email-exporter: Don't waste limited attempts on cached entries (#8262) 2025-06-23 14:55:53 -07:00
exporter_test.go email-exporter: Don't waste limited attempts on cached entries (#8262) 2025-06-23 14:55:53 -07:00
pardot.go email-exporter: Use the upsert-by-email endpoint (#8297) 2025-07-07 16:55:30 -07:00
pardot_test.go email-exporter: Don't waste limited attempts on cached entries (#8262) 2025-06-23 14:55:53 -07:00