Getloyal is a special network partner.

Special partners can use additional and extended data from adjust, and have been integrated with a custom module in adjust's backend. This guide describes how to activate the Getloyal module, as well as additional set up that may be required or beneficial.

To integrate Getloyal with adjust, follow these steps:

  1. Activate the module by flicking a switch in the Getloyal panel in your dashboard.
  2. Update your SDK to send certain partner parameters. This may be mandatory.
  3. Create a tracker for Getloyal, adding certain mandatory parameters, and use this as the destination of your ads.
  4. All set - adjust will transmit the requisite data to Getloyal.

1Activating the Getloyal module

All settings related to Getloyal can be found in your dashboard. Simply open your app settings and follow through to Partner Setup > Add Partners > Getloyal.

You can activate the Getloyal module simply by flicking the switch in your adjust dashboard. Getloyal will identify your app based on the bundle ID or store app ID that you've entered for your app.

Once activated, adjust will automatically start sending install and (when activated) event callbacks to Getloyal.

1.1List of parameters transmitted to Getloyal

Getloyal require certain parameters to be passed to them via their module. When you activate their module, the following parameters will be automatically transmitted.

  • Event names
  • SDK version
  • Revenue data (if you activate it)
  • Timestamps
  • City
  • Locale
  • Hashed device IDs
  • Raw device IDs
  • Device model
  • OS name and versions
  • Country
  • Partial tracker names
  • All partner parameters (if you activate them)

2Creating tracker URLs for Getloyal

Getloyal requires certain tracker parameters. These tracker parameters must be appended in order for adjust to attribute your Getloyal traffic correctly, and for Getloyal to correctly interpret the data being sent back to them from adjust. Follow these steps to set up a tracker URL for Getloyal:

  1. Create a tracker in your adjust dashboard, naming it as you like, e.g. "Getloyal". The tracker URL will be created and added to your list of trackers.
  2. Copy the tracker URL using the "Copy URL" button on the right hand side, as you hover over your "Getloyal" tracker.
  3. In a text editor, paste the URL. Add one of the following strings to the end of the URL, depending on the platform.
    iOS & Android:
    ?glc_id=1

  4. Copy the URL and use it as the destination of any Getloyal ads.
    Your URL should look something like:
    https://app.adjust.com/f0ob4r?glc_id=1

For more details on creating tracker URLs, please check out the tracker generation guide.

3Sending partner parameters to Getloyal

Getloyal allows you to send a set of predefined parameters. If you attach any of these parameters to an event in your adjust SDK, these will be forwarded to Getloyal. You can find out more about attaching partner parameters in the SDK readme specific to the SDK or SDKs you are working with. Below is a list of the defined parameters that Getloyal accepts:

Parameter key Value
item_id An ID for the product visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in e-commerce apps.
restaurant_id An ID for the restaurant visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in food delivery apps.
food_id An ID for the product visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in food delivery apps.
hotel_id An ID for the hotel visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in hotel booking apps.
room_id An ID for the hotel room visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in hotel booking apps.
board_type The hotel board type visited by the user. Optional for all events tracked in hotel booking apps.
destination Travel destination visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in travel apps.
origin Travel origin visited by the user. Required for "purchase" events and recommended for "add to cart" and "item view" events tracked in travel apps.