A [global callback](/en/article/server-callbacks#global-callbacks) is a main callback that covers every data point that Adjust measures.

Global callbacks are fired in addition to any other callback that you have specified at the individual event level. So, if you set a global callback in addition to a callback at the in-app event level, Adjust will fire two callbacks: one that contains the data requested in the global callback and one that contains the data requested at the in-app event level.  

The recommended placeholders below are the bare essentials for a global callback. If, for example, you are expecting to receive information on [installs](/en/article/install-callbacks), [sessions](/en/article/session-callbacks), and [in-app events](/en/article/event-callbacks), your global callback URL should also include the recommended placeholders found on those pages. 

## [Recommended placeholders](#recommended-placeholders)

<table>
  <thead>
    <tr>
      <th>Placeholder</th>
      <th>Description</th>
      <th>Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>{activity_kind}</code></td>
      <td>This will allow you to determine the data point, such as impression, click, install, rejected install, session, and more</td>
      <td><code>session</code></td>
    </tr>
    <tr>
      <td><code>{event}</code></td>
      <td>This will allow you to identify different in-app events at the event-token level</td>
      <td><code>bkrfgq</code></td>
    </tr>
    <tr>
      <td><code>{event_name}</code></td>
      <td>This will allow you to identify different in-app events by the event name as written in AppView</td>
      <td><code>signup</code></td>
    </tr>
  </tbody>
</table>

<callout type="note">
Event names can always be modified in AppView, and so you should use the <code>{event_name}</code> placeholder as a human-readable label. Conversely, event tokens are permanent, and can always be referenced in your reporting as a constant identifier.
</callout>

## Callback example

++++>
### Callback URL with placeholders
#### Unencoded (Do not use as is)

```uri
https://serverendpoint.com/mobile_attribution?gps_adid={gps_adid}&idfa={idfa}&idfv={idfv}&adid={adid}&tracker_token={link_token}&tracker_name={link_name}&app_name={app_name}&activity_kind={activity_kind}&created_at={created_at}&event_token={event}&event_name={event_name}
```

===
### Callback URL populated with values

```uri
https://serverendpoint.com/mobile_attribution?gps_adid=gps_adid=38400000-8cf0-11bd-b23e-10b96e40000d&adid=18546f6171f67e29d1cb983322ad1329&tracker_token=abc123&tracker_name=Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en&app_name=MyApp&activity_kind=event&created_at=1533568830&event_token=bkrfgq&event_name=purchase_100_coins
```

++++<

## [Other recommended placeholders](general-recommended-placeholders)

We also advise that you include the following placeholders in all callback URLs. These placeholders will ensure that you always receive basic information that you can use to identify the app, link, data point, and device to which the rest of your callback data belongs.

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Placeholder</th>
      <th colspan="1" rowspan="1">Description</th>
      <th colspan="1" rowspan="1">Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>{gps_adid}</code></td>
      <td>Google Play Store advertising ID (Android only)</td>
      <td>38400000-8cf0-11bd-b23e-10b96e40000d</td>
    </tr>
    <tr>
      <td><code>{idfa}</code></td>
      <td>ID for advertisers (iOS only)</td>
      <td>8C6CBCOD-5F43-4765-A6E6-84DFF3D24707</td>
    </tr>
    <tr>
      <td><code>{idfv}</code></td>
      <td>ID for vendors (iOS only)</td>
      <td>CCB300A0-DE1B-4D48-BC7E-599E453B8DD4</td>
    </tr>
    <tr>
      <td><code>{adid}</code></td>
      <td>Adjust device ID</td>
      <td>18546f6171f67e29d1cb983322ad1329</td>
    </tr>
    <tr>
      <td><code>{tracker}</code></td>
      <td>Adjust link token</td>
      <td>abc123</td>
    </tr>
    <tr>
      <td><code>{tracker_name}</code></td>
      <td>Current link name as defined in Campaign Lab</td>
      <td>Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en</td>
    </tr>
    <tr>
      <td><code>{app_name}</code></td>
      <td>Name of the app</td>
      <td>MyApp</td>
    </tr>
    <tr>
      <td><code>{activity_kind}</code></td>
      <td>This will allow you to determine the data point: impression, click, install, rejected install, rejected reattribution, session, reattribution, uninstall, reinstall, reattribution reinstall, updated attribution, in-app event, or ad spend (<code>cost_updated</code>)</td>
      <td>rejected_reattribution</td>
    </tr>
    <tr>
      <td><code>{created_at}</code></td>
      <td>The timestamp for when the data point occurred</td>
      <td>1404214665</td>
    </tr>
  </tbody>
</table>

The recommended placeholders that are the bare essentials for a global callback.

## [Other recommended placeholders](general-recommended-placeholders)

We also advise that you include the following placeholders in all callback URLs. These placeholders will ensure that you always receive basic information that you can use to identify the app, link, data point, and device to which the rest of your callback data belongs.

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Placeholder</th>
      <th colspan="1" rowspan="1">Description</th>
      <th colspan="1" rowspan="1">Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>{gps_adid}</code></td>
      <td>Google Play Store advertising ID (Android only)</td>
      <td>38400000-8cf0-11bd-b23e-10b96e40000d</td>
    </tr>
    <tr>
      <td><code>{idfa}</code></td>
      <td>ID for advertisers (iOS only)</td>
      <td>8C6CBCOD-5F43-4765-A6E6-84DFF3D24707</td>
    </tr>
    <tr>
      <td><code>{idfv}</code></td>
      <td>ID for vendors (iOS only)</td>
      <td>CCB300A0-DE1B-4D48-BC7E-599E453B8DD4</td>
    </tr>
    <tr>
      <td><code>{adid}</code></td>
      <td>Adjust device ID</td>
      <td>18546f6171f67e29d1cb983322ad1329</td>
    </tr>
    <tr>
      <td><code>{tracker}</code></td>
      <td>Adjust link token</td>
      <td>abc123</td>
    </tr>
    <tr>
      <td><code>{tracker_name}</code></td>
      <td>Current link name as defined in Campaign Lab</td>
      <td>Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en</td>
    </tr>
    <tr>
      <td><code>{app_name}</code></td>
      <td>Name of the app</td>
      <td>MyApp</td>
    </tr>
    <tr>
      <td><code>{activity_kind}</code></td>
      <td>This will allow you to determine the data point: impression, click, install, rejected install, rejected reattribution, session, reattribution, uninstall, reinstall, reattribution reinstall, updated attribution, in-app event, or ad spend (<code>cost_updated</code>)</td>
      <td>rejected_reattribution</td>
    </tr>
    <tr>
      <td><code>{created_at}</code></td>
      <td>The timestamp for when the data point occurred</td>
      <td>1404214665</td>
    </tr>
  </tbody>
</table>

All callbacks placeholders

Global callbacks

Take your growth to the next level with Adjust’s setup guides, best practices, and FAQs.

Marketer

Integrate our APIs and open-source SDKs with your apps and business analytics.


Developer

In-depth advice for our global Technology Partners on how best to work with Adjust.


Placeholder	Description	Example
`{activity_kind}`	This will allow you to determine the data point, such as impression, click, install, rejected install, session, and more	`session`
`{event}`	This will allow you to identify different in-app events at the event-token level	`bkrfgq`
`{event_name}`	This will allow you to identify different in-app events by the event name as written in AppView	`signup`

Placeholder	Description	Example
`{gps_adid}`	Google Play Store advertising ID (Android only)	38400000-8cf0-11bd-b23e-10b96e40000d
`{idfa}`	ID for advertisers (iOS only)	8C6CBCOD-5F43-4765-A6E6-84DFF3D24707
`{idfv}`	ID for vendors (iOS only)	CCB300A0-DE1B-4D48-BC7E-599E453B8DD4
`{adid}`	Adjust device ID	18546f6171f67e29d1cb983322ad1329
`{tracker}`	Adjust link token	abc123
`{tracker_name}`	Current link name as defined in Campaign Lab	Network1%3A%3AChristmas%3A%3AReindeers%3A%3A320x70_en
`{app_name}`	Name of the app	MyApp
`{activity_kind}`	This will allow you to determine the data point: impression, click, install, rejected install, rejected reattribution, session, reattribution, uninstall, reinstall, reattribution reinstall, updated attribution, in-app event, or ad spend (`cost_updated`)	rejected_reattribution
`{created_at}`	The timestamp for when the data point occurred	1404214665