> ## Documentation Index
> Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn Ads Destination

> Track LinkedIn ad conversions from your storefront with Upstack Data — automatic event mapping, click-ID capture, and identity enrichment.

<Note>
  **Data direction:** This is a **destination** — Upstack sends event and conversion data **out** to this platform via server-side APIs.
</Note>

## What it does

Upstack tracks LinkedIn through the **LinkedIn Insight Tag** on your storefront. Upstack captures storefront events — page views, product views, add-to-carts, checkouts, and purchases — and reports them to LinkedIn with the `li_fat_id` click identifier attached, so LinkedIn can tie conversions back to the ads that drove them.

<Note>
  You only need your **Partner ID** to set this up. See [How to configure the LinkedIn destination](/destinations/catalog/linkedin/how-to-configure-linkedin-destination-in-upstack-data).
</Note>

## Tracking Method

<Note>
  LinkedIn currently receives events from the browser only. See [Tracking Method](/concepts/tracking-method) for more details.
</Note>

## How it works

The Upstack Pixel captures each event on your storefront and enriches it with identity and click-ID data. Upstack then loads the LinkedIn Insight Tag and reports the event to LinkedIn.

Because Upstack owns the event capture, every LinkedIn event carries the same identity data as the rest of your tracking — you do not maintain a separate Insight Tag or a second set of event mappings.

## Setup guides

<CardGroup cols={2}>
  <Card title="Onboarding guide" icon="route" href="/destinations/catalog/linkedin/complete-how-to-guide-for-onboarding-linkedin-in-upstack-data">
    End-to-end walkthrough for connecting LinkedIn to Upstack Data.
  </Card>

  <Card title="Configure destination" icon="sliders" href="/destinations/catalog/linkedin/how-to-configure-linkedin-destination-in-upstack-data">
    Configure the LinkedIn destination inside Upstack Data.
  </Card>

  <Card title="Find Partner ID" icon="magnifying-glass" href="/destinations/catalog/linkedin/how-to-find-linkedin-partner-id">
    Locate your LinkedIn Partner ID in Campaign Manager.
  </Card>

  <Card title="Enable click ID tracking" icon="link" href="/destinations/catalog/linkedin/how-to-enable-linkedin-click-id-tracking">
    Enable enhanced conversion tracking for `li_fat_id` click IDs.
  </Card>
</CardGroup>

## Event mapping

Upstack maps storefront events to LinkedIn standard events automatically:

| Upstack event                            | LinkedIn event   |
| ---------------------------------------- | ---------------- |
| `PageView`                               | `PAGE_VIEW`      |
| `ViewContent`                            | `VIEW_CONTENT`   |
| `AddToCart`                              | `ADD_TO_CART`    |
| `AddToWishlist`                          | `ADD_TO_LIST`    |
| `InitiateCheckout`                       | `START_CHECKOUT` |
| `Purchase`, `NC Purchase`, `RC Purchase` | `PURCHASE`       |
| `Search`                                 | `SEARCH`         |
| `Lead`                                   | `LEAD`           |
| `SignUp`, `CompleteRegistration`         | `SIGN_UP`        |
| `Subscribe`                              | `SUBSCRIBE`      |
| `Contact`                                | `CONTACT`        |

PII is hashed with SHA-256 before it leaves Upstack. Upstack includes every available match key on every event — hashed `email`, `li_fat_id` (LinkedIn click ID), `ip_address`, and `user_agent` — to maximise match quality.

## FAQ

<AccordionGroup>
  <Accordion title="What is the Partner ID?">
    The **Partner ID** is the numeric identifier for your LinkedIn ad account's Insight Tag. You'll find it in Campaign Manager → **Data** → **Signals Manager**. It is the only LinkedIn credential the destination needs.
  </Accordion>

  <Accordion title="Do I need to keep my own Insight Tag on the storefront?">
    No. Upstack loads the Insight Tag for you once the destination is configured. If you already load it through your theme, Google Tag Manager, or another app, remove that copy — two tags with the same Partner ID can double-count events.
  </Accordion>

  <Accordion title="What if my event match rate is low?">
    LinkedIn's match rate depends on how much identity data each event carries. Common causes of low match quality:

    * **Missing `li_fat_id`** — enable click ID tracking so the identifier is captured from the landing-page URL.
    * **Anonymous visitors** — events from visitors without an email have fewer keys to match against. Match rates improve as more identified customers convert.
    * **Missing checkout fields** — make sure your Shopify checkout collects email.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Events not appearing in Campaign Manager">
    If events aren't appearing after 10 minutes of confirmed store traffic, check the basics first.

    **Steps to fix:**

    1. Go to **Event Destinations → LinkedIn Ads**
    2. Verify the **Partner ID** is correct — numeric, no extra spaces
    3. Confirm the destination status is **Healthy**
    4. In Campaign Manager, check **Data → Signals Manager → Signal Diagnostics** for events with status "Received"
  </Accordion>

  <Accordion title="Events appear, but conversions aren't attributed to ads">
    Attribution needs the `li_fat_id` click ID, which is captured from the landing-page URL.

    **Steps to fix:**

    1. Click one of your live LinkedIn ads and confirm `li_fat_id` appears in the destination URL
    2. Check that the ad links directly to your storefront rather than through a redirect that strips query parameters
    3. See [How to enable LinkedIn click ID tracking](/destinations/catalog/linkedin/how-to-enable-linkedin-click-id-tracking)
  </Accordion>
</AccordionGroup>

<Note>
  For additional troubleshooting beyond LinkedIn-specific issues, see [Troubleshooting: Events Not Reaching Destination](/troubleshooting/destination-shows-disconnected).
</Note>

## Related

<CardGroup cols={2}>
  <Card title="Identity resolution" icon="fingerprint" href="/pixel/identity-resolution">
    How Upstack matches anonymous visitors to known customers for higher match rates.
  </Card>

  <Card title="Verify events" icon="circle-check" href="/quickstart/verify-events">
    Confirm events are firing from your storefront before checking the destination.
  </Card>

  <Card title="Events not reaching destination" icon="wrench" href="/troubleshooting/destination-shows-disconnected">
    End-to-end diagnostic guide when events aren't arriving at any destination.
  </Card>

  <Card title="All destinations" icon="grid-2" href="/destinations/catalog">
    Every destination Upstack can send events to.
  </Card>
</CardGroup>