Verified should mean auditable.
Every content syndication vendor claims their leads are “high quality.” Almost none will show you how they know. OpGen Verified is a published verification methodology, a published quality threshold, and a published replacement policy — so you can hold us to the same standard we hold ourselves to.
Why we published this
The content syndication category has a lead-quality trust problem. Third-party audits, marketer surveys, and Forrester’s Say Goodbye to MQLs thesis all point at the same underlying issue: buyers can’t verify what they’re being sold.
Most vendor “quality guarantees” are unverifiable claims — recycled contacts labeled “opt-in,” bot-generated form fills labeled “engagement,” aging records labeled “current.” When a client challenges the numbers, the vendor points to a private methodology and asks the client to trust it.
We think that’s the wrong model. So we published ours.
The four Verified checks
Every lead OpGen delivers under the Verified Standard passes four independent verification checks before it reaches your CRM. Each check has a written definition, a measurable threshold, and a documented failure trigger.
Identity Verification
What we check: The contact’s name, business email, company, job title, and company domain are all real, current, and consistent with each other.
How we check it:
- Email deliverability validated via real-time SMTP verification (no catch-all acceptance)
- Company domain confirmed active with a matching corporate email suffix
- Job title cross-referenced against publicly available employment records (LinkedIn, corporate directories, or equivalent) within the last 12 months
- Duplicate detection against your CRM’s existing records and against leads delivered in the trailing 90 days
Fails if: Email bounces, corporate domain doesn’t match, title cannot be corroborated, or the contact has been delivered to this program in the last 90 days.
Evidence recorded per lead: Verification tool and version, timestamp (UTC), pass/fail flag, and the specific data field that resolved the check.
Fit Verification
What we check: The contact matches the ICP you defined at kickoff — company size, industry, geography, role level, and any custom qualifiers.
How we check it:
- Firmographic match to your written ICP definition (employee count, revenue band, industry classification)
- Geographic match to your named target regions
- Role and seniority match to your named target personas
- Any custom qualifier (technology stack, buying trigger, department) explicitly validated
Fails if: The contact falls outside any single kickoff-defined ICP dimension without documented client approval to accept the exception.
Evidence recorded per lead: Firmographic source, matched ICP dimensions, timestamp (UTC), and any custom qualifier evidence.
Engagement Verification
What we check: The contact actually engaged with your content — not a passive form fill, not a bot, not a co-registration.
How we check it:
- Verified content download or asset access, timestamped and logged
- Session duration and page-behavior signals above the fraud-detection threshold
- IP and device fingerprinting against known bot and click-farm signatures
- Human review sampling on higher tiers (see Verification tiers below)
Fails if: Engagement signals suggest bot activity, co-registration without content interaction, or the contact cannot recall the asset when contacted (spot-check applied on Verified HQL and 100% on Verified Appointment).
Evidence recorded per lead: Content asset identifier, engagement timestamp (UTC), ruleset version applied, and reviewer initials where human QA applied.
Consent Verification
What we check: The contact opted into being contacted about your topic and product category, in a form that would survive an audit.
How we check it:
- Explicit opt-in captured at the point of content download, with topic and sender named
- Consent record retained with timestamp, form language, and source
- Compliance with GDPR, CAN-SPAM, CASL, CCPA, and LGPD depending on the contact’s jurisdiction
- Documented right of the contact to withdraw consent, honored within 72 hours
Fails if: Consent was implied rather than explicit, the opt-in form language did not name the client or category, or a valid unsubscribe request has been received and not honored.
Evidence recorded per lead: Consent form identifier, jurisdiction, opt-in language snapshot, timestamp (UTC).
Verification tiers
Verification depth scales with the tier you buy. This is intentional: it lets us price accurately and it lets you match verification intensity to lead value.
| Tier | Identity | Fit | Engagement | Consent | Human QA sample rate |
|---|---|---|---|---|---|
Verified CPL standard content syndication lead | Automated, 100% | Automated, 100% | Automated, 100% | Automated, 100% | Random 5% audit |
Verified HQL higher-intent qualified lead | Automated, 100% | Automated + BANT check, 100% | Automated + engagement scoring, 100% | Automated, 100% | Human QA on 25% |
Verified Appointment BANT-qualified meeting | Automated, 100% | Full BANT validation, 100% | Human confirmation of intent, 100% | Automated + explicit meeting opt-in, 100% | Human QA on 100% |
Every tier passes all four checks. The tier defines how many of the checks include human review vs. automated verification alone, and what the qualification bar looks like beyond ICP fit.
What happens when a lead fails
Failed leads never reach your CRM. If a lead fails any of the four checks after delivery — because a signal we couldn’t catch pre-delivery surfaces later — OpGen replaces it under the published Replacement Policy at no additional cost, within ten business days of the review decision on your dispute.
You don’t have to prove the failure. You dispute the lead by referencing its Verified Lead ID; we review the same records we used to verify it; and if any of the four checks does not hold, the lead is replaced. Our commitment: more than 3% dispute rate on any campaign triggers a program-level root-cause review at our expense; more than 5% cumulative unlocks client-elected remedies including program exit.
What you can see (the Verified transparency layer)
We’re a specialist agency, not a SaaS platform. Rather than build a live dashboard product, we commit to the same transparency in a format that fits how our clients actually consume audit information. Every Verified program includes three artifacts:
The Verified Program Report
A standardized PDF delivered every two weeks showing every lead delivered on the program, per-check verification status, program-level pass rates, dispute activity against the SLA thresholds, publisher performance, and an SLA compliance summary. Cadence upgrades to weekly by month 6.
The Verified Audit Export
A per-lead CSV or JSON download containing the full verification evidence trail for every delivered lead: which checks ran, when, using what tool, and with what result. Refreshed at least twice weekly. Available on-demand from your Client Portal, by email request within one business day, or on an automated recurring delivery to your SFTP or inbox.
The Client Portal
A shared workspace hosted per program containing the running archive of every Program Report ever delivered, the current Audit Export, your SOW ICP definitions of record, the dispute submission form and status log, and the pinned methodology and SLA versions in effect at your SOW date.
Our transparency roadmap is published, dated, and versioned at /verified/roadmap. Weekly report cadence in the next six months. An OpGen-branded client portal within nine months. Real-time verification status per lead in the twelve-to-eighteen-month window. Every commitment in the current methodology and SLA is live today — the roadmap is about how we upgrade the format, not about future promises replacing current commitments.
If you can’t see how a lead was verified, we didn’t really verify it. Verified means auditable — on your schedule, at whatever depth of evidence you need.
What OpGen Verified is not
We believe in transparency about limits too:
We are not a first-party publisher.
OpGen orchestrates syndication across preferred publisher partners and does not own a proprietary audience. We think that’s an advantage — we have no incentive to force you onto a channel that isn’t working — but if you specifically need first-party-only delivery, we’ll tell you upfront.
We do not use recycled or aggregated third-party contact lists.
All leads come from opted-in content engagement on verified publisher properties, and every contact record is validated at delivery, not licensed from a data broker.
We do not offer a live self-serve dashboard product.
Our transparency runs on the Program Report, the Audit Export, and the Client Portal — all documented above, all delivered on published cadence. If a real-time self-serve UI is a hard procurement requirement, we’ll tell you upfront and we’ll help you evaluate whether a platform vendor is a better fit.
We do not guarantee closed-won revenue.
No syndication vendor honestly can. What we guarantee is that every lead we deliver meets the four Verified checks, and that failures are replaced. What you do with the leads downstream — nurture cadence, sales follow-up, offer strength — is where the pipeline math actually gets decided, and we’ll help you build that system, not just deliver into it.
Why this is different
Most vendor quality claims are private. OpGen Verified is public — the methodology above, the SLAs in the Replacement Policy, the reporting cadence, and the transparency roadmap. If we ever change the methodology, we’ll say so and date the change. You can audit us against ourselves.
That’s the standard.
Frequently asked questions
Why isn’t there a live dashboard?
Because we chose to be honest about what we are. OpGen is a specialist agency, not a SaaS platform. Building a live dashboard product would take engineering resources we’d rather put into verification quality, publisher relationships, and named-team service. Instead, we commit to the same transparency in a different format: a bi-weekly written Program Report, an on-demand per-lead Audit Export, and a shared Client Portal workspace with everything archived. Every field a live dashboard would show is available to you, in writing, on cadence, in a format any procurement team can audit. Our transparency roadmap describes when real dashboard capability arrives over time.
How do I know the four checks are actually running?
Look at the Audit Export. Every delivered lead has a row with the timestamp, tool, and reviewer initials (where applicable) for each of the four checks. If we’re claiming a check ran, the export shows when and how. If we can’t show it, you get the replacement under the SLA.
What if my ICP changes mid-program?
Updated ICP definitions are recorded in your SOW addendum and reflected in your next Program Report’s ICP Appendix. All leads delivered after the addendum effective date are verified against the new ICP. Prior deliveries are governed by the ICP in effect on their delivery date.
Can I audit against a specific lead?
Yes. Every delivered lead has a Verified Lead ID. Reference the ID in a dispute or an audit request and we respond with the full evidence trail — the same records we used to verify it — within five business days per the SLA.
Where is the methodology version I bought under?
Your SOW references the methodology version in effect on the execution date. That version is pinned to your Portal workspace. Change history is public at /verified/history. If we update the methodology, active clients receive 30 days’ written notice before it takes effect on their program, and clients may elect to remain on the prior version through the current SOW term.
Ready to see it in action?
Request a sample Verified Program Report, or schedule a program design call.