Signal
Source, landing page, session, form, and account context where available.
ACQUISITION QUALITY REVIEW
See Why a Lead Is Ready - Before It Reaches CRM
A ThreatIP review brings acquisition context, quality, reasons, verdict, and recommended action into one inspectable decision for growth, sales, and RevOps.
Illustrative product workflow. Validate the decision on your own acquisition data.
ThreatIP quality reviewIllustrative workflow
SIGNALSource + form contextAvailable context
QUALITYNeeds reviewQuality view
VERDICTNeeds ReviewDecision state
ACTIONReviewRecommended next step
Available context flows into a quality decision and recommended action.
One review, one decision
The review keeps the acquisition story next to the record.
A lead is easier to handle when the team can see how it arrived, what context is available, what the quality view says, and what should happen next.
Quality
A readable view of the evidence and its confidence, not a black-box label.
Verdict + action
Send, Review, Nurture, or Hold with the reasons close at hand.
Review context
Inspect the parts of acquisition that shape the handoff.
The same review pattern can bring visitor, lead, and campaign context into one place without pretending every signal is available for every record.
01 / Visitor
Where did the visit come from?
Review acquisition source, landing page, and available session context.
02 / Lead
What arrived in the form?
Add lead details, business-domain context, and available engagement signals.
03 / Campaign
Which pattern produced it?
Keep campaign, UTM, source, and landing-page context visible.
04 / Decision
What should happen next?
Make the verdict and recommended action clear before CRM routing or sales attention.
Real product evidence
Give the team a review surface they can read together.
Use existing ThreatIP product views to ground the conversation in real interface patterns and review context.
Acquisition reviewIllustrative product view
Reasons
- New domain First interaction
- Low session depth 1 page viewed
- No company match Domain not identified
- Form submitted quickly 18s on page
Activity context
Sourcegoogle.comCampaignQ3_Growth_SearchLanding page/pricingSession time00:00:18Returning visitorNo
Confidence 68%
Review before sending to CRM
Illustrative product view. Example values are not customer results.
Reasons
Readable context
Keep the evidence that shaped the review close to the decision.
Verdict
Trusted / Needs Review / Low Intent / Low Quality
Use the approved quality states, then pair them with a recommended action.
Action
Recommended next step
Support the next workflow without claiming autonomous policy ownership.
Verdict and recommendation
A review should make the next action easier to explain.
The decision states are recommendations and context. The team decides how they map to routing, nurture, sales attention, or monitoring.
Send
Available evidence supports moving the record to the next workflow.
Review
Context is incomplete or unusual enough to deserve human attention.
Nurture
The record may be useful, but it is not ready for immediate sales attention.
Hold
The available acquisition quality is not strong enough for the next handoff.
Questions teams ask
Make the quality decision easier to understand.
Clear answers help growth, sales, RevOps, and founders decide whether this workflow fits their current acquisition path.
What does an acquisition-quality review contain?
It brings available acquisition signals, quality context, reasons, a verdict, and a recommended action into one reviewable decision.
Does the review require CRM access?
The marketing site describes the review concept and product workflow. Teams can start by evaluating their own acquisition path before deciding how to connect downstream systems.
Can a review include campaign context?
Yes, where available. Campaign, source, UTM, landing-page, visitor, and lead context can help explain how the record entered the funnel.
What are the possible outcomes?
ThreatIP uses Send, Review, Nurture, and Hold as clear decision outcomes for the next workflow.
What does the product view show?
It shows how available acquisition context can be brought together around a quality review and its next action.
Continue the cluster
Keep exploring the acquisition-quality workflow.
Use the next page to move from the category question to the product layer or business decision that matters next.
Next step
Start with the acquisition data your team already has.
Evaluate the quality context before the next record reaches CRM, sales, or a campaign decision.
Start Free Trial