Who should shortlist Incognia?
App-led businesses where device integrity, trusted locations and location-spoofing evidence affect the decision.
How the product fits the workflow
Incognia documents SDK and API integration for device and location observations. Its portfolio also includes Browser ID, so evaluate web and native mobile products separately.
What the business receives
Risk assessment and supporting device or location evidence, available through the relevant API and dashboards.
Strength and tradeoff
Why it belongs on the shortlist
Location and device context can address business questions that a generic IP flag does not resolve.
What to check first
Confirm collection requirements, permission behavior and platform coverage. The exact quote depends on the product and usage model.
Access, pricing and the unit
Request a tailored demonstration. Quote based on scope and volume. Billing unit: Confirm MAU/API and chosen scope.
Use the vendor’s current plan and product scope when estimating cost. Confirm supported platforms, included output, request counting and operational support before starting a pilot.
Editorial fit breakdown
Strong identity context fits mobile and location-sensitive journeys; a web-only business may place different weights on those strengths.
| Category | Weight | Grade |
|---|---|---|
| Account abuse fit | 25 percent | 4.6 / 5 |
| Identity context | 15 percent | 4.8 / 5 |
| Decision output | 15 percent | 4.5 / 5 |
| Implementation | 15 percent | 4.0 / 5 |
| Commercial access | 10 percent | 3.0 / 5 |
| Operational control | 10 percent | 4.3 / 5 |
| Cross-journey coverage | 10 percent | 3.6 / 5 |
Weighted grades produce 8.5 out of 10. Read the complete methodology and 28 lenses for the definition of the scale.
Run a useful first evaluation
Compare ordinary travel, a new legitimate device, denied optional permissions and controlled location anomalies. Keep native and web results in separate cohorts.
Record the protected action, event reference, proposed response and later outcome. Include ordinary returning customers in the same cohort. Inspect unavailable results and a support-led reversal before moving from observation to enforcement.
Use the controlled rollout guide to assign owners and release gates, and the API integration checklist for event binding and safe retries.
Official sources
- Use cases and integration · reviewed October 21, 2026
- Pricing scope · reviewed October 21, 2026
