Two levels of idempotency. The provider's own event id makes a webhook redelivery a complete no-op. Human identity — normalised phone or lowercased email — means the same person filling three forms produces one card with three sets of answers merged in, existing values winning because they were there first.
Also called: duplicate leads from forms · they filled out two forms · one person two submissions
- 1A recorded provider event id short-circuits the whole ingestion
- 2Phone matching uses the last ten digits; email matching is trimmed and lowercased
- 3On a match, answers and attribution merge into the existing card and the delivery is logged as merged
- 4A delivery with no name, email or phone is rejected with the reason recorded, not silently dropped
A customer who filled the form twice — once from an ad, once from the website a week later — became two cards, so two reps rang the same person and neither knew what the other had been told. A second submission from the same phone or email now adds to the card that already exists. Duplicate protection works at two levels: a redelivered notification from the provider changes nothing, and the same human never grows a second card.
- Webhook redeliveries minting duplicate cards
- One person filling several forms becoming several leads
- Context split across duplicate records
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →