ZapBounce and Pipedrive

Pipedrive lets a person hold several email addresses with labels: work, home, other. That is genuinely useful and it breaks the usual pattern of one verdict per record.

A person whose work address is dead and whose personal address works is not an invalid contact. Storing one verdict on the person loses exactly the information you need.

One person, several addresses, one field

Most integrations write a single status onto the person record, which forces a choice between the addresses and usually picks the primary one whether or not it is the live one.

Pipedrive's email sync compounds it. Mail sent through the integration goes to the primary address, so a person whose primary is dead is silently unreachable while their secondary sits there working.

Sales teams then log activities against a person nobody has actually reached, and the deal moves stages on the strength of emails that bounced.

How the data moves

  1. Verify every address on the person, including the secondary ones

    Pull all email values per person through the API. Checking only the primary is how a reachable contact gets marked dead.

  2. Write a verdict field per label

    Custom fields for the work verdict and the personal verdict, rather than one field that has to average two facts.

  3. Promote a working address to primary

    Where the primary is invalid and a secondary is valid, reorder them. Pipedrive sends to the primary, so this is the change that actually reaches the person.

  4. Filter on the verdict for email campaigns

    Pipedrive filters read custom fields, so a filter on the work verdict gives you a sending list without deleting anyone.

Setting it up

  1. Create custom person fields for the verdict on each email label you use, plus a check date.
  2. Pull persons through the API with all email values, not only the primary.
  3. Batch every distinct address for verification, which collapses the duplicates across persons automatically.
  4. Write the verdicts back to the per-label fields.
  5. Reorder addresses so a valid one is primary wherever the current primary came back invalid.
  6. Build a filter on the verdict field for any campaign you send from Pipedrive.

Pipedrive: common questions

Does Pipedrive verify email addresses?

No. It records bounces from synced mail after the fact, which is a different thing from a check before the send.

Should I delete a person whose addresses all fail?

No. The deal history is worth keeping. Mark the addresses and route the person to a phone or LinkedIn play.

How do I handle several addresses per person?

A verdict field per label. One field per person forces you to throw away the distinction that made the multiple addresses useful.

Check a Pipedrive export today

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