Answers before you change your acquisition workflow.

ThreatIP is an Acquisition Quality Platform for B2B SaaS. It evaluates available visitor, lead, account, and campaign context, then presents quality, a verdict, and a recommended action before your team applies its own CRM or sales policy.

Acquisition volume alone does not show whether a visitor, lead, or campaign deserves attention. ThreatIP helps teams review acquisition quality before weak or ambiguous context moves downstream into CRM and sales workflows.

It means evaluating acquisition context before a record reaches the next CRM workflow. ThreatIP adds a reviewable quality decision to the handoff; it does not replace the CRM that stores records and runs downstream sales processes.

Your CRM can score and prioritize records using the data already in its workflow. ThreatIP evaluates broader acquisition context before CRM delivery—combining available visitor behavior, source and campaign context, account context, lead quality, and intent. It does not replace CRM scoring; it adds an upstream quality decision and context before sales acts.

Traditional lead scoring usually emphasizes attributes, known behaviors, and CRM workflow activity. ThreatIP looks at the broader acquisition journey before the record reaches the CRM, then makes the path explicit: Quality → Verdict → Recommended Action. The point is context before handoff, not a claim that one score is universally better.

No. Your CRM remains the system for records, pipeline, activities, sales workflows, and automation. ThreatIP adds acquisition-quality context and a decision before CRM handoff, according to the workflow your team governs.

A CRM is valuable once a record and its workflow context are available. ThreatIP helps make the acquisition context visible earlier, so teams can decide whether to Send, Review, Nurture, or Hold a record before sales attention is applied.

ThreatIP can use available visitor behavior, source and campaign context, account or company context, lead data, technical or network context, and product-usage activity. The available signals depend on what can be observed or supplied for a given visitor, lead, account, or campaign.

No. ThreatIP does not claim universal visitor or company identification. It uses account or company context when available and keeps the decision tied to the evidence available for that interaction. Identification and quality confidence vary with the data and context provided.

ThreatIP works with the context available for the interaction rather than assuming a complete identity. When account or identity information is missing, the resulting quality view and confidence should be interpreted within those limits.

A low-intent or low-quality lead does not have to be treated like a sales-ready record. ThreatIP can surface a verdict and recommended action such as Send, Review, Nurture, or Hold; your team owns policy and decides how those actions map to CRM workflows.

Quality summarizes the evaluation of available context. The Verdict expresses the decision state, while Recommended Action makes the next workflow step explicit. Reasons and context stay close to the decision so your team can review it before applying policy.

The current workflow language includes Send, Review, Nurture, and Hold. These are recommendations for the workflow your team governs; they do not delete records or override your organization’s CRM, legal, or customer policies.

Yes. ThreatIP is designed to compare campaign and source context with the quality of the acquisition that follows, so teams can look beyond conversion counts when reviewing demand.

Conversion volume shows how many actions occurred. Campaign quality adds context about whether the resulting visitors, leads, or records appear useful for the workflow your team is trying to create.

Available source and campaign context can be part of the broader acquisition evaluation. The effect depends on the data available and the routing or review policy your team configures.

ThreatIP currently supports HubSpot, Pipedrive, and GoHighLevel workflow destinations, along with Webhooks for supported automation paths. Exact field mapping and routing behavior depend on your configuration and policy.

ThreatIP is intended to carry acquisition-quality context such as the quality view, verdict, reasons, and recommended action into a supported workflow. Exact fields and routing behavior depend on your configuration.

Yes. Webhooks are a supported destination for carrying decision context into an automation system your team governs. Use your configuration and workflow details to confirm the exact payload and behavior for your use case.

The free trial lasts 14 days.

No credit card is required to start the trial. There is no automatic charge at trial end, and it does not automatically convert to a paid subscription.

The published trial offer includes 1 domain, 10,000 events, 1 CRM destination, and 1 Acquisition Quality Report.

When your 14-day free trial ends, paid features are restricted until you choose a plan. Your trial data is preserved, and you are only charged after you actively select a paid plan and complete checkout.

The setup path is to verify your email, add one domain, and install the tracker. Exact setup time depends on your website, acquisition workflow, and review policy; ThreatIP does not promise a guaranteed setup time.

The published plan limits are 1 domain on Starter, 3 on Growth, and 10 on Scale. Workspace behavior and any custom requirements should be confirmed with the ThreatIP team rather than inferred from these domain limits.

Starter, Growth, and Scale differ by domains, event volume, and the published workflow and support capabilities shown on the pricing page. Review the current plan details before choosing a package.

ThreatIP may process account and business contact details, workspace configuration, campaign context, lead data, product-usage activity, and technical logs to operate the service. The available acquisition signals vary by interaction and setup.

The published Security & Trust page describes organization-scoped workflows, access controls, encrypted transport, monitoring, and security-minded development practices as part of its safeguards.

Retention depends on the selected plan and data type. Customer configuration and routing policies are retained for the active subscription, while event and analytics retention follows the selected plan and the deletion lifecycle in the Data Retention Policy.

Review the Security & Trust page and the published Privacy, Terms, Cookie Policy, and Data Retention Policy pages. Questions about security or privacy can be sent through the published ThreatIP contact path.