With Adjust’s Facebook integration, you can track performance marketing efforts on Facebook, Facebook Messenger, and Instagram.  

Use our basic setup instructions to connect Adjust to Facebook and track your campaigns. When you’re finished, move on to the advanced setup instructions to turn on impression-based attribution, forward data to Facebook, and more.

## [Before you begin](before-you-begin)

Here's what you need to know before getting started.  

**Requirements**

*   A registered [Facebook app](https://developers.facebook.com/apps/).
*   A [Facebook Developer App ID](https://developers.facebook.com/apps).

## [Basic setup](basic-setup)

<div class="wistia_responsive_padding"
  style=""><iframe frameborder="0"
    scrolling="no" class="wistia_embed"
    allowfullscreen="allowfullscreen"
    height="253"
    mozallowfullscreen="mozallowfullscreen"
    name="wistia_embed"
    src="//fast.wistia.net/embed/iframe/59jp75eb9r"
    width="450"></iframe><span
    class="wistia_embed wistia_async_59jp75eb9r popover=true popoverAnimateThumbnail=true">&nbsp;</span>
</div>

Share the video with [this link](https://adjust-video.wistia.com/medias/59jp75eb9r). To connect your Adjust dashboard to Facebook Ads, follow these steps.

1.  Find your app and select your app options caret (^).
2.  Select **Partner Setup**.
3.  Select **ADD PARTNERS**, and select **Add** (+ icon) beside **Facebook**.
4.  Enter your Facebook Developer App ID in the **APP ID** field.
5.  Select **SAVE**.

Well done! Your basic setup is complete.  

<callout type="note">
Your Facebook Developer App ID comes from your Facebook Developer account. This App ID should be the same for all of your apps in Adjust, regardless of platforms.
</callout>

## [Advanced setup](advanced-setup)

Now that Adjust is connected to Facebook, customize your setup.

### [Turn on impression-based (view-through) attribution](turn-on-impression-based-view-through-attribution)

Adjust does not automatically attribute installs to Facebook impressions. 

<fragment id="Turn on impression-based attribution" />

### [Disable Facebook event logging](disable-facebook-logging)

If your app includes the Facebook SDK, we recommend disabling its event logging features to ensure that there are no duplicate events between Facebook and Adjust. Instead of defining events in the Facebook SDK, you can define equivalent events on Adjust and link them to Facebook. Defining events on Adjust also allows you to link the events to other networks besides Facebook.

To disable Facebook SDK event logging, follow these steps:

1. Navigate to [Facebook App Dashboard](https://developers.facebook.com/apps/).
2. Click on your app.
3. Select __Settings__.
4. Select __Basic__.
5. Select __Log In-App Events Automatically__.
6. Set to __No__ to disable automatic event logging.

Disable Automatic Event Logging in the Facebook SDK in your app code by following these instructions:

* [iOS](https://developers.facebook.com/docs/app-events/getting-started-app-events-ios/#disable-auto-events)
* [Android](https://developers.facebook.com/docs/app-events/getting-started-app-events-android/#disable-auto-events)
* [Unity](https://developers.facebook.com/docs/app-events/unity#disable-automatically-logged-events)

Remove manually logged events in the Facebook SDK in your app code by following these instructions:

* [iOS](https://developers.facebook.com/docs/app-events/getting-started-app-events-ios/#manually-log-events)
* [Android](https://developers.facebook.com/docs/app-events/getting-started-app-events-android/#log-manually)
* [Unity](https://developers.facebook.com/docs/app-events/unity/#manually-log-events)

<callout type="note">
When using the Facebook Partner setup, Adjust will automatically link install and session events to Facebook. However, to log Purchase events that would normally be logged by Facebook's SDK you will need to create the Purchase event on Adjust and link it to Facebook.
</callout>

### [Forward in-app revenue and purchases](forward-in-app-revenue-and-purchases)

Revenue forwarding lets you pass detailed revenue data directly to your Facebook Ads Manager dashboard.  

To forward in-app revenue and purchases to Facebook, follow these steps.

1.  Find your app select the app options caret (^).
2.  Select **Partner Setup** > **Facebook**.
3.  Turn on **Revenue Forwarding**.
4.  Select **Event Linking**.
5.  Find the revenue event(s) you want to link and update the field(s) with _Fb Mobile Purchase_.
6.  Select **OK**.
7.  Select **SAVE**.

Now you'll see purchases and revenue amounts from Adjust displayed in your Facebook Ads Manager dashboard.

### [Forward ad revenue](forward-ad-revenue)

Ad revenue forwarding lets you send all of your ad revenue callbacks to Facebook. 

To forward ad revenue data, follow these steps.

1. Find your app select the app options caret (^).
2. Select __Partner Setup > Facebook__.
3. Turn on __Ad Revenue Forwarding__.
4. Select __SAVE__.

<callout type="note">
Your ad revenue data will display in Facebook Ads Manager under <code>fb_mobile_purchase</code>. This value is hardcoded and cannot be changed.
</callout>

### [Forward in-app events](forward-in-app-events)
Event linking (or mapping) lets you forward in-app event data directly to Facebook for more precise targeting. This is also required for event-based bid optimization.  

<callout type="note">
If you have already set up app event tracking in your Facebook SDK, do not set up event linking between Adjust and Facebook. This will duplicate your event data in Facebook. If you have questions about your setup, please reach out to <a href="mailto:support@adjust.com">support@adjust.com</a>.  
</callout>

To optimize your Facebook campaigns on Adjust events, you must link each event to one of the standard Facebook events that appear [here in their documentation](https://developers.facebook.com/docs/app-ads/optimizing-your-app-ad#app-event-optimization). 

If you link your Adjust events as other standard or custom events, Facebook will not use them for optimization.

1.  Find your app and select your app options caret (^).
2.  Select **Partner Setup** > **Facebook** > **Event Linking**.
3.  Find the event you want to link and update the field with a Facebook event name or your own custom name. For reference, the predefined Facebook labels are:
    *   `fb_mobile_level_achieved`
    *   `fb_mobile_add_payment_info`
    *   `fb_mobile_add_to_cart`
    *   `fb_mobile_add_to_wishlist`
    *   `fb_mobile_complete_registration`
    *   `fb_mobile_tutorial_completion`
    *   `fb_mobile_initiated_checkout`
    *   `fb_mobile_purchase`
    *   `fb_mobile_rate`
    *   `fb_mobile_search`
    *   `fb_mobile_spent_credits`
    *   `fb_mobile_achievement_unlocked`
    *   `fb_mobile_content_view`
    *   `Subscribe`
    *   `StartTrial`
    *   `AdClick`
    *   `AdImpression` 
4.  Select **OK**.
5.  Select **SAVE**.

### [Forward uninstalls](forward-uninstalls)

If you've purchased Adjust's uninstall and reinstall tracking, then Adjust automatically sends uninstall data to Facebook.  

To stop forwarding Adjust-tracked uninstalls to Facebook, follow these steps.

1.  Find your app and select the app options caret (^)
2.  Select **Partner Setup > Facebook**
3.  Turn off **Uninstall Forwarding**

To share uninstall data with Facebook again, you can turn on **Uninstall Forwarding** at any time.

### [Forward custom data](forward-custom-data)

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and forward them directly to Facebook.  

First, set up partner parameters within the Adjust SDK ([full list here](#developer-guides-for-partner-parameters)). Then, turn on partner parameter forwarding in the Adjust dashboard.  

To turn on partner parameter forwarding in Adjust, follow these steps.

1.  Find your app and select your app options caret (^)
2.  Select **Partner Setup** > **Facebook**
3.  Turn on **Parameter Forwarding**
4.  Select **Partner Parameter Mapping**
5.  In the **FROM APP** field, enter the name of your Adjust partner parameter (as written into the Adjust SDK). In the **TO FACEBOOK** field, enter your corresponding Facebook name.
6.  Select **SAVE**

Now that your partner parameters are connected to Facebook, Adjust will forward custom event details directly to Facebook for any of your linked events.

### [Developer guides for partner parameters](developer-guides-for-partner-parameters)

*   [iOS](https://github.com/adjust/ios_sdk#partner-parameters)
*   [Android](https://github.com/adjust/android_sdk#partner-parameters)
*   [Windows](https://github.com/adjust/windows_sdk#8-partner-parameters)
*   [Adobe Air](https://github.com/adjust/adobe_air_sdk#partner-parameters)
*   [Unity](https://github.com/adjust/unity_sdk#partner-parameters)
*   [Cordova](https://github.com/adjust/cordova_sdk#partner-parameters)
*   [Marmalade](https://github.com/adjust/marmalade_sdk#partner-parameters)
*   [Xamarin](https://github.com/adjust/xamarin_sdk#partner-parameters)
*   [Cocos2d-x](https://github.com/adjust/cocos2dx_sdk#partner-parameters)
*   [React Native](https://github.com/adjust/react_native_sdk#partner-parameters)
*   [Titanium](https://github.com/adjust/titanium_sdk#partner-parameters)
*   [Corona](https://github.com/adjust/corona_sdk#partner-parameters)

### [Additional deeplink support for Facebook](deeplink-support)

Adjust supports [Facebook App Links](https://developers.facebook.com/docs/applinks/overview) to deeplink users from a Facebook ad into your app, to an app store, or to a website. This means you can set up an ad campaign on Facebook using:

*   [An Adjust tracker with deep\_link parameter](/en/article/standard-deeplink-setup)
*   [A Universal link (iOS)](/en/article/direct-links-for-ios)

**Deeplink setup**

Adjust offers 2 parameters, which you should add to your deeplink:

*   If you are using a universal link, add `adj_mobile_not_track=1`
*   If you are using an Adjust tracker with the deep\_link parameter, add `mobile_not_track=1`

These parameters ensure that the user is attributed to Facebook as intended.

Example universal link with an Adjust tracker & website redirect:

 `https://xxxx.adj.st/path/?adjust_t=abc123b&adj_redirect=https://www.mysite.com&adj_mobile_not_track=1`

**Add your deeplink to Facebook**

To get started, add your Adjust deeplink to Facebook. To do this, follow these steps.

1.  Sign in to [Facebook Ads Manager](https://www.facebook.com/business/tools/ads-manager)
2.  Find your campaign and select **Text & Links**
3.  Under **Deep Link** enter your Adjust tracker + deeplink or Universal link 

**How does it work?** 

After adding your deeplink to Facebook, it is automatically converted into a link that’s set behind your ad. The link contains Facebook App Links metadata. When a user clicks your ad, this metadata is relayed back to Facebook instructing them where to send the user. For instance, they will be sent into your app if it’s already installed. If it's not installed, Facebook reads the redirect URL data from your deeplink and sends the user there instead. 

### [Forward data for Facebook Dynamic Ads](forward-data-for-facebook-dynamic-ads)

Facebook Dynamic Product Ads let you show the most relevant products to the users most likely to re-engage in your app and on other devices. Our integration lets you forward product data for dynamic ad tracking without the Facebook SDK.  

**Requirements**

*   A Facebook product catalog, product feed, and product set
*   Adjust SDK [partner parameters](#developer-guides-for-partner-parameters)

To forward data for Facebook Dynamic Product Ads, follow these steps.

#### 1. Link events to Facebook

In Adjust, [set up event linking](/en/article/facebook#forward-in-app-events) to the following Facebook events:

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Event name</th>
      <th colspan="1" rowspan="1">Description</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>Fb Mobile Content View</code></td>
      <td>When a user views a product</td>
    </tr>
    <tr>
      <td><code>Fb Mobile Add To Cart</code></td>
      <td>When an item is added to the cart</td>
    </tr>
    <tr>
      <td><code>Fb Mobile Purchase</code></td>
      <td>When an item/items are purchased</td>
    </tr>
  </tbody>
</table>

#### 2. Map partner parameters

Now that you’ve linked your events, follow the [custom data forwarding](#forward-custom-data) instructions to set up parameter mapping. Each event requires two successful parameter triggers: one for the item ID and one to identify a product or product group ID. All partner parameters, keys, and values must be alphanumeric and cannot contain any special characters.

Here are the parameters to include:

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Field name</th>
      <th colspan="1" rowspan="1">Description</th>
      <th colspan="1" rowspan="1">Type</th>
      <th colspan="1" rowspan="1">Required</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>fb_content_type</code></td>
      <td>Either&nbsp;product&nbsp;or&nbsp;product_group</td>
      <td>String</td>
      <td>Yes</td>
    </tr>
    <tr>
      <td><code>fb_content_id</code></td>
      <td>The retailer's product or product group ID(s). This should be a string containing a JSON-encoded array of IDs.</td>
      <td>String</td>
      <td>Yes</td>
    </tr>
    <tr>
      <td><code>_valueToSum</code></td>
      <td>The value of the product or purchase amount</td>
      <td>String</td>
      <td>No</td>
    </tr>
    <tr>
      <td><code>fb_currency</code></td>
      <td>The currency of the product or purchase amount</td>
      <td>String</td>
      <td>No</td>
    </tr>
  </tbody>
</table>

Now that your parameters are mapped, you can serve your app users Facebook Dynamic Product Ads.

### [Track Facebook Pixel events](track-facebook-pixel-events)

Adjust's webview bridge lets you track [Facebook Pixel](https://developers.facebook.com/docs/facebook-pixel/) events without integrating the Facebook SDK into your app. Our webview bridge passes your Facebook Pixel events to the Adjust SDK as app events, along with all related fields as partner parameters.

To implement Adjust's webview bridge, see our [Facebook Pixel integration](https://github.com/adjust/ios_sdk/blob/master/doc/english/fb_pixel.md) guide for developers on Github.

### [Track Facebook ad spend](tracking-facebook-ad-spend-in-adjust)

Adjust connects directly to your Facebook Ads account to track ad spend for your Facebook campaigns. Ensure you have the correct permissions set in your Facebook Ads account as shown in the image below:

<asset id="Facebook Ads Account Permissions" />

* For Ad spend tracking: The __Access your Facebook ads and related stats__ toggle must be set to __YES__.
* For Adjust Automate: *__Both__* the __Access your Facebook ads and related stats__ and __Manage your ads__ toggles must be set to __YES__.

To turn on ad spend tracking, follow these steps. 

1.  In Adjust, select **MENU**.
2.  Select **Partner Ad Accounts** > **Facebook**.
3.  Select **ADD ACCOUNT**, then enter your login credentials and confirm that Adjust can manage your ads.

All done! Now Adjust will track ad spend for your Facebook campaigns. To view a complete list of linked ad accounts, select **Settings** (gear icon).  

Adjust can access ad spend data for every linked account. To disconnect a Facebook ad account from Adjust, find the account's **Settings** (gear icon) and select **UNLINK**.

+++>
### If you are using Facebook Automated App Ads

* Facebook does not provide the `impression_device` parameter for Automated App Ads campaigns. So, for multiplatform apps, the dashboard displays the device operating system as `unknown`.
* The dashboard does not display data about `installs (paid)`. 

+++<

### [How do I view my Facebook ad spend data in Adjust?](how-do-i-view-my-facebook-ad-spend-data-in-adjust)

To view your Facebook ad spend, follow these steps in the Adjust Dashboard.

1. Find your app and select your options caret.
2. Select Statistics.
3. Select the __Cost__ tab.
4. Select __Filters__.
5. Under __Partners__, add `Facebook`.

Now you can see your total Facebook ad spend data displayed for the app. Select a tracker to drill-down into your data.

Use additional Filters to further refine your view. For instance, you can select __View By - Country__. This breaks your campaigns down according to the country they are run in, and offers a side-by-side comparison. 

With Adjust’s Facebook integration, you can track performance marketing efforts on Facebook, Facebook Messenger, and Instagram.

Facebook Ads Account Permissions

Set up Facebook

With Adjust's Google Ads integration, you can track and analyze the performance of your Google Ads campaigns.  

Use these basic setup instructions to connect Adjust with Google Ads and track your campaigns. When you're finished, move to the [customize your setup](/en/article/customize-your-google-ads-setup) instructions to track ad spend, forward data to Google Ads, and more.

## [Before you begin](before-you-begin)

**Requirements**

*   Google Ads account

**Helpful information**

- Adjust’s Google Ads API integration includes tracking for the following campaign types:
  - Search
  - Display
  - Shopping
  - Video
  - App
- All Google Ads traffic appears in the Statistics tab of your Adjust Dashboard.
- Your Google Ads conversions are organized in a campaign structure dependent upon the campaign type you used.


## [Basic setup](activating-the-adjust-google-adwords-integration)

Set up Google Ads in Adjust and import your linked events into Google Ads before launching your campaign.

## [1. Connect your Adjust dashboard to Google Ads](how-to-set-up-your-adwords-module-in-the-adjust-dashboard)

Connect your Adjust dashboard to Google Ads with the following steps:

1.  Find your app and select your app options caret (^).
2.  Select **Partner Setup**.
3.  Select **ADD PARTNERS,** and select **Add** (+ icon) beside **Google Ads**.
4.  Enter your LinkID in the **LINKID** field.
5.  Select **SAVE**.

You do not need to create any Adjust trackers for your campaigns. You should only create a tracker if you use Google Ads app extensions. The tracker is then implemented through the Google Ads UI. See [Manage event linking](#2--manage-event-linking) for more details. 

<callout type="note">
By default, the attribution window for all Google Ads regular campaign installs is set to 30 days, and Google Ads pre-registration campaigns are set to 90 days. These defaults will override your app’s attribution window settings. 
</br></br>
Adjust recommends that you match Google Ads' attribution window with your apps to avoid install discrepancies. While not recommended, you can customize your desired attribution window by turning off those defaults and by changing the attribution window in <b>All Settings > Attribution > Device matching</b>.
</callout>

## [2. Manage event linking in Adjust](how-to-set-up-event-linking-between-adjust-and-google-adwords)

All Adjust-tracked events are linked to Google Ads automatically. This means that Adjust sends in-app event data, from all sources, to Google Ads. 

To override automatic event linking and only share certain events with Google Ads, follow these steps.

1. Find your app and select your app options caret (^).
2. Select __Partner Setup > Google Ads > Event Linking__.
3. Find and select the event you want to remove.
4. Select __X__ (cross icon).

<callout type="warning">
Linked events must contain a valid IP address. If Adjust currently tracks your in-app events via a server-to-server integration, update your request to include an IP address using the parameter <code>ip_address=</code>
</callout>

For S2S event requests, [send your current SDK version](#send-the-sdk-version). Google uses this to fully optimize your in-app event campaigns.

### Event names

All event names appear in Google Ads as you label them in the Adjust Dashboard. Spaces and special characters are replaced with an underscore (`_`). Special characters that appear at the start or end of the name are deleted. Any series of two or more special characters are replaced with a single underscore.

**Example:** `REVad_$$cost$$` in the Adjust dashboard becomes `revad_cost` in Google Ads.  

You can change event names manually from the **Event Linking** section. Type a custom name or select a default name from the drop-down menu.

Here are the available default Adjust names that map to Google's in-app events:

*   `In App Purchase`
*   `View Item List`
*   `View Item`
*   `View Search Results`
*   `Add to Cart`
*   `Ecommerce Purchase`

Select `In App Purchase` for a revenue event. If you are certain that your transactions are consistently e-commerce, select `Ecommerce Purchase`. 

#### [Send the SDK version for server-to-server events](send-the-sdk-version)

It is recommended, not required, that you send your SDK version along with S2S events.   

To do this, you need the formatted SDK version. The format will be (platform)(SDK version). Here are some examples:

<table>
  <thead>
    <tr>
      <th>Platform</th>
      <th>SDK Version</th>
      <th>Formatted SDK Version</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>iOS</td>
      <td>4.12.3</td>
      <td><code>ios4.12.3</code></td>
    </tr>
    <tr>
      <td>Android</td>
      <td>4.18.0</td>
      <td><code>android4.18.0</code></td>
    </tr>
  </tbody>
</table>

Once you've formatted the SDK version, always send it via a custom request header named `Client-SDK`.  

**Example:**  

If the formatted SDK version is ios4.12.3, then the custom header would be defined in the  
following curl command:  

    curl -X GET \\  
    
    'https://s2s.adjust.com/event?s2s=1&event_token=f0ob4r&app_token=4w565xzmb54d&idfa  
    =D2CADB5F-410F-4963-AC0C-2A78534BDF1E&created_at=2017-01-02T15%3A04%3A0  
    5Z%2B0200&callback_params=%7B%22f0o%22%3A%22bar%22%2C%20%22bar%22%3  
    A%22baz%22%7D&partner_params=%7B%22f0o%22%3A%22bar%22%2C%20%22bar%  
    22%3A%22baz%22%7D' \  
    -H 'Client-Sdk: ios4.12.3'  

## [3\. Import your linked events into Google Ads](import-your-linked-events-into-google-ads)

In Google Ads, a conversion action is a specific user action that you have defined as valuable to your business, such as an online purchase. 

To import your Adjust events into Google Ads as conversion actions, follow [Google Ads' support documentation](https://support.google.com/adwords/answer/7382633). Once imported, Google Ads will begin to send Adjust conversion data for conversion actions.

<callout type="warning">
You must import all relevant conversion actions (both first open and any relevant in-app actions) into Google Ads before launching a Google Ads campaign. 
Adjust cannot report any Google Ads-driven app installs or in-app events until you have completed your import. 
</callout>

## [View your Google Ads data in Adjust](view-your-google-ads-data-in-adjust) 

With Adjust’s Google Ads integration, you can run your campaign and view reported data in the Adjust Dashboard. The campaign information that Adjust reports varies depending on the Google Ads inventory in use. 

<table>
  <thead>
    <tr>
      <th>Adjust tracker level</th>
      <th>Google ads term</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Network</td>
      <td><code>Ads [campaign type] Installs&nbsp;</code></td>
    </tr>
    <tr>
      <td>Campaign</td>
      <td><code>campaign_name (campaign_id)</code><br />
        <ul>
          <li>This comes from your Google Ads dashboard</li>
        </ul>
      </td>
    </tr>
    <tr>
      <td>Adgroup</td>
      <td><code>adgroup_id</code></td>
    </tr>
    <tr>
      <td>Creative</td>
      <td>Depends on the inventory</td>
    </tr>
  </tbody>
</table>

<callout type="note">
Google Ads can occasionally send Adjust an attribution claim without the campaign_type parameter or with the parameter populated with an unknown value. 
When this happens, we attribute the engagement to the tracker Google Ads (unknown).
</callout>

These are the primary ad inventories: ACI, ACPRE, ACE, Shopping, Search, Display, and Video. See below for the campaign structure for each.

### [ACI, ACPRE, and ACE](aci-uacpre-and-ace)

<table>
  <thead>
    <tr>
      <th>Adjust tracker level</th>
      <th>Google Ads term</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Network</td>
      <td><b>For ACI:</b>&nbsp;<br />Google Ads ACI<br /><br /><b>For ACE:&nbsp;</b><br />Google Ads ACE<br /><br /><b>For ACPRE:</b><br />Google Ads Pre-registration</td>
    </tr>
    <tr>
      <td>Campaign</td>
      <td>campaign_name (campaign_id)<br /><br />Example: iOS Google App campaigns test (12345678)</td>
    </tr>
    <tr>
      <td>Adgroup</td>
      <td>adgroup_id<br /><br />Example: 123456</td>
    </tr>
    <tr>
      <td>Creative</td>
      <td>"network_type network_subtype"</td>
    </tr>
  </tbody>
</table>

<callout type="note">
ACI iOS Search inventory doesn't appear in your attribution or ad spend data in Adjust.
</callout>

### [Shopping](shopping)

<table>
  <thead>
    <tr>
      <th>Adjust tracker level</th>
      <th>Google Ads term</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Network</td>
      <td>Google Shopping</td>
    </tr>
    <tr>
      <td>Campaign</td>
      <td>campaign_name (campaign_id)</td>
    </tr>
    <tr>
      <td>Adgroup</td>
      <td>adgroup ID<br /><br />Example: 123456</td>
    </tr>
    <tr>
      <td>Creative</td>
      <td>"network_type network_subtype"</td>
    </tr>
  </tbody>
</table>

### [Search](search-1)

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Adjust tracker level</th>
      <th colspan="1" rowspan="1">Google Ads term</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Network</td>
      <td>Google Ads Search</td>
    </tr>
    <tr>
      <td>Campaign</td>
      <td>campaign_name (campaign_id)</td>
    </tr>
    <tr>
      <td>Adgroup</td>
      <td>adgroup ID, Example: 123456</td>
    </tr>
    <tr>
      <td>Creative</td>
      <td>keyword_matchtype, e.g., hotel_Broad</td>
    </tr>
  </tbody>
</table>

### [Display (GDN, Admob)](display-gdn-admob)

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Adjust tracker level</th>
      <th colspan="1" rowspan="1">Google Ads term</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Network</td>
      <td>Google Ads Display</td>
    </tr>
    <tr>
      <td>Campaign</td>
      <td>campaign_name (campaign_id)</td>
    </tr>
    <tr>
      <td>Adgroup</td>
      <td>adgroup ID, Example: 123456</td>
    </tr>
    <tr>
      <td>Creative</td>
      <td>Placement, Example: mobile_app - 1</td>
    </tr>
  </tbody>
</table>

### [Video (Youtube, Admob)](video-youtube-admob)

<table border="1">
  <thead>
    <tr>
      <th colspan="1" rowspan="1">Adjust tracker level</th>
      <th colspan="1" rowspan="1">Google Ads term</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Network</td>
      <td>Google Ads Video</td>
    </tr>
    <tr>
      <td>Campaign</td>
      <td>campaign_name (campaign_id)</td>
    </tr>
    <tr>
      <td>Adgroup</td>
      <td>adgroup ID, Example: 123456</td>
    </tr>
    <tr>
      <td>Creative</td>
      <td>video_id, Example: 98765456784</td>
    </tr>
  </tbody>
</table>

## [FAQs](faq)

### [How does Adjust track installs with Google Ads?](how-does-adjust-track-installs)

Since API integrations don’t use Adjust tracker URLs, Adjust sends SANs every app session our SDK reports. If Google Ads recognizes the activity, they respond with the device identifier and timestamp. Following our own attribution method, Adjust then uses the engagement data from all networks (including non-SANs) to attribute the install to the last tracked source.

### [Where can I find my LINKID in Google Ads?](where-can-i-find-my-linkid-in-google-ads)

To access your LINKID, follow these steps in Google Ads. 

1.  Navigate to the **Linked accounts** tab and select **App Analytics Platforms**
2.  Once here, you will see a list of your app(s), along with a tracking provider and a LINKID for each
3.  Select the **Copy Link** button to copy your LINKID to your clipboard

Please note that each of your apps should have only one LINKID associated with it on Google Ads. To avoid any confusion, designate one ad account to generate a single LINKID and share this LINKID with all other accounts. 

For details on how to create and share LINKIDs, visit [Google’s Ads support documentation](https://support.google.com/adwords/answer/7365001).

### [How do I set up Adjust tracking for Google organic search?](set-up-adjust-tracking-for-google-organic-search)

__Requirements__

- Business pricing plan
- Adjust SDK 4.27 or higher configured to *always* send the referrer to Adjust 
  - For additional information, see [the Android SDK install referrer information](https://github.com/adjust/android_sdk#install-referrer).   

Google allows mobile users to download apps directly from a Google search. This means that when a search is made from a mobile device, the results can include icons for relevant mobile apps. When a user clicks an app icon, they are redirected to the Google Play Store to download the app. In Adjust, these installs are tracked and recorded as Google organic search and _do not_ count towards your payment plan’s included attributions.  

All installs attributed to Google's organic search will display search keywords at the Campaign level (sublevel 1). 

Adjust can track up to 100,000 search terms for your app, and all keywords can be included in your Adjust install and reattribution callbacks using the `{search_term}` placeholder. This placeholder will be filled with the search query used by the device immediately before clicking on the download link.

### [Why does my Adjust dashboard show fewer installs than Google Ads?](why-does-my-adjust-dashboard-show-fewer-installs-than-google-adwords)

In the case of a reported install discrepancy, it's recommended that you always consider the following.  

- **Different attribution windows** 

If the attribution windows on both platforms are different, you can edit your Adjust attribution windows (**All Settings** \> **Attribution**) to match Google Ads.  

- **Different time zones** 

Confirm that the time zones on both platforms are the same.  

- **Different conversion dates** 

Google Ads reports conversion events as the day of click, while Adjust reports conversions on the day of install (i.e., first app open)  

- **Your acquisition strategy** 

If you are advertising on multiple channels, it is possible that a reported Google Ads user is attributed elsewhere in Adjust.  

Adjust's Google Ads API integration sends all recorded installs to Google Ads. As a self-attributing network, Google Ads responds to Adjust with click data. If Google Ads has a click timestamp record from a user's earlier ad engagement, they report this as an install on the Google Ads dashboard. 

However, as a third-party attribution partner, Adjust considers all tracked inventory and only attributes the user to Google Ads if it is the most recent source of ad engagement (within the applicable attribution window). Therefore, it is possible that a Google Ads-reported user may be attributed elsewhere within Adjust.

With Adjust's Google Ads integration, you can track and analyze the performance of your Google Ads campaigns.  

Set up Google Ads

Adjust offers continued client attribution and ad measurement support for Apple’s iOS 14+ releases with ATT and SKAdNetwork dashboard feature. Adjust offers iOS 14+ support with our latest SDK versions, along with ATT, and SKAdNetwork dashboard features. Follow the next steps to ensure that you have everything in place for iOS 14+ .

## [Steps to support iOS 14](Steps-to-support-iOS-14)

### [1\. Update your SDK](update-your-SDK)

[Adjust’s latest SDK versions](/en/article/sdk-releases) offer support for key parts of Apple’s iOS 14 update. This includes an enhanced number of data points that are used for probabilistic matching, to attribute installs from clicks when the IDFA isn’t available.

<callout type="note">
iOS 14 builds only work in the latest Xcode, although the Adjust SDK is backward compatible with Xcode 11. For new builds, Xcode 12 beta 5 is available from Apple <a href="https://developer.apple.com/download/"> (Read More)</a>.
</callout>

#### [SKAdNetwork](SKAdNetwork) 
<img src="//images.ctfassets.net/5s247im0esyq/4E0nMBylU6Drc4EZtU2eg9/c78f90fe4b1f51407a7f8a73801f6dfa/ka367000000c11b_00Nb0000009tvM7_0EM0X0000038Ysz.png" style="display: inline-block" /> [iOS](https://github.com/adjust/ios_sdk/blob/master/README.md#skadnetwork-framework) / [Unity](https://github.com/adjust/unity_sdk#skadnetwork-framework) / [Cordova](https://github.com/adjust/cordova_sdk/blob/master/README.md#skadnetwork-framework) / [Flutter](https://github.com/adjust/flutter_sdk/blob/master/README.md#af-skadn-framework) / [Titanium](https://github.com/adjust/titanium_sdk/blob/master/README.md#skadn-framework) / [Corona](https://github.com/adjust/corona_sdk#skadnetwork-framework) / [Cocos2d-x](https://github.com/adjust/cocos2dx_sdk#skadnetwork-framework) / [React Native](https://github.com/adjust/react_native_sdk#skadnetwork-framework)

The [SKAdNetwork framework](https://developer.apple.com/documentation/storekit/skadnetwork) is an alternative method used for attribution without access to user-level data. For access to the SKAdNetwork, ad networks must first be registered with Apple. Next, developers must ensure that their apps are compatible with Apple-registered networks and the new framework.

The Adjust SDK has integrated support for the SKAdNetwork and is switched on by default. This means that Adjust will automatically register for SKAdNetwork attribution upon SDK initialization and can handle the conversion value update. You can choose to turn it off.

#### [AppTrackingTransparency (ATT)](AppTrackingTransparency) 
<img src="//images.ctfassets.net/5s247im0esyq/4E0nMBylU6Drc4EZtU2eg9/c78f90fe4b1f51407a7f8a73801f6dfa/ka367000000c11b_00Nb0000009tvM7_0EM0X0000038Ysz.png" style="display: inline-block" /> [iOS](https://github.com/adjust/ios_sdk/blob/master/README.md#apptrackingtransparency-framework) / [Unity](https://github.com/adjust/unity_sdk#apptrackingtransparency-framework) / [Cordova](https://github.com/adjust/cordova_sdk/blob/master/README.md#apptrackingtransparency-framework) / [Flutter](https://github.com/adjust/flutter_sdk/blob/master/README.md#af-att-framework) / [Titanium](https://github.com/adjust/titanium_sdk/blob/master/README.md#att-framework) / [Corona](https://github.com/adjust/corona_sdk#att-framework) / [Cocos2d-x](https://github.com/adjust/cocos2dx_sdk#att-framework) / [React Native](https://github.com/adjust/react_native_sdk#att-framework)

App publishers will need to use Apple’s AppTrackingTransparency framework if their app collects the user’s IDFA and shares it. The ATT framework will present an app-tracking authorization request to the user and the Adjust SDK can track this authorization status. A user can still control privacy at the app level. Users can also block all apps from tracking them at the global level. In iOS 14, block app tracking in the device's **Settings** menu.

#### [Launch an opt-in pop-up via Adjust](Launch-pop-up)

You can use the Adjust SDK wrapper function to present the app-tracking authorization request to users. Optimize your chances of gaining the user opt-in by choosing when to launch the app-tracking authorization request in your app. 

Adjust’s SDK wrapper for the ATT framework means you don’t have to do any extra work to implement Apple’s ATT API. When the wrapper is called the first time, the iOS pop-up launches. Every time after, the wrapper retrieves the tracking authorization status. This is sent to the Adjust backend, and Adjust relays the information directly to you.

### [2\. Placeholder updates](placeholder)

The Adjust placeholder `{att_status}` lets you receive information about how an iOS 14+ user chooses to share their data. Add the placeholder to your callback URL or CSV definition to receive the ATT status in your raw data.

The user status is populated using four (4) possible integer values:

<table>
  <thead>
    <tr>
      <th>Value</th>
      <th>Meaning</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>0 (Not Determined)</td>
      <td>If a user hasn’t yet received an authorization request to allow app-related tracking data.&nbsp;</td>
    </tr>
    <tr>
      <td>1 (Restricted)</td>
      <td>If the authorization to allow app-related tracking data is restricted.</td>
    </tr>
    <tr>
      <td>2 (Denied)</td>
      <td>If the authorization to allow app-related tracking data is denied.</td>
    </tr>
    <tr>
      <td>3 (Authorized)</td>
      <td>If the user gives the authorization to allow app-related tracking data.&nbsp;</td>
    </tr>
  </tbody>
</table>

Adjust changed the behavior of two existing placeholders to assist you with the transition to iOS 14 if you can’t yet switch to use the `{att_status}`. You’ll see this change only if you update to the latest SDK and for your iOS 14.5+ users.

The behavior for `{tracking_enabled}` and `{tracking_limited}` changes in the following way:

<table>
  <thead>
    <tr>
      <th>Placeholder</th>
      <th>Value returned</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>{tracking_enabled}</code></td>
      <td>
        <ul>
          <li dir="ltr">Returns <code>1</code> if the user opt-in status is <b>authorized</b></li>
          <li dir="ltr">Returns <code>0</code> if the user opt-in status is <b>not determined</b>,&nbsp;<b>denied</b>, or <b>restricted</b></li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><code>{tracking_limited}</code></td>
      <td>
        <ul>
          <li dir="ltr">Returns <code>1</code> if the user opt-in status is <b>not determined</b>,&nbsp;<b>denied</b>, or <b>restricted</b></li>
          <li dir="ltr">Returns <code>0</code> if the user opt-in status is <b>authorized</b></li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>


#### Changes to the Limit Ad Tracking (LAT) KPI

Since LAT will be deprecated after iOS 14, Adjust has transitioned how the current KPI behaves in the dashboard. Until you are able to switch to using `{att_status}`, note these changes. 

The LAT KPI is temporarily still visible in the dashboard and filled using the following behavior. 

*   Counts `1` if `att_status` is **restricted**, or **denied**, or **not determined**
*   Counts `0` if `att_status` is **authorized** 

You’ll see this change only if you update to the latest SDK and only for your iOS 14.5+ users.

<callout type="note">
Apple plans to deprecate the Limit Ad Tracking (LAT) setting. This means that if you don’t update to the latest SDK, Adjust sets the LAT value based on whether the IDFA is present. If the IDFA is a string of zeroes, LAT is considered <b>ON</b>.
</callout>

+++>
### iOS 14.0-14.4 only
#### Tracking Placeholders & LAT

#### Changes to `{tracking_enabled}` and `{tracking_limited}` placeholders

Adjust changed the behavior of two existing placeholders to assist you with the transition to iOS 14 if you can’t yet switch to use the `{att_status}`. 

You’ll see this change only for your iOS 14.0-14.4 users.

The behavior for `{tracking_enabled}` and `{tracking_limited}` changes in the following way:

<table border="1"class="no-auto-header">
  <tbody>
    <tr>
      <td><code>{tracking_enabled}</code></td>
      <td>
        <ul>
          <li dir="ltr">Returns <code>1</code> if the user opt-in status is <b>authorized</b>, or<b> not determined</b></li>
          <li dir="ltr">Returns <code>0</code> if the user opt-in status is <b>denied</b>, or <b>restricted</b></li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><code>{tracking_limited}</code></td>
      <td>
        <ul>
          <li dir="ltr">Returns <code>1</code> if the user opt-in status is <b>denied</b>, or <b>restricted</b></li>
          <li dir="ltr">Returns <code>0</code> if the user opt-in status is <b>authorized</b>, or<b> not determined</b></li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

<callout type="note">
Apple plans to deprecate the Limit Ad Tracking (LAT) setting. This means that if you don’t update to the latest SDK, Adjust sets the LAT value based on whether the IDFA is present. If the IDFA is a string of zeroes, LAT is considered <b>ON</b>.
</callout>


#### Changes to the Limit Ad Tracking (LAT) KPI

Since LAT will be deprecated after iOS 14, Adjust is transitioning how the current KPI behaves in the dashboard. Until you are able to switch to using `{att_status}`, note these changes. 

The LAT KPI is temporarily still visible in the dashboard and filled using the following behavior. 

*   Counts `1` if `att_status` is **restricted**, or **denied**
*   Counts `0` if `att_status` is **authorized**, or **not determined**

You’ll see this change only if you update to the latest SDK and only for your iOS 14 users.

+++<


### [3\. Added callback activity: ATT update (iOS)](callback)

To support iOS 14+ changes, Adjust has included a new activity type for callbacks: `ATT update (iOS)`. This is included by default in your global callbacks, which provide a full list of data points from all Adjust-tracked activities. 

Now, when a user’s authorization status changes and you are using global callbacks, user-level data is sent directly to your servers seconds after Adjust tracks the event. To quickly find these events, filter the `{activity_kind}` for att\_update.

For a full overview of how to create global callback URLs, [follow Adjust’s guide to Real-time Callbacks](/en/article/best-practices-callbacks#global).

### [4\. Testing Console support](testing-console-support)

Previously, you could only enter the IDFA to verify raw device activity directly within your Adjust dashboard. The [Testing Console](/en/article/testing-console) now supports the use of IDFV and ADID.


Adjust offers continued client attribution and ad measurement support with Apple’s iOS 14 release. 

iOS 14 User privacy frameworks

[SKAdNetwork](https://developer.apple.com/documentation/storekit/skadnetwork) is Apple’s own attribution framework for app install and reinstall attribution without access to user-level data. This means that Apple performs attribution and notifies the relevant ad network, who then sends a postback with the data to Adjust. Adjust aggregates and reports the data from all your ad networks. 

The Adjust SDK has integrated support for the SKAdNetwork and is switched on by default. This means that Adjust automatically registers for SKAdNetwork attribution upon SDK initialization and can handle the conversion value update. You can choose to turn this functionality off.

You can set up SKAdNetwork conversion value management and event mapping in just a few steps in Adjust. Then, view your aggregated data in the Data Canvas or collect SKAdNetwork raw data to leverage and analyze for campaign optimization. For more information about these features, visit our dedicated guides.

## [Before you begin](before-you-begin)

Here’s what you need to know before getting started. 

**Requirements** 

*   Update your Adjust SDK to v4.23.0+
<img src="//images.ctfassets.net/5s247im0esyq/4E0nMBylU6Drc4EZtU2eg9/c78f90fe4b1f51407a7f8a73801f6dfa/ka367000000c11b_00Nb0000009tvM7_0EM0X0000038Ysz.png" style="display: inline-block" /> [iOS](https://github.com/adjust/ios_sdk/blob/master/README.md#skadnetwork-framework) / [Unity](https://github.com/adjust/unity_sdk#skadnetwork-framework) / [Cordova](https://github.com/adjust/cordova_sdk/blob/master/README.md#skadnetwork-framework) / [Flutter](https://github.com/adjust/flutter_sdk/blob/master/README.md#af-skadn-framework) / [Titanium](https://github.com/adjust/titanium_sdk/blob/master/README.md#skadn-framework) / [Corona](https://github.com/adjust/corona_sdk#skadnetwork-framework) / [Cocos2d-x](https://github.com/adjust/cocos2dx_sdk#skadnetwork-framework) / [React Native](https://github.com/adjust/react_native_sdk#skadnetwork-framework)

*   Admin, Editor, or Custom Editor permissions
*   Confirmation from your Technical Account Manager or a representative at [support@adjust.com](mailto:support@adjust.com) that your app has been internally validated for the SKAdNetwork 

**Helpful information**

*   You can set up SKAdNetwork on your own or with Adjust. When you work with Adjust, you can control everything from your Dashboard and do not need to update your app code to make changes. Your setup method will also determine how you view your conversion value data in Adjust. 
*   For access to the SKAdNetwork, ad networks must first be registered with Apple. Next, developers must ensure that their apps are compatible with Apple-registered networks and the SKAdNetwork framework.

<callout type="tip">
iOS 14 builds only work in the latest Xcode, although the Adjust SDK is backward compatible with Xcode 11. For new builds, Xcode 12 beta 5 is available from <a href="https://developer.apple.com/download/">Apple</a>.
</callout>

## [How it works](how-it-works)

The SKAdNetwork leverages App Store download data to perform attribution. This means there is no device-level data tracked or shared, and that your SKAdNetwork data is separate to your Adjust-tracked data. 

After an install or reinstall, Apple lets you use **conversion values** to identify in-app events triggered by the user, such as completing a level or making a payment. 

The methods described below are Adjust's solutions to managing SKAdNetwork data and conversion values in order to optimize your campaigns. 

+++>
### What is a conversion value?

The conversion value is a 6-bit value. It contains six numeric characters, which can only be 0 or 1. A 6-bit value can take 64 different values: 0 - 63.

<table>
  <thead>
    <tr>
      <th>Decimal</th>
      <th>Binary</th>
      <th>Decimal</th>
      <th>Binary</th>
      <th>Decimal</th>
      <th>Binary</th>
      <th>Decimal</th>
      <th>Binary</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>0</td>
      <td>000000</td>
      <td>16</td>
      <td>010000</td>
      <td>32</td>
      <td>100000</td>
      <td>48</td>
      <td>110000</td>
    </tr>
    <tr>
      <td>1</td>
      <td>000001</td>
      <td>17</td>
      <td>010001</td>
      <td>33</td>
      <td>100001</td>
      <td>49</td>
      <td>110001</td>
    </tr>
    <tr>
      <td>2</td>
      <td>000010</td>
      <td>18</td>
      <td>010010</td>
      <td>34</td>
      <td>100010</td>
      <td>50</td>
      <td>110010</td>
    </tr>
    <tr>
      <td>3</td>
      <td>000011</td>
      <td>19</td>
      <td>010011</td>
      <td>35</td>
      <td>100011</td>
      <td>51</td>
      <td>110011</td>
    </tr>
    <tr>
      <td>4</td>
      <td>000100</td>
      <td>20</td>
      <td>010100</td>
      <td>36</td>
      <td>100100</td>
      <td>52</td>
      <td>110100</td>
    </tr>
    <tr>
      <td>5</td>
      <td>000101</td>
      <td>21</td>
      <td>010101</td>
      <td>37</td>
      <td>100101</td>
      <td>53</td>
      <td>110101</td>
    </tr>
    <tr>
      <td>6</td>
      <td>000110</td>
      <td>22</td>
      <td>010110</td>
      <td>38</td>
      <td>100110</td>
      <td>54</td>
      <td>110110</td>
    </tr>
    <tr>
      <td>7</td>
      <td>000111</td>
      <td>23</td>
      <td>010111</td>
      <td>39</td>
      <td>100111</td>
      <td>55</td>
      <td>110111</td>
    </tr>
    <tr>
      <td>8</td>
      <td>001000</td>
      <td>24</td>
      <td>011000</td>
      <td>40</td>
      <td>101000</td>
      <td>56</td>
      <td>111000</td>
    </tr>
    <tr>
      <td>9</td>
      <td>001001</td>
      <td>25</td>
      <td>011001</td>
      <td>41</td>
      <td>101001</td>
      <td>57</td>
      <td>111001</td>
    </tr>
    <tr>
      <td>10</td>
      <td>001010</td>
      <td>26</td>
      <td>011010</td>
      <td>42</td>
      <td>101010</td>
      <td>58</td>
      <td>111010</td>
    </tr>
    <tr>
      <td>11</td>
      <td>001011</td>
      <td>27</td>
      <td>011011</td>
      <td>43</td>
      <td>101011</td>
      <td>59</td>
      <td>111011</td>
    </tr>
    <tr>
      <td>12</td>
      <td>001100</td>
      <td>28</td>
      <td>011100</td>
      <td>44</td>
      <td>101100</td>
      <td>60</td>
      <td>111100</td>
    </tr>
    <tr>
      <td>13</td>
      <td>001101</td>
      <td>29</td>
      <td>011101</td>
      <td>45</td>
      <td>101101</td>
      <td>61</td>
      <td>111101</td>
    </tr>
    <tr>
      <td>14</td>
      <td>001110</td>
      <td>30</td>
      <td>011110</td>
      <td>46</td>
      <td>101110</td>
      <td>62</td>
      <td>111110</td>
    </tr>
    <tr>
      <td>15</td>
      <td>001111</td>
      <td>31</td>
      <td>011111</td>
      <td>47</td>
      <td>101111</td>
      <td>63</td>
      <td>111111</td>
    </tr>
  </tbody>
</table>

+++<

<asset id="iOS & SKAD - Conversion value mapping scheme" />

### [Updates to the conversion value](updates-to-the-conversion-value)

1. When a user clicks an ad, downloads the app from the App store and opens the app for the first time, the Adjust SDK calls SKAdNetwork to register for attribution.

2. If a specified event is triggered before that timer ends, the conversion value is updated to the value. The timer is then reset for another 24 hours.

3. Once 24 hours pass with no conversion value update, another random timer of up to 24 hours starts. When it ends, Apple sends the final conversion value in a postback to the attributed ad network who then forwards this on to Adjust. 

<callout type="important">
SKAdNetwork attribution data is never shared in real-time. Due to the timer that is activated when a method is called, there will always be a minimum 24-hour period between an install and the postback to the attributed ad network.
</callout>

<asset id="iOS & SKAD - SKAdNetwork flow" />

#### Methods called

<table>
  <thead>
    <tr>
      <th>Method</th>
      <th>Description and instructions</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>registerAppForAdNetworkAttribution()</code></td>
      <td>Verifies the first launch of an app installed as a result of an ad.<br />
        <ul>
          <li><a href="https://developer.apple.com/documentation/storekit/skadnetwork/2943654-registerappforadnetworkattributi">Apple documentation</a></li>
        </ul>
      </td>
    </tr>
    <tr>
      <td><code>updateConversionValue(_:)</code></td>
      <td>Updates the conversion value and verifies the first launch of an app installed as a result of an ad.<br />
        <ul>
          <li><a href="https://developer.apple.com/documentation/storekit/skadnetwork/3566697-updateconversionvalue">Apple documentation</a></li>
        </ul>
      </td>
    </tr>
  </tbody>
</table>

### [Receive SKAdNetwork data](receive-skadnetwork-data)

Networks only receive one SKAdNetwork postback per user and it will include the final, highest conversion value. Be aware that only networks can receive SKAdNetwork postbacks, and these cannot be sent to Adjust or app publishers directly.

To find out more about what data Adjust receives from networks, read our article about [SKAdNetwork partner integrations](/en/article/skadnetwork-partner-integrations).  

## [Manage SKAdNetwork without Adjust](manage-skadnetwork-without-adjust)

If you choose to manage your SKAdNetwork settings yourself, be aware of the following points. 

1.  Your app developers need to call the SKAdNetwork `registerAppForAdNetworkAttribution()` method at app open 
2.  Developers should define what each conversion value means within the app
3.  Adjust only reports the conversion value as it is received from the ad network. This will be a value between 0 - 63 as found in the network payload. 

Example ad network payload: 

<fragment id="Example SKAdNetwork postback to partners" />

Adjust’s support for the SKAdNetwork framework lets you set up SKAdNetwork conversion and event mapping easily in Adjust.

iOS & SKAD - Conversion value mapping scheme

iOS & SKAD - SKAdNetwork flow

SKAdNetwork

Here, you'll find a basic overview and frequently asked questions about Adjust tracker URLs.  

For instructions on creating and managing trackers, see these articles:

*   [Create a tracker URL](/en/article/basic-tracker-setup)
*   [Customize your tracker settings](/en/article/advanced-tracker-setup)
*   [Hide, unhide, or blacklist trackers](/en/article/tracker-maintenance)

## [Tracker URL basics](tracker-url-basics)

Adjust trackers are your foundation for campaign tracking. Use tracker URLs to:

*   Link users to your app in the appropriate app store
*   Record engagement type (clicks or impressions)
*   Segment users by attribution source
*   Redirect users based on device type

Your trackers can live wherever there's mobile engagement—like in-app advertisements, emails, search engine results, social media posts, mobile websites, and more. The placement of the actual tracker URL depends on what channel you use.  

When you create a tracker in Adjust, the [Campaign Wizard](#what-is-the-adjust-campaign-wizard) automatically makes two URLs: a click-based tracker and an impression-based tracker. Each URL includes an Adjust domain (`https://app.adjust.com` for click URLs or `https://view.adjust.com` for impression URLs) and a unique [tracker token](#what-is-an-adjust-tracker-token) created by Adjust (e.g., `abc123`).   

**Example click URL:** 
```
https://app.adjust.com/abc123
```

**Example impression URL:**
```
https://view.adjust.com/impression/abc123
```

These basic tracker URLs track attributions, and you can also customize them to reflect campaign information, pass custom data, redirect users based on device type, and more.  

**Note:** Unsure how to use your tracker URLs? No problem! Feel free to reach out to [support@adjust.com](mailto:support@adjust.com) with your top-level tracker and the details of your intended use case.

### [Campaign structure parameters](campaign-structure-parameters)

You can use campaign structure parameters to see what networks, campaigns, adgroups, and creative content your attributed users engaged with. Like UTM parameters on desktop web URLs, campaign structure parameters on Adjust tracker URLs offer valuable insights into where your mobile users come from.  

Adjust tracker URLs support up to 4 levels of data:  
**network** (top level)**campaign** (sublevel 1)**adgroup** (sublevel 2)**creative** (sublevel 3)**Example top-level tracker URL:**
```
https://app.adjust.com/abc123
```

**Example top-level tracker URL with all three sublevels** (within the query string):
```
https://app.adjust.com/abc123?campaign=Example_CampaignName&adgroup=Example_PublisherID&creative=Example_CreativeID
```

When users engage with your Adjust tracker, your network partners automatically fill in any campaign structure parameters. If you'd rather provide this data yourself, you can hardcode your own data values into your tracker URL.  

Formatting guidelines for campaign structure parameters:

*   Always separate campaign parameters with an ampersand (`&`)
*   Only use lowercase text (e.g., `campaign` instead of `Campaign` or `CAMPAIGN`) — campaign structure parameters are case sensitive
*   Check that campaign structure parameters are spelled correctly (e.g., `adgroup` instead of `adgroups` or `adgrouping`)
*   Follow the hierarchy of sublevels (e.g., a campaign parameter cannot be appended to an adgroup-level tracker). Otherwise, the higher parameter will be ignored and only data at the lowest sublevel tracker will populate.

Helpful information:

*   **Empty campaign structure parameters are `unknown`.** If your tracker URL doesn't include campaign structure parameters, the Adjust dashboard (and all exported reporting) displays the value `unknown`. To make sure similar data points are recorded at the same sublevel, we recommend setting the same values at each parameter across all tracked channels.
*   **Tracker levels are permanent.** Once you create a campaign-level tracker, it can't be edited or renamed to become an adgroup or creative-level tracker.

**Tip:** Use Adjust's [additional parameters](/en/article/advanced-tracker-setup#additional-parameters) to customize your users' experience with your tracker (e.g., deeplinking directly into your app or redirecting to a specific website).

## [Tracker URL FAQs](faq)

### [What is the Adjust Campaign Wizard?](what-is-the-adjust-campaign-wizard)

The Campaign Wizard is where you create and customize tracker URLs within the Adjust dashboard (**All Settings** \> **Trackers**). Whether you're creating a URL to track your own channels or run with an ad network, the Campaign Wizard makes it easy to set data points and design your users' engagement experience.  

Use the Campaign Wizard to:

*   Structure your campaigns within Adjust’s four-tier hierarchy, from the top level down to your lowest sublevel
*   Add deeplinks to direct your users to a specific page within your app
*   Append redirect or fallback URLs to send users to different web destinations
*   Set tracker-level attribution settings (down to the adgroup sublevel) to decide exactly how and when your users are attributed/reattributed
*   Track ad spend with any network that supports cost data

**Note:** Some features may not be available with your current Adjust package. Cost features are available with a Business Pro (or higher) pricing plan, and tracker-level attribution settings are available with an Enterprise (or higher) pricing plan.

### [What is an Adjust tracker token?](what-is-an-adjust-tracker-token)

Adjust automatically creates a unique identifying string (e.g., `abc123`) for every Adjust tracker. These tracker tokens contain 6 or more alphanumeric characters and appear at the end of your tracker URLs.  

**Example top-level tracker URL:**
```
https://app.adjust.com/abc123
```
Here, the tracker token is `abc123`.  

**Example tracker URL with appended Adjust parameters**
```
https://app.adjust.com/xyz4567?label=user_id&deeplink=myapp%3A%2F%2Flanding_page_promotion&redirect=https%3A%2F%2Fmywebsite.com
```
Here, the tracker token is `xyz4567`. It still appears at the end of the top-level URL (before the query string starting with `?`).  

**Note:** Click and impression URLs for the _same tracker_ include the same unique tracker token.

### [How are click tracker URLs and impression tracker URLs different?](difference-between-tracker-impression-tracker) 

Click and impression URLs redirect to two separate, independently-operated Adjust server endpoints. This helps maintain the integrity of your attribution data, since clicks and impressions use different attribution windows. Use click URLs for your click-based campaigns, and impression URLs for your view-through campaigns.

### [Are my Adjust trackers for retargeting different than my trackers for user acquisition?](trackers-for-retargeting-and-user-acquisition)

Adjust trackers operate the same way for all campaigns. However, because retargeting focuses on specific customers, your tracker should always include a user's [advertising ID](/en/article/device-identifiers#advertising-ids). This lets you know your campaign is reaching the right audience.

*   **iOS Example:**

```
https://app.adjust.com/abc123?idfa=8A3CB124-5A79-4334-8802-F75FEC099C58
```

*   **Android Example:**

```
https://app.adjust.com/abc123?gps_adid=38400000-8cf0-11bd-b23e-10b96e40000d

```

### [Can I track QR codes with Adjust?](can-i-track-qr-codes)

Of course! Tracking QR codes with Adjust is simple and helps you leverage the full power of attribution across all of your marketing channels. The aggregated data is displayed in the dashboard and can be filtered like other networks. Fundamentally, the QR code operates in just the same way as any other ad your users see. A device’s camera reads the QR code like a URL: every time a code is scanned and read, it works like a click on a link in the device’s default browser. 

To get started with tracking and receiving attribution data from QR codes, first [create a tracker URL](/en/article/basic-tracker-setup#create-tracker-url) in the Adjust dashboard. Then, use a [QR code generator](http://goqr.me/) to create your QR code. Enter your Adjust tracker URL into the space provided. QR codes can also easily be used as deeplinks to provide a seamless user experience, sending users straight into your app or via an app store. Simply generate your deeplink tracker in the Adjust dashboard and add it to the QR code generator like any other tracker URL.


Here, you'll find a basic overview and frequently asked questions about Adjust tracker URLs.  

Adjust tracker URLs

Most Popular Articles

Are you ready for iOS 14.5? Learn about Adjust's Attribution Privacy Models here.

How can we help you?

Most Popular Articles