Announcement

Incognia Raises $31 million in Series B!

How to Get the Most Out of your Incognia Proof of Value (POV)

So you're interested in an Incognia Proof of Value (POV), but want to learn more about what it entails and what benefits you might see from it?

Our POV helps potential customers understand the impact and value of our unique signal for your business’s use cases. Unlike traditional Proof of Concept (POC) trials, our POV allows you to test the Incognia solution in production, analyze its performance, and measure potential ROI without disrupting your existing processes.

Our POV process includes clear success goals, custom integration support, technical assistance, and detailed analysis reports. It's a straightforward way to evaluate Incognia's in-production value and determine if it's the right solution for your needs.

Sound interesting? Let's dive into some frequently asked questions to help you learn more about our POV process.

Why do you call it a POV instead of a POC?

Usually, a proof of concept (POC) trial is performed in a customer’s pre-production environment, where they can try out the solution’s technical capabilities and features on a small scale with test users and devices.

While this pre-production POC testing allows customers to evaluate how individual solution capabilities work, it doesn’t show the true value the solution would have at scale, how you would integrate it with your solution stack and decision off the data, or what impact you could expect once it was integrated.

So in Incognia’s POV process, we actually allow you to test out our solution in production in a monitor-only mode. We collect location and device data via our SDK to let you simulate in-production assessments without impacting the user experience.

This enables you to analyze its performance and measure the potential ROI within your application at scale, without having to act on what it’s telling you.

Do you have other questions? Ask Mike anything.

What is the main goal of a POV?

The overall goal of our POV process is to enable customers to clearly understand the value of Incognia’s solution within the context of their mobile app and user base without disrupting existing UX, solution flows, and technology stacks.

Our POV process has proven to be very effective at helping companies measure Incognia’s in-production value.

Do you have other questions? Ask Mike anything.

What specific use cases can an Incognia POV address?

1. Food Delivery

  • Driver fraud
  • GPS spoofing
  • Promotion/coupon abuse
  • Payment fraud

2. Financial Services

  • New account fraud
  • Identity fraud
  • Account takeover

3. iGaming

  • Geolocation compliance
  • Payment fraud
  • Account takeover
  • Player collusion

4. Marketplaces

  • Fake accounts
  • Promotion abuse
  • Listing verification
  • False advertising
  • Collusion
  • Account takeover
  • CNP fraud

Do you have other questions? Ask Mike anything.

What should we expect to get out of the POV? Business benefits?

Our POV demonstrates Incognia’s capabilities to combat fraud/abuse within your given use case and allows you to review assessments for comparison against internal decisioning.

At the conclusion of the POV, Incognia will provide a report and data set with all cumulative results that allows you to analyze value provided by the Incognia solution.

Do you have other questions? Ask Mike anything.

How long is Incognia’s POV?

Our POVs typically run for about 30 days in order to provide enough time for Incognia to independently analyze and measure the scale and impact of the relevant risk scenarios.

Do you have other questions? Ask Mike anything.

How quickly should we expect to see results?

We’ll share results with you early and often. Over the duration of the POV, Incognia will provide weekly reports detailing our analysis and findings. This includes reviewing assessments in collaboration with you to compare with internal decisioning for evaluation and provide feedback.

At the conclusion of the POV, we’ll share a data set containing all risk decisions made during the POV.

Do you have other questions? Ask Mike anything.

Do we need to integrate the Incognia SDK and APIs to run a POV?

In order to run a POV, Incognia requires an SDK-only integration, which collects data over the course of the POV.

Incognia’s API is not required for a POV as no real-time customer decisions are made during this period.

Do you have other questions? Ask Mike anything.

How much integration time is necessary to get started?

Incognia’s technical implementation typically requires less than 1 day of engineering time for the customer.

The effort required to implement Incognia for a POV is as follows:

  1. A one (1) hour SDK integration planning meeting between Incognia and the customer's Product & Engineering Teams.

  2. Once Incognia's SDK integration is slotted into the customer’s Engineering sprint schedule, two to three (2-3) hours of an Android and/or iOS developer’s time on the customer side is required to integrate Incognia's mobile SDK into the customer’s mobile app(s).

  3. A one (1) hour SDK integration validation call between Incognia and the customer's mobile developer(s) to technically validate the successful integration of Incognia's SDK, and confirm that Incognia is receiving the necessary user data to support Incognia's POV performance analysis and reporting.

  4. The POV officially kicks off when the customer rolls out Incognia's SDK to all (or an agreed upon subset) of the customer's users.

Do you have other questions? Ask Mike anything.

Should we run the POV with all users or a subset?

We recommend running the POV for all users to maximize the richness of the data and findings you receive during the POV. However, Incognia can still be effective on a subset of users if you choose to test on a smaller audience.

Do you have other questions? Ask Mike anything.

Should we run a POV on both iOS and Android?

Yes. The SDK should be integrated on both iOS and Android if you have a mobile app on both operating systems. This allows Incognia to provide the most comprehensive analysis of your potential use cases and allows you to fully evaluate how our solution could help.

Do you have other questions? Ask Mike anything.

Will our users feel any impact of having the Incognia software on their device?

Any impact to the user will be minimal. Incognia’s SDK may increase the battery consumption on the user's device by approximately .5% per day.

Do you have other questions? Ask Mike anything.

Do we need to request location from our users to run a POV?

Yes. Incognia requires location from a statistically relevant group of app users for evaluation during the POV.

Do you have other questions? Ask Mike anything.

Do users need to provide “Always on” location permission to run a POV? What level of location permissions are required?

“Always” authorization for location data is NOT required for Incognia’s solution. Incognia can leverage background location data when it’s available, but by no means is it a requirement.

All Incognia customers today operate with “When In Use” location authorization, and our solution delivers strong performance.

For situations in which foreground location is preferred for battery consumption and privacy, Incognia has continued to optimize ways to continually collect location:

  • Proactively – For example, at app initialization

  • Opportunistically – For example, when location is made available in the app for other purposes

  • Programmatically – For example, time-based checks when app is in foreground

Do you have other questions? Ask Mike anything.

What data does the Incognia SDK collect?

We do not collect any personal data that can directly identify a person such as name, ID, e-mail, etc. We also do not collect any personal data considered sensitive, or PII. 

Data we collect through our SDK is listed below:

  • Location Data: Location information such as GPS, WiFi signals, and Bluetooth signals.

  • Device Identifier Data: Refers to the identifying information of your device on which the application is installed. For example, mad id (only stored after applying hash with a secret).

  • Device Data: Information related to your device, including device model, operating system, and operating system version.

  • Application Data: Information related to the application, such as the app session and events defined by the application developers (for example the registration of new users).

Do you have other questions? Ask Mike anything.

How large is the Incognia SDK?

Incognia’s Android SDK is 570 KB and iOS SDK is 1.9 MB.

Do you have other questions? Ask Mike anything.

How much battery power does the Incognia SDK require?

Our SDK’s battery consumption is 0.5% per day when operating with location in the background (non-standard). When our SDK operates in an app with location in the foreground only (standard), battery consumption is negligible.

Do you have other questions? Ask Mike anything.

What is the definition of Incognia’s risk assessments?

high_risk

Incognia deems the action (e.g. signup, login) performed by the device to be potentially fraudulent, and advises you to take preventive actions for the given action.

low_risk

Incognia considers this action performed by the device to be safe to accept.

unknown_risk

Incognia is unable to provide a precise assessment at the time of the request.

Do you have other questions? Ask Mike anything.

Schedule a Demo

One of our specialists will be glad to meet you and go over Incognia's capabilities.

To help us personalize our conversation for your business, please fill out the following form.