How to Connect LinkedIn Conversions API with Perspection for B2B Tracking

How do you connect Perspection to LinkedIn Conversions API?

Connecting Perspection to LinkedIn Conversions API requires navigating to Connectors in the Perspection dashboard, selecting the LinkedIn destination card, entering 3 required credential fields (Ad Account ID, Access Token, and Conversion Rule ID), saving the configuration, and running the built-in connection test to confirm API access to the LinkedIn Marketing API version 202402.

Follow these steps to connect Perspection to the LinkedIn Conversions API:

1. Log in to the Perspection dashboard at dashboard.perspection.app and select the workspace where LinkedIn conversions should be sent.

2. Navigate to Connectors in the left sidebar, then select the Destinations tab.

3. Locate the LinkedIn destination card, labeled "Conversions API" beneath the LinkedIn logo.

4. Click the LinkedIn card to expand the configuration form.

5. Enter all 3 required credential fields (detailed in the credentials section below).

6. Optionally enter the Organization ID to associate conversions with a specific LinkedIn Company Page.

7. Optionally enter a Conversion ID if the conversion mapping differs from the Conversion Rule ID.

8. Optionally enter a Partner ID if the LinkedIn account operates through a LinkedIn Marketing Partner.

9. Click Save to store the configuration.

10. Click Test to validate API connectivity. Perspection sends a GET request to https://api.linkedin.com/rest/adAccounts/{ad_account_id} with the provided Access Token and the LinkedIn-Version: 202402 header. Perspection returns a success or failure message with response latency in milliseconds.

11. Once the test passes, toggle the Live switch to activate event dispatch.

After activation, Perspection begins dispatching conversion events to LinkedIn in real time. The destination card displays a health status badge: Live (healthy), Degraded (intermittent errors), or Down (persistent failures). For a detailed explanation of health status monitoring across all destinations, see Guide 17: Destination Health Monitoring.

Required Credentials

1. Ad Account ID (ad_account_id)

   • Format: Numeric string (e.g., 512345678).

   • Where to find: Open LinkedIn Campaign Manager and log in to the advertising account. Navigate to Account Settings. The Ad Account ID appears in the account overview section and in the Campaign Manager URL as a numeric identifier.

   • Important: The Ad Account ID must belong to the account that owns the conversion rules. Perspection uses the Ad Account ID to validate the connection by calling the LinkedIn Ad Accounts REST endpoint.

2. Access Token (access_token)

   • Format: String starting with AQV (e.g., AQVxxxxxxxx...).

   • How to generate: Open the LinkedIn Developer Portal and navigate to the registered application. Generate an OAuth 2.0 token with the following scopes:

     • r_ads -- Read access to advertising accounts

     • rw_conversions -- Read and write access to conversion events

     • r_ads_reporting -- Read access to ad reporting (recommended for verification)

   • Token lifetime: LinkedIn OAuth 2.0 access tokens expire after 60 days. Perspection does not currently auto-refresh LinkedIn tokens. Set a calendar reminder to regenerate and update the Access Token in Perspection before the 60-day expiration.

   • Reference: LinkedIn Marketing API -- Conversions API Authentication

3. Conversion Rule ID (conversion_rule_id)

   • Format: LinkedIn URN format (e.g., urn:lla:llaPartnerConversion:123456).

   • Where to find: In LinkedIn Campaign Manager, navigate to Analyze then Conversion Tracking. Select the conversion rule that should receive server-side events. Copy the Conversion Rule ID from the rule details panel. The Conversion Rule ID follows the URN format urn:lla:llaPartnerConversion:{numeric_id}.

   • Prerequisite: The conversion rule must be created in LinkedIn Campaign Manager before configuring Perspection. LinkedIn supports conversion rules for URL-based conversions, event-specific conversions, and custom conversions. For server-side tracking with Perspection, create an event-specific conversion rule.

   • Reference: LinkedIn Help -- Conversion Tracking

Optional Credentials

4. Organization ID (account_id)

   • Format: Numeric string (e.g., 12345678).

   • Where to find: Navigate to the LinkedIn Company Page. The Organization ID appears in the page URL as linkedin.com/company/{organization_id}.

   • When needed: The Organization ID associates conversion events with a specific LinkedIn Organization. Useful for advertisers managing multiple Company Pages under a single advertising account.

5. Conversion ID (conversion_id)

   • Format: Numeric string (e.g., 123456).

   • When needed: Required only when mapping specific event types to different conversion actions within LinkedIn. If the Conversion ID is not provided, Perspection uses the Conversion Rule ID for all dispatched events.

6. Partner ID (partner_id)

   • Format: Numeric string (e.g., 123456).

   • When needed: Required only when the LinkedIn advertising account operates through a LinkedIn Marketing Partner or agency. The Partner ID enables partner-level attribution reporting.

What data does Perspection send to LinkedIn?

Perspection sends conversion events to the LinkedIn Conversions API at https://api.linkedin.com/rest/conversions with the Conversion Rule ID, Unix-millisecond timestamp, conversion value with currency code, a unique event ID for deduplication, SHA-256-hashed email and phone arrays for identity matching, the LinkedIn First-Party Ad Tracking UUID (li_fat_id) for click attribution, and an external ID for cross-platform stitching.

Payload structure

Perspection constructs each LinkedIn conversion payload with the following structure:

{
  "elements": [
    {
      "conversion": {
        "conversionHappenedAt": 1740672000000,
        "conversionValue": {
          "currencyCode": "USD",
          "amount": "2499.00"
        },
        "eventId": "evt_abc123-def456-ghi789"
      },
      "user": {
        "userInfo": {
          "hashedEmails": ["a1b2c3d4e5f6..."],
          "hashedPhoneNumbers": ["f6e5d4c3b2a1..."],
          "linkedinFirstPartyAdsTrackingUUID": "li_fat_id_value"
        },
        "userIds": {
          "dmpUuids": ["customer-12345"]
        }
      }
    }
  ],
  "conversionRuleId": "urn:lla:llaPartnerConversion:123456"
}

{
  "elements": [
    {
      "conversion": {
        "conversionHappenedAt": 1740672000000,
        "conversionValue": {
          "currencyCode": "USD",
          "amount": "2499.00"
        },
        "eventId": "evt_abc123-def456-ghi789"
      },
      "user": {
        "userInfo": {
          "hashedEmails": ["a1b2c3d4e5f6..."],
          "hashedPhoneNumbers": ["f6e5d4c3b2a1..."],
          "linkedinFirstPartyAdsTrackingUUID": "li_fat_id_value"
        },
        "userIds": {
          "dmpUuids": ["customer-12345"]
        }
      }
    }
  ],
  "conversionRuleId": "urn:lla:llaPartnerConversion:123456"
}

{
  "elements": [
    {
      "conversion": {
        "conversionHappenedAt": 1740672000000,
        "conversionValue": {
          "currencyCode": "USD",
          "amount": "2499.00"
        },
        "eventId": "evt_abc123-def456-ghi789"
      },
      "user": {
        "userInfo": {
          "hashedEmails": ["a1b2c3d4e5f6..."],
          "hashedPhoneNumbers": ["f6e5d4c3b2a1..."],
          "linkedinFirstPartyAdsTrackingUUID": "li_fat_id_value"
        },
        "userIds": {
          "dmpUuids": ["customer-12345"]
        }
      }
    }
  ],
  "conversionRuleId": "urn:lla:llaPartnerConversion:123456"
}

Event filtering

Perspection selectively dispatches only conversion-relevant events to LinkedIn. The LinkedIn connector processes 6 event types and skips all other events:

Events outside the 6 conversion types -- including page_view, session_start, identify, and custom behavioral events -- return a success response with a skip message (e.g., "Event page_view skipped - not a conversion event for LinkedIn"). The selective filtering prevents LinkedIn from receiving non-conversion signals that would dilute conversion rule accuracy.

Identity matching signals

Perspection sends 4 identity signals to LinkedIn for user matching, listed in order of matching strength:

1. LinkedIn First-Party Ad Tracking UUID (li_fat_id): The strongest identity signal for LinkedIn attribution. Perspection extracts the li_fat_id from the click_ids vault using a triple-fallback pattern: JSONB click_ids column, individual database columns, and event properties. The li_fat_id is a first-party cookie set when a user clicks a LinkedIn ad and lands on the advertiser's website. Perspection also checks for a linkedin_uuid field in the user data payload.

2. Hashed email addresses (hashedEmails): SHA-256-hashed email addresses sent as an array. LinkedIn uses hashed email for deterministic identity matching against LinkedIn member profiles. Perspection's browser SDK automatically captures and hashes email from form submissions, and the processing pipeline propagates the hashed email through identity resolution.

3. Hashed phone numbers (hashedPhoneNumbers): SHA-256-hashed phone numbers sent as an array. LinkedIn uses hashed phone as a secondary deterministic matching signal.

4. External ID (dmpUuids): A persistent user identifier -- such as a CRM customer ID or account number -- passed through the Perspection identify() call. Perspection sends the external ID in the dmpUuids array, which LinkedIn uses for Data Management Platform cross-referencing.

API request headers

Perspection sends every LinkedIn API request with 3 required headers:

Rate limiting and retry behavior

The LinkedIn Conversions API enforces a rate limit of 500 calls per hour per application. Perspection tracks the rate limit counter internally and returns a rate limit error when remaining capacity reaches zero, re-queuing the event for dispatch after the rate limit window resets.

For transient failures (HTTP 5xx and 429 status codes), Perspection retries with exponential backoff using the following parameters:

• Maximum retries: 3

• Base delay: 500 milliseconds

• Backoff multiplier: 2x per attempt (500ms, 1000ms, 2000ms)

Non-retriable errors (HTTP 4xx) are logged with the full LinkedIn API error response and routed to the Dead Letter Queue (DLQ) for investigation.

Conversion value and currency

When a conversion event includes a monetary value (e.g., a purchase amount), Perspection sends the value in the conversionValue object with a currencyCode and amount string. Perspection extracts the currency code using a 3-source fallback: event properties.currency, then custom_data.currency, then the workspace default currency. If no currency is configured at any level, Perspection defaults to USD.

For B2B advertisers tracking high-value conversions (enterprise software subscriptions, annual contracts), passing accurate conversion values enables LinkedIn's Value Optimization bidding strategy, which prioritizes ad delivery to users likely to generate the highest conversion value rather than the highest conversion volume.

How do you verify LinkedIn conversion events?

Verify LinkedIn conversion delivery by checking 3 locations: the Perspection dashboard Connectors page for the Live health badge and Test button result, the Perspection workspace Sent Data tab for per-event dispatch status and latency, and LinkedIn Campaign Manager's Conversion Tracking panel under Analyze for conversion count, value, and attribution window alignment.

Follow the verification sequence below after activating the LinkedIn destination:

Step 1: Run the Perspection connection test

1. Navigate to the Perspection dashboard workspace and open Connectors then Destinations.

2. Expand the LinkedIn destination card.

3. Click the Test button. Perspection sends a GET request to the LinkedIn Ad Accounts endpoint to validate the Access Token and Ad Account ID.

4. Perspection displays "Connection test successful!" with response latency (typically 200-500ms for the LinkedIn API), or the specific LinkedIn API error message if the connection fails.

5. Confirm the destination card shows a Live health status badge.

Step 2: Trigger a test conversion

1. Open the website connected to the Perspection workspace in a separate browser tab.

2. Perform a tracked conversion action -- for example, submit a lead form (triggers lead), complete a sign-up (triggers sign_up), or complete a purchase (triggers purchase).

3. Return to the Perspection dashboard and open the Sent Data tab.

4. Locate the LinkedIn dispatch entry for the test event. Confirm the entry shows a "Success" status.

5. If the entry shows a "Failed" status, expand the error message for the full LinkedIn API error details.

Step 3: Verify in LinkedIn Campaign Manager

1. Open LinkedIn Campaign Manager and select the advertising account.

2. Navigate to Analyze then Conversion Tracking.

3. Select the specific conversion rule configured in Perspection (matching the Conversion Rule ID).

4. Review the conversion count and conversion value columns.

5. Note: LinkedIn may take up to 24 hours to reflect newly uploaded conversions in Campaign Manager reporting. The conversion status should show "Active" with recent conversion activity.

Step 4: Monitor Event Match Quality

1. In the Perspection dashboard, navigate to the workspace analytics view.

2. Review the Event Match Quality (EMQ) metrics for LinkedIn-dispatched events. For a complete explanation of EMQ scoring, weights, and optimization strategies, see Guide 16: Event Match Quality.

3. LinkedIn conversion matching relies primarily on hashed email. A missing email address is the single most impactful gap for LinkedIn attribution. Ensure Perspection SDK identify() calls capture email at login, registration, and form submission touchpoints.

Troubleshooting common issues

• "LinkedIn API error (401): Unauthorized": The Access Token has expired (LinkedIn tokens expire after 60 days) or lacks the rw_conversions scope. Regenerate the Access Token in the LinkedIn Developer Portal with the correct scopes and update the credential in Perspection.

• "LinkedIn API error (403): Forbidden": The Access Token does not have permission to write to the specified Ad Account. Verify the LinkedIn application has the rw_conversions permission and the token-generating user has admin access to the Ad Account in Campaign Manager.

• "Rate limit exceeded (500 calls/hour)": The LinkedIn Conversions API enforces a 500-call-per-hour rate limit. Perspection automatically re-queues rate-limited events for delivery after the rate limit window resets. High-volume advertisers dispatching more than 500 conversion events per hour should contact Perspection support to discuss batching optimization.

• Conversions not appearing in Campaign Manager: Allow up to 24 hours for LinkedIn reporting lag. If conversions still do not appear after 24 hours, verify the Conversion Rule ID matches the correct conversion rule in Campaign Manager. Ensure the Conversion Rule ID follows the URN format urn:lla:llaPartnerConversion:{numeric_id}.

• Low match rate on LinkedIn conversions: LinkedIn relies heavily on hashed email for identity matching. Unlike Meta (which uses FBP/FBC cookies) or Google Ads (which uses GCLID), LinkedIn matching depends on the advertiser capturing the user's email address. Implement Perspection SDK identify() calls at every email capture point to maximize LinkedIn match rates.

Methodology

All LinkedIn Conversions API configuration steps in this guide were verified against the Perspection production dashboard and LinkedIn Campaign Manager as of February 2026.

"For B2B advertisers, the single highest-impact action for LinkedIn Conversions API attribution is capturing email at every conversion touchpoint -- demo request forms, content downloads, webinar registrations, and free trial sign-ups. LinkedIn's identity graph relies on hashed email as the primary matching signal, far more than browser cookies or click IDs. Advertisers who combine Perspection's server-side email hashing with first-party domain tracking for li_fat_id persistence consistently see 85-95% conversion attribution rates on LinkedIn, compared to 55-65% with the browser-based Insight Tag alone. The attribution lift is especially pronounced for enterprise sales cycles exceeding 14 days, where Safari ITP cookie expiration would otherwise erase the click-to-conversion link entirely." -- Perspection Engineering Team

Sources and References

1. LinkedIn Marketing API -- Conversions, https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api

2. LinkedIn Campaign Manager Help, https://www.linkedin.com/help/lms

3. Perspection Product Guide -- Event Match Quality, /library/event-match-quality-guide

4. Perspection Product Guide -- Destination Health, /library/destination-health-failed-events-guide