Set up FraudScore

FraudScore is an analytics network integrated with Adjust. Our integration lets FraudScore receive attribution and in-app event data through automated callbacks. Use this data with the partners' tools for analytics and insights.

In this article, learn how to set up measurement with FraudScore for your app. This includes activating the integration and choosing what data Adjust can share with FraudScore.

Before you begin

Requirements

iOS / Android / Windows / Unity / React Native / Flutter / Adobe Air / Cordova / Marmalade / Xamarin / Cocos2d-x / Titanium / Corona

Credentials

API KEY

  • For help finding your credentials, contact your FraudScore representative.

Select FraudScore and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > FraudScore. Select Next to move to the next screen.
  3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with FraudScore.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with FraudScore. To enable data sharing:

  1. Enter your API KEY.

Once you enable data sharing with FraudScore, Adjust automatically sends FraudScore the following data, by default:

  • click
  • install
  • event
  • rejectedInstall

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

  1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
  2. Set the same data sharing settings for multiple platforms by selecting Use global settings.

Now, under What will be shared by default?, review the activities that Adjust shares with FraudScore by default:

  • click
  • install
  • event
  • rejectedInstall

Send additional data

Choose the amount and type of data that you want to share with FraudScore through callbacks. FraudScore may use this information to optimize performance.

To send additional data, you can review and customize the following:

Map events

Map events that you want to share to the values that FraudScore can receive. Data for unmapped events is not shared with FraudScore.

Under Map events, follow these steps to choose the in-app events you want to directly send to FraudScore.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with FraudScore.
  3. In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to. You might have to map an event to several values.
  4. Select Apply.

Now FraudScore will receive in-app event data for each of your linked events.

Enable FraudScore for your app

In the Setup review screen, you can review your choices. You can also go back and make changes to:

  • Your selected app
  • Data sharing options

Select Enable partner to enable FraudScore for your app. Analytics partners don't work with links for campaigns. Once enabled, our integration sends attribution and in-app event data via automated callbacks.

Partner specific setup instructions

To set up Fraudscore reporting to include network click IDs, append &label={network_id_macro} to your Adjust tracker URL using a valid macro .

List of all parameters forwarded to FraudScore

FraudScore requires Adjust to send the following parameters (data points) with your callbacks:

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{android_id}Android ID (Android only)
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{country_subdivision}Device subdivision of country, e.g., state
{country}Device two-character country code
{deeplink}Deeplink URL appended to click URL
{device_name}Device model number
{device_type}Device type
{gclid}Google click ID
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{impression_attribution_window}Attribution window settings for impression matching (hours)
{inactive_user_definition}Inactivity period required for reattribution (hours)
{ip_address}Device IP address
{isp}Device internet service provider
{label}Value of the Adjust "label" parameter sent on click
{language}Device two-character language code
{nonce}Random lowercase alphanumeric string (unique per callback)
{os_name}Device operating system
{os_version}Operating system version number
{postal_code}Device postal code of IP address
{random}Random number (unique per callback)
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{referrer}Google Play Store referrer (Android only)
{reftag}Random device reference tag
{timezone}Device time zone
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{adgroup_name}Adgroup name, as taken from the tracker
{app_id}Store App ID or Google Play Store
{app_name_dashboard}Name of the app in the Adjust Dashboard
{app_name}Name of the app
{app_version_raw}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{click_referer}Referrer header from click
{click_time}Attributed click timestamp
{connection_type}Internet connection type
{created_at_hour}Activity timestamp, rounded down to the nearest hour
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{network_name}Network name, as taken from the tracker
{rejection_reason}Reason for a rejected attribution
{store}Target store of click