Constant Contact list cleanup and suppression workspace

Build me a list hygiene workspace for Constant Contact that I open about once a month to clean up our audience. Constant Contact has no built in list cleaning tools, so this app is the surface where I review who should be suppressed and then act on it in bulk. It is a recurring ritual, not a one off cleanup, so it should be fast to reopen and should always show the current state of the audience.

The app opens on a single review screen with four buckets, each one a section with a count at the top so I can see the size of the problem before I touch anything. Build the buckets like this. Hard bounces: enumerate recent campaigns with Get Email Campaign Summaries, resolve their activities with Get Campaign Activity, then pull Get Campaign Activity Tracking Bounces for each and show the bounce reason alongside each contact. Dormant contacts: start from List Contacts and check each one with Get Contact Activity Summary over the last 90 days, keeping the contacts with no opens in that window. Recent unsubscribes: pull Get Campaign Activity Tracking Opt-outs across those same recent campaigns. Over-listed contacts: use List Contacts with list_memberships included and flag anyone sitting on an unusually high number of lists, defaulting to more than ten, and note that Constant Contact caps a contact at fifty lists.

Every bucket renders as a checkbox table with columns for email, name, lists, tags, and last engagement date, plus select all and a live count of the current selection. Populate the filter controls above the tables from List Contacts, List Contact Lists, List Segments, and List Tags so I can narrow a bucket to a specific list, segment, or tag before I start selecting.

With rows selected I can apply three bulk actions. Move to suppression list, which uses Add List Memberships (Bulk) against a dedicated suppression list, creating it with Create Contact List the first time if it does not already exist. Pull off active lists, which uses Remove List Memberships (Bulk) for the lists I choose. Retag, which uses Update Contact to apply a review tag such as needs review or re-engage later.

Two rules matter more than anything else and must be baked into the handlers, not just the interface. First, never hard delete anyone. Cleanup always moves contacts to the suppression list before removing them from active lists, in that order, so every decision stays reversible. If the suppression add fails, do not run the removal. Second, any action touching more than one hundred contacts shows a confirmation dialog stating the exact count, the target lists, and the bucket the contacts came from, and only proceeds when I confirm.

The bulk membership endpoints run asynchronously and return 202 Accepted with an activity id, so do not assume the work finished. Poll Get Activity Status until the state is completed and show real progress in the interface, then refresh the affected bucket counts. Surface any per contact failures the activity reports rather than silently swallowing them.

Every bulk action appends an audit row to a Google Sheet using Append Values so there is a paper trail of what we cleaned. Each row records the contact email, which list or lists they were removed from, which bucket they came from, the action taken, who ran it, and the timestamp. Write the audit rows after the Constant Contact activity completes so the log reflects what actually happened, and keep the sheet append non blocking for the user so a logging hiccup never leaves the audience half cleaned without a record.

A few implementation details to respect. Contact subresources like list_memberships and taggings are excluded by default, so request them with the include query parameter when listing contacts. Update Contact is a full replacement, so fetch the contact first, merge the new tag into its existing fields, and send the complete object back rather than a partial patch. Contact listing is cursor paginated, so follow the next link to build a complete bucket. Constant Contact allows roughly four requests per second and ten thousand per day, so batch and throttle the per contact activity lookups and cache bucket results for the session instead of refetching on every render.