Adjust webhook

This article gives you knowledge of how webhooks send information from Adjust to Meiro Events.

Requirements

To properly set up the webhook, it is required firstly to arrange server-to-server security. This means that each incoming request should carry a token generated in the Adjust dashboard. Requests that do not carry the token or that carry an incorrect token are rejected by Adjust server.

Feature

In the Adjust when a webhook is triggered, it automatically shows the event in your active event list and dashboard statistics.

Adjust automatically hides events that are more than 3 months old and have no tracked history, though all hidden event data remains available for export through their KPI service.

In Adjust you may customize the event integration to track unique events once per device. They’re helpful for adding context to events the app can’t recognize, like showing registration as unique from a login in-app action.

Examples of events in Adjust include:

Example data

Example: Install callbacks

Adjust servers trigger an install callback when a user opens an app for the first time after installation.

Use cases

Here are practical use cases on how to generate Adjust webhooks with the Meiro Events:

One of the benefits of tracking the events is collecting valuable statistics that may be used in running advertising campaigns. The event will bring you deep insights into where your users go directly after installation, or what features are of the most interest or identify the last thing users do before they become inactive, etc.

You may trigger sending of reports as a response to tracked anomalies for low installations rate. When the condition is met, then you'll receive a message with a link to the report sent by an Adjust webhook.