What “deduplicated” means in Feediqo
Deduplication is applied when records are assembled for display and export. A normalized LinkedIn profile, person identity or store domain prevents the same detected identity from appearing twice in the same result set. Campaign recipients are additionally deduplicated by normalized email address.
The published coverage number remains a count of connected source records, not a claim of 208 million globally unique people. Different employees at the same company are intentionally separate leads.
What “validated” means in Feediqo
Feediqo validates source configuration, record keys, supported data types, URLs and field mappings. This protects filters and exports from malformed source rows. Verification of a named person is distinct from live mailbox deliverability or confirmation that the person still holds the listed role. An available email is shown as a contact route; Feediqo does not attach a live mailbox-deliverability timestamp unless such evidence exists.
Estimates are not audited figures
Traffic and revenue are source estimates. Compare values in the same currency and context; do not describe them as a company’s actual sales or purchasing budget.
How to read store contact coverage
Some stores have several public business contact addresses; others have none. Availability varies by store and may change when a business updates its website or the directory is updated.
An observation date describes the available source context. It does not mean every field or mailbox was checked on that date.
Before you use a prospect list
- Confirm the business, website and person’s current role.
- Check whether the contact route fits your purpose.
- Review the address type and contact context before sending.
- Apply your suppression records and respect opt-outs.
- Check the rules and permissions relevant to your campaign and recipients.
Read the full lead contact review checklist →
Report an incorrect record or request removal
Contact contact@feediqo.com with the relevant domain or profile and the correction requested. Do not send passwords or sensitive documents. See our privacy policy for data requests.