Set up Precog for App
Precog for App is an analytics partner integrated with Adjust. Our integration lets Precog for App receive data measured in Adjust through automated callbacks. Use this data with the partners' tools for analytics and insights.
In this article, learn how to set up measurement with Precog for App for your app. This includes activating the integration and choosing what data Adjust can share with Precog for App.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Precog for App parameters. Follow the guides linked below to use this feature.
iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona
Credentials
API KEY, DATABASE NAME, and TABLE NAME
- For help finding your credentials, contact your Precog for App representative.
Select Precog for App and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Precog for App. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Precog for App.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Precog for App. To enable data sharing:
- Enter your API KEY, DATABASE NAME, and TABLE NAME.
Once you enable data sharing with Precog for App, Adjust automatically sends Precog for App the following data, by default:
- click
- impression
- install
- session
- uninstall
- reinstall
- reattributionReinstall
- reattribution
Set your data sharing options
If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- 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 Precog for App by default:
- click
- impression
- install
- session
- uninstall
- reinstall
- reattributionReinstall
- reattribution
Send additional data
Choose the amount and type of data that you want to share with Precog for App through callbacks. Precog for App may use this information to optimize performance.
To send additional data, you can review and customize the following:
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Precog for App will receive your app’s session activity.
Uninstalls or reinstalls
Sharing uninstalls or reinstalls lets Precog for App receive your app’s uninstall and/or reinstall data measured by Adjust.
For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Precog for App receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Map events
Map events that you want to share to the values that Precog for App can receive. Data for unmapped events is not shared with Precog for App.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Precog for App. This lets you:
- Set individual events to manage campaign strategies for each platform.
- Customize data sharing per platform.
Under Map events, follow these steps to choose the in-app events you want to directly send to Precog for App.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Precog for App.
- Under Partner event, you need to select the Precog for App event that corresponds to the Adjust event.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
- Select Use global mapping to map the same events for all platforms.
- In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Apply.
Now Precog for App will receive in-app event data for each of your linked events.
Map all events
If Precog for App supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Precog for App will receive in-app event data for all your linked events.
Map parameters
You usually need to map parameters to share custom data with Precog for App.
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. This lets Precog for App receive custom event details for each of your linked events.
Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.
To share partner parameters to Precog for App, follow these steps.
- Set up partner parameters within the Adjust SDK.
- Check Before you begin for all SDK development platform links.
- Under Set your data sharing options, select Parameters.
- Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
- Select Map parameter.
- In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
- In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.
Enable Precog for App 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 Precog for App 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.
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 |
{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 |
{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 |
{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 |
{idfv} | Uppercase iOS ID for vendors |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{inactive_user_definition} | Inactivity period required for reattribution (hours) |
{ip_address} | Device IP address |
{language} | Device two-character language code |
{last_time_spent} | Length of user's last session, in seconds |
{match_type} | Attribution method |
{mnc} | Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier. |
{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) |
{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 |
{time_spent} | Length of user's current session, in seconds |
{timezone} | Device time zone |
{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 |
{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 |
{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 |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{engagement_time} | Engagement timestamp |
{installed_at} | Install (i.e., first app open) timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{last_tracker_name} | A reattributed user's previous tracker name |
{last_tracker} | 6-character Adjust tracker token of a reattributed user's previous tracker |
{network_name} | Network name, as taken from the tracker |
{reattributed_at} | Reattribution timestamp |
{store} | Target store of click |
{tracker_name} | Current tracker name |
{tracker} | 6-character Adjust tracker token |