Fraud Alerts
Case Study

Appsflyer's Protect360

Protect360 fraud solution, sets the standard for mobile ad fraud prevention and detection, ensuring users stay ahead of every threat, before, during, and after install.

To date, the app has more than 5M+ downloads

My Role

Senior UX designer, primary & secondary research, conducting user interviews, wireframes, final designs, branding, and website.

Give the user what he is looking for.
Before he starts looking for it.

The Problem

Many of our users have a compulsive habit of checking our system randomly in order to stay informed about their fraudulent activity. It feels annoying to play a guessing game with the system to get the info they are paying for, especially when working with large budgets that can easily go to waste.

Not to mention, most of the time they spend in the system is actively trying to filter the data and conduct an analyses to try to find their problematic sources.

Visited dashboard D/M

≤ 1

≤ 2

≤ 3

≤ 5

5 >

Renewal Rate

54%

60%

62%

68%

84.5%

Percent of accounts

18%

29%

39%

52%

48%

What did we find?

The more engaged a customer is with the dashboard

the more likely they will renew

- The goal -

Increase renewal %

Alexa Young, CA

“Give insights they push you.
So you don't need to dig.
Send notifications!"

Morgan James, NY

"As a UA manager, it's crucial for me to stay on top of any potential fraud activities on my campaigns. With the notifications feature I can receive real-time alerts and take immediate action to protect my ad spend."

Lisa Driver, MI

“Have customers review you and share what they had to say. Click to edit and add their testimonial.”

Solution

Create proactive notifications to inform our users for fraudulent activity.

Challenges

Create an easy sign up to the fraud alert system, and enable users to set their fraud threshold and wait for it to come!
Create a flow for users to return the system from directly from the notifications, and get focused and details from the dashboard. No need to search for the info anymore.
Quickly finding the hot data without depending on searching the system

Target Audience

Protect360 users, user acquisition managers

Understanding the need of the product

To understand the goal and need of the product, I tried to find the high-level problems that users face. we conducted a series of interviews with high end clients who use our product daily.

Interviews & key insights

I interviewed 9 people who use Protect360 to identify their behavior, working environment, needs, and frustrations. I created an empathy map to understand what these people say and do. I broke down all the responses into higher-level themes to come up with key insights.

Why are notifications necessary?
What notifications are likely to occur?
Which type of notification model should it use?
When should the notifications (and push notifications) appear/disappear?
How should the layout be presented when the notification has been dismissed?
How can the notifications be presented with more efficiency?
How should the notification settings be designed?

Findings

Reasons of checking Protect360

Users enter the dashboard to check their sources updates and activity, like finding bad media sources, compare activity by dates, look for fraud reasoning. download CSV files, share screenshots etc.

Too much information

Users want to bring as many installs as possible via the campaign / media sources the information on the dashboard is very overwhelming and complicated.

Keep a log / records of my activity

Users would either take screen shots of the dashboard, download a cdv file, and save the info in a folder on their desktop. There wasn’t a way to do this via the system.

No quick ways to share data

Users would like to keep a record of the info, download the data and share with their shareholders.

Playing the “Guessing game”

Users would often get annoyed that they didn’t know about the fraudulent activity on time to report their partners about the problematic sources

Hottest activity

Users wanted to get updated on new and fresh activity. this was one of the main reasons they use our dashboard.

Defining the user

After analyzing the key findings, I listed down user behavior, emotions, frustrations to validate my design decisions.

How might we?

a) Help users keep up with the important updates while they are working without entering the system?

b) Help users find what they are looking for without digging deep in the dashboard

c) Give the users a way to easily access prev activity and lost data

Listing ideas

We brainstormed possible features for our MVP and were marked them on a scale of impact and easiness to development. We decided that for MVP we’d let users set a threshold for the fraudulent activity and get notified daily.