ZapBounce

ZapBounce and Capsule CRM

Capsule leans on tags rather than an elaborate custom-field model. That suits verification well: a small set of tags carries the verdict and every list filter can read them.

The discipline is keeping the tag set small and mutually exclusive, because a contact carrying two contradictory verdict tags is worse than one carrying none.

Tags drift when nothing enforces exclusivity

Capsule will happily let a contact hold both a valid tag and an invalid one, applied months apart by two different processes. Any filter reading those tags then produces a list nobody can explain.

The fix is to remove the previous verdict tag in the same operation that applies the new one, which the API supports and a manual process does not reliably do.

Capsule also has no native bounce handling to fall back on, so the tags are the only record of address health in the system.

How the data moves

  1. Use one tag per verdict, applied exclusively

    Four tags, one per result value, and applying one removes the others. That exclusivity is the whole design and it has to be enforced in code. Role and disposable are separate flags on the response, so they get their own tags outside the exclusive set.

  2. Add a custom field for the check date

    Tags carry no timestamp. Without the date, a verdict from last year looks exactly like one from this morning.

  3. Export and verify through the API

    Capsule's API returns parties with their tags, so the write-back can remove the old tag and add the new one in one operation.

  4. Filter campaign lists on the tag

    A saved list filtered on the valid tag becomes the sending audience, updating as tags change.

Setting it up

  1. Create four tags, one per result (valid, invalid, catch_all, unknown), with a shared prefix so they sort together, plus one each for the role and disposable flags.
  2. Add a custom field for the check date, because tags do not carry one.
  3. Pull parties through the Capsule API with their existing tags.
  4. Verify the addresses and write back, removing any previous verdict tag as you apply the new one.
  5. Build a saved list filtered on the valid tag for campaigns.
  6. Re-run quarterly, so the check date never gets far out of range.

Capsule CRM: common questions

Why tags rather than a custom field?

Because Capsule's filtering is built around tags and everything in the interface can read them. Add the check date as a field, since tags cannot carry one.

What if a contact ends up with two verdict tags?

Any filter reading them becomes unreliable. Enforce exclusivity in the write-back rather than trusting a manual process.

Does Capsule track bounces?

Not natively. The tags are your only record of address health in the system.

Reference

Check a Capsule CRM export today

100 free checks a month, no card. Unknown results and duplicates are never billed.

Get an API keySee pricing