Set up Precog for App

Precog for App is an Adjust module partner. Our integration lets Precog for App receive attribution and app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Precog for App. Then, use our advanced setup instructions to customize what information Precog for App receives.

Basic setup

To turn on Adjust’s integration with Precog for App, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select Add (+icon) next to Precog for App
  4. Enter your API KEY, DATABASE NAME and TABLE NAME (contact your Precog for App representative for help finding these)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Precog for App will receive callbacks for these activities:

  • impression
  • click
  • install
  • session
  • reattribution
  • reattribution reinstall
  • reinstall
  • uninstall

Advanced setup

Choose which data Precog for App receives from Adjust by customizing your setup.

Forward in-app revenue

Revenue forwarding lets Precog for App receive revenue amounts along with your revenue event data.

To forward in-app revenue to Precog for App, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Precog for App
  3. Turn on In-App Revenue Forwarding

Now Precog for App will receive the revenue amount for every tracked transaction.

 

Note: Link at least one revenue event to Precog for App before turning on Revenue Forwarding

 

Forward uninstalls / reinstalls

To forward uninstalls and/or reinstalls to Precog for App, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Precog for App
  3. Turn on Uninstall / Reinstall Forwarding

Now Precog for App will receive all of your app's uninstall and/or reinstall data

 

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to Precog for App, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Precog for App
  3. Turn on Session Forwarding

Now Precog for App will receive your app’s session activity.

 

Forward custom data

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Precog for App.

Note: Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To forward partner parameters to Precog for App, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > Precog for App
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding Precog for App name.
  7. Select Save

Now Precog for App will receive custom event details for each of your linked events.

 

Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.

 

Forward app events

Event linking lets Precog for App receive app event data. You can link every app event in Adjust to a preset Precog for App name or a custom event name.

To forward app events to Precog for App, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup >Precog for App > Event Linking
  3. Find the event you want to link and update the field with a Precog for App event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now Precog for App will receive app event data for each of your linked events.

List of all parameters forwarded to Precog for App

Precog for App requires Adjust to send the following parameters (data points) with your callbacks:

Placeholder Information
{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} Name of the app
{campaign_name} Campaign name, as taken from the tracker
{city} Device city
{click_attribution_window} Attribution window settings for device matching (hours)
{click_referer} Referrer header from click
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{conversion_duration} Time between click and install or reattribution in seconds
{country_subdivision} Device subdivision of country, e.g., state
{country} Device two
{created_at} Activity timestamp
{creative_name} Creative name, as taken from the tracker
{currency} Original ISO 4217 currency code sent from Adjust SDK
{deeplink} Deeplink URL appended to click URL
{device_name} Device model number
{device_type} Device type
{engagement_time} Engagement timestamp
{environment} Current Adjust SDK environment setting
{event_name} Event name, as set in the Dashboard
{gclid} Google click ID
{idfa||android_id} IDFA, or Android ID if IDFA is empty
{idfa||gps_adid} IDFA, or GPS ADID if IDFA is empty
{impression_attribution_window} Attribution window settings for impression matching (hours)
{inactive_user_definition} Inactivity period required for reattribution (hours)
{installed_at} Install (i.e., first app open) timestamp
{ip_address} Device IP address
{is_organic} 1 if organic traffic, 0 if non
{language} Device two
{last_time_spent} Length of user's last session, in seconds
{last_tracker_name} A reattributed user's previous tracker name
{last_tracker} 6
{match_type} Attribution method
{mnc} Mobile network code: two
{network_name} Network name, as taken from the tracker
{nonce} Random lowercase alphanumeric string (unique per callback)
{os_name} Device operating system
{os_version} Operating system version number
{partner_parameters} Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{postal_code} Device postal code of IP address
{random_user_id} Random user ID (per device)
{random} Random number (unique per callback)
{reattributed_at} Reattribution timestamp
{reattribution_attribution_window} Attribution window settings for reattribution (hours)
{reftag} Random device reference tag
{region} Device region code
{revenue_float} Revenue, as sent from Adjust SDK, in whole currency units
{revenue_usd_cents} Revenue, in US cents
{revenue} Revenue, as sent from Adjust SDK in cents
{search_term} Google organic search term
{session_count} Number of sessions recorded by current Adjust SDK
{store} Target store of click
{time_spent} Length of user's current session, in seconds
{timezone} Device time zone
{tracker_name} Current tracker name
{tracker} 6
{tracking_enabled} 1 if tracking is enabled, 0 if not
{tracking_limited} 1 if tracking is limited, 0 if not
{user_agent} Incoming raw user agent