Set up Pushwoosh

Pushwoosh is an analytics partner integrated with Adjust. Our integration lets Pushwoosh 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 Pushwoosh for your app. This includes activating the integration and choosing what data Adjust can share with Pushwoosh.

Before you begin

Requirements

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

Credentials

CUSTOMER KEY and APPLICATION CODE

  • For help finding your credentials, contact your Pushwoosh representative.

Select Pushwoosh and your app in Campaign Lab

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

Enable data sharing

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

  1. Enter your CUSTOMER KEY and APPLICATION CODE.

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

  • install
  • event

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 Pushwoosh by default:

  • install
  • event

Send additional data

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

To send additional data, you can review and customize the following:

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets Pushwoosh receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

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 Pushwoosh 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 Pushwoosh can receive. Data for unmapped events is not shared with Pushwoosh.

Map individual events

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Pushwoosh.
  3. Under Partner event, you need to select the Pushwoosh 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 Pushwoosh will receive in-app event data for each of your linked events.

Map all events

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

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

Map parameters

You usually need to map parameters to share custom data with Pushwoosh.

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Pushwoosh. This lets Pushwoosh 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 Pushwoosh, follow these steps.

  1. Set up partner parameters within the Adjust SDK.
  2. Under Set your data sharing options, select Parameters.
  3. Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
    1. Select Map parameter.
    2. In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
    3. In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
Note:

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 Pushwoosh 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 Pushwoosh 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.

Partner specific setup instructions

Pushwoosh allows you to send any kind of partner parameters. Any partner parameters that you send in the SDK will be forwarded to Pushwoosh, and incorporated into their analysis.

List of all parameters forwarded to Pushwoosh

Pushwoosh 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)
{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_type}The campaign pricing model (available for ad spend tracking only)
{currency}Original ISO 4217 currency code sent from Adjust SDK
{deeplink}Deeplink URL appended to click URL
{event_name}Event name, as set in the Dashboard
{gclid}Google click ID
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{is_reattributed}1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
{lifetime_session_count}Number of sessions recorded across entire user lifetime
{match_type}Attribution method
{partner_parameters}Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{push_token}Push notification token, i.e., registration token (Android), device token (iOS)
{referrer}Google Play Store referrer (Android only)
{reftag}Random device reference tag
{reporting_cost}Cost of the user engagement converted to your app's reporting currency and as reported in the Adjust Dashboard (available for ad spend tracking only)
{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}Revenue, in US dollars
{revenue}Revenue, as sent from Adjust SDK in cents
{session_count}Number of sessions recorded by current Adjust SDK
{time_spent}Length of user's current session, in seconds
{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_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{click_referer}Referrer header from click
{click_time_hour}Attributed click timestamp, rounded to the nearest hour
{created_at}Activity timestamp
{engagement_time_hour}Engagement timestamp rounded to the nearest hour
{first_tracker_name}Name of a user's first attribution source
{hardware_name}Hardware name
{impression_based}1 if impression-based engagement, 0 if not
{impression_time_hour}Attributed impression timestamp, rounded to the nearest hour
{installed_at_hour}Install (i.e., first app open) timestamp rounded to the nearest hour
{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_hour}Reattribution timestamp, rounded to the nearest hour
{reinstalled_at}Reinstall timestamp
{store}Target store of click
{tracker_name}Current tracker name
{tracker}6-character Adjust tracker token
{uninstalled_at}Uninstall timestamp (estimation based on last session time)