Set up Lacuna

Lacuna is an ad network integrated with Adjust. Our integration lets Lacuna receive attribution and in-app event data through automated callbacks.

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

Before you begin

Requirements

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

Select Lacuna and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > Lacuna. 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 Lacuna.
  4. Select Next.

Enable data sharing

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

  1. Turn on Enabled

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

  • install
  • reattribution
  • event
  • rejectedInstall
  • ad revenue

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 Lacuna by default.

  • install
  • reattribution
  • event
  • rejectedInstall
  • ad revenue

Send additional data

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

  1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Lacuna:
  • Data from all attribution sources
  • Only data attributed to Lacuna

Ad revenue (from ad views)

Ad revenue sharing lets Lacuna receive user ad revenue data. This lets Lacuna use ad revenue data to optimize your user targeting and campaigns.

Growth solution:

This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.

To share ad revenue to Lacuna, select one or more Ad Revenue Sources.

  • If you leave this field empty, we send ad revenue data from all integrated mediation sources.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Lacuna 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 Lacuna can receive. Data for unmapped events is not shared with Lacuna.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Lacuna. 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 Lacuna.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Lacuna.
  3. Under Partner event, you need to select the Lacuna event that corresponds to the Adjust event.
    1. 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.
    2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
  4. Select Apply.

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

Map all events

If Lacuna supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now Lacuna will receive in-app event data for all your linked events.

Configure your link and settings

You have the option to set your:

Create your link and share it with Lacuna

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
  • Link structure parameters
  • User destinations
  • Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Lacuna.

Once you’ve created your link, share it with Lacuna for placement in campaigns.

List of all parameters forwarded to Lacuna

Lacuna 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
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{device_type}Device type
{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
{language}Device two-character language code
{match_type}Attribution method
{os_name}Device operating system
{os_version}Operating system version number
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{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
{timezone}Device time zone
{user_agent}Incoming raw user agent
{app_name}Name of the app
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{click_time}Attributed click timestamp
{conversion_duration}Time between click and install or reattribution in seconds
{created_at}Activity timestamp
{device_manufacturer}Device manufacturer name
{hardware_name}Hardware name
{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
{last_session_time}Last session timestamp
{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
{tracker_name}Current tracker name
{ad_impressions_count}Number of mobile ads served to end users
{ad_revenue_network}Ad network that displayed the ad
{ad_revenue_unit}Ad unit that generated the revenue
{ad_revenue_placement}User placement, as defined on the platform
{oaid}OAID device ID
{ad_mediation_platform}Mediation platform name