ZapBounce

ZapBounce and Attio

Attio's data model is unusually flexible, and that flexibility solves a problem most CRMs force you around: where a verdict belongs when a person has several addresses.

In a rigid model you attach one verdict to the record and lose the distinction. Attio lets you keep it.

One verdict per record throws away what you measured

A person with a work address that bounces and a personal address that works is not an invalid contact. A single status field on the record has to pick one, and it usually picks wrong.

The downstream effect is in sequence audiences: either you exclude a reachable person, or you include an unreachable address. Both are avoidable with a model that can hold two facts.

Attio's attributes and its API make the per-address verdict practical rather than theoretical, which is the reason to do it here rather than settle for a record-level field.

How the data moves

  1. Model the verdict against the address

    An attribute per email value rather than one per person. That keeps the information the multiple addresses existed to carry.

  2. Sync through the API on a schedule

    Attio's API returns records with all attribute values, so the job can enumerate every address per person in one pass.

  3. Build list views on the verdict attribute

    Attio views filter on attributes, so a confirmed-address view becomes the sequence source.

  4. Write the check date alongside

    A verdict without a date silently expires. The date is what lets a view exclude stale results.

Setting it up

  1. Add verdict and check-date attributes shaped to your email attribute structure.
  2. Build a scheduled sync that pulls records with every email value.
  3. Verify the distinct addresses, which collapses duplicates across records before billing.
  4. Write verdicts back against the address they belong to rather than the record.
  5. Create a list view filtered on a recent valid verdict for outbound.
  6. Create a second view for unresolvable addresses and route those to a different play.

Attio: common questions

Why attach the verdict to the address?

Because the verdict is a fact about an address, not about a person. Attaching it to the record forces a choice you do not have to make here.

How often should the sync run?

Daily for new records, quarterly for a full re-check. Outbound data decays fastest in the first few months after capture.

Does Attio verify addresses?

It records what happened to sent mail. A pre-send check is what this integration adds.

Reference

Check a Attio export today

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

Get an API keySee pricing