Set up Easyence
Easyence is an analytics partner integrated with Adjust. Our integration lets Easyence 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 Easyence for your app. This includes activating the integration and choosing what data Adjust can share with Easyence.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Easyence 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
ACCOUNT ID and API KEY
- For help finding your credentials, contact your Easyence representative.
Select Easyence and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Easyence. 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 Easyence.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Easyence. To enable data sharing:
- Enter your ACCOUNT ID and API KEY.
Once you enable data sharing with Easyence, Adjust automatically sends Easyence the following data, by default:
- install
- session
- event
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 Easyence by default:
- install
- session
- event
Send additional data
Choose the amount and type of data that you want to share with Easyence through callbacks. Easyence 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 Easyence will receive your app’s session activity.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Easyence 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 Easyence can receive. Data for unmapped events is not shared with Easyence.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Easyence. 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 Easyence.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Easyence.
- Under Partner event, you need to select the Easyence 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 Easyence will receive in-app event data for each of your linked events.
Map all events
If Easyence supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Easyence will receive in-app event data for all your linked events.
Map parameters
You usually need to map parameters to share custom data with Easyence.
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Easyence. This lets Easyence 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 Easyence, 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 Easyence 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 Easyence 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 Easyence
Easyence requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{android_id} | Android ID (Android only) |
{city} | Device city |
{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_type} | Device type |
{environment} | Current Adjust SDK environment setting |
{gclid} | Google click ID |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{ip_address} | Device IP address |
{label} | Value of the Adjust "label" parameter sent on click |
{language} | Device two-character language code |
{os_name} | Device operating system |
{partner_parameters} | Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks |
{random_user_id} | Random user ID (per device) |
{reftag} | Random device reference tag |
{revenue_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{session_count} | Number of sessions recorded by current Adjust SDK |
{time_spent} | Length of user's current session, in seconds |
{timezone} | Device time zone |
{tweet_id} | Unique tweet ID |
{activity_kind} | Type of user activity |
{adgroup_name} | Adgroup name, as taken from the tracker |
{campaign_name} | Campaign name, as taken from the tracker |
{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_hour} | Attributed impression timestamp, rounded to the nearest hour |
{install_begin_time} | App download began timestamp (Android and Google Play Store only) |
{install_finish_time} | App download completion timestamp |
{installed_at} | Install (i.e., first app open) timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{last_session_time} | Last session timestamp |
{network_name} | Network name, as taken from the tracker |
{referral_time} | User landed on app Play Store page timestamp (Android and Google Play Store only) |
{tracker_name} | Current tracker name |
{proxy_ip_address} | IP address of user's proxy |
{iad_keyword_id} | Apple Search Ads keyword ID |
{google_ads_campaign_name} | Google Ads campaign name |
{google_ads_campaign_type} | Google Ads campaign type |
{iad_ad_id} | Apple Search Ads adId |