Languages 

Set up LayApp

LayApp is a network and Adjust module partner. Our integration lets LayApp receive attribution and in-app event data through automated callbacks.

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

Basic setup

To turn on Adjust’s integration with LayApp, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select the add (+) icon next to LayApp
  4. Turn on Enabled
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

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

  • click
  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • reattribution
  • event
  • rejectedInstall

Advanced setup

Choose which data LayApp receives from Adjust by customizing your setup.

Forward in-app revenue

In-app revenue forwarding lets LayApp receive revenue amounts along with your revenue event data.

To forward in-app revenue to LayApp, follow these steps.

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

Now LayApp will receive the revenue amount for every tracked transaction.

Note: Link at least one [revenue event] to LayApp before turning on In-App Revenue Forwarding.

Forward uninstalls / reinstalls

To forward uninstalls and/or reinstalls to LayApp, follow these steps.

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

Now LayApp 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 LayApp, follow these steps.

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

Now LayApp 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 LayApp.

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 LayApp, 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 > LayApp
  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 LayApp name.
  7. Select Save

Now LayApp 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 in-app events

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

To forward in-app events to LayApp, follow these steps.

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

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

List of all parameters forwarded to LayApp

LayApp 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)
{api_level}API level (Android only)
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{cost_amount}Cost of the user engagement (available for ad spend tracking only)
{cost_currency}ISO 4217 currency code of the cost data (available for ad spend tracking only)
{cost_id_md5}An MD5 hash of the cost ID provided by a network using our ad spend API (available for ad spend tracking only)
{cost_type}The campaign pricing model (available for ad spend tracking only)
{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
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{inactive_user_definition}Inactivity period required for reattribution (hours)
{ip_address}Device IP address
{isp}Device internet service provider
{language}Device two-character language code
{last_time_spent}Length of user's last session, in seconds
{lifetime_session_count}Number of sessions recorded across entire user lifetime
{mac_sha1}Uppercase MAC SHA-1 hash
{match_type}Attribution method
{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)
{region}Device region code
{reporting_currency}Dashboard reporting ISO 4217 currency code
{reporting_revenue}Revenue, as reported in the Adjust Dashboard, in whole currency units
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{revenue_usd_cents}Revenue, in US cents
{revenue_usd}Revenue, in US dollars
{revenue}Revenue, as sent from Adjust SDK in cents
{sdk_version}Adjust SDK version (per app)
{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_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
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{attribution_updated_at}Updated attribution timestamp
{campaign_name}Campaign name, as taken from the tracker
{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
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{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
{reattributed_at}Reattribution timestamp
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{reinstalled_at}Reinstall timestamp
{rejection_reason}Reason for a rejected attribution
{store}Target store of click
{time_to_reinstall}Time between latest app uninstall and subsequent reinstall in seconds
{time_to_uninstall}Time between app install (or latest reinstall) and subsequent uninstall in seconds
{tracker_name}Current tracker name
{uninstalled_at}Uninstall timestamp (estimation based on last session time)