v0 and LinkedIn Ads integration: Step-by-Step Guide 2025

 

Preparing Global TypeScript Declarations

 

To ensure the TypeScript compiler recognizes the global variables used by LinkedIn’s Insight Tag, create a new file named custom.d.ts in your project’s root directory and insert the following code:

declare interface Window {
    lintrk: any;
    linkedindatapartnerids: string[];
}

Place this file at the root of your v0 project so the compiler automatically picks it up.

 

Creating the LinkedIn Ads Integration File

 

Create a new file named linkedinAds.ts in your project’s source folder. This file will contain functions to load the LinkedIn Insight Tag script and to track events. Insert the following code:

export function loadLinkedinInsightTag(partnerId: string): void {
    // Initialize the global array if it does not exist
    window.linkedindatapartnerids = window.linkedindatapartnerids || [];
    window.linkedindatapartnerids.push(partnerId);

    // Create the global lintrk function if it is not yet defined
    if (typeof window.lintrk !== "function") {
        window.lintrk = function (action: string, data: any) {
            (window.lintrk.q = window.lintrk.q || []).push([action, data]);
        };
    }

    // Dynamically load the LinkedIn Insight Tag script
    const script = document.createElement("script");
    script.type = "text/javascript";
    script.async = true;
    script.src = "https://snap.licdn.com/li.lms-analytics/insight.min.js";
    document.getElementsByTagName("head")[0].appendChild(script);
}

export function trackLinkedinEvent(eventName: string, payload?: any): void {
    if (typeof window.lintrk === "function") {
        window.lintrk('track', eventName);
    } else {
        console.warn("LinkedIn tracking function not available yet.");
    }
}

This file defines two functions:

• loadLinkedinInsightTag: Initializes the LinkedIn partner ID, ensures the tracking function exists, and dynamically injects the LinkedIn script into your page.
• trackLinkedinEvent: Calls the LinkedIn tracking function to record a specific event (you can extend this with additional payload data if needed).

 

Integrating the LinkedIn Integration into Your Main Code

 

Locate your project’s main entry file (typically named app.ts or main.ts) and import the integration functions. Then, call the loadLinkedinInsightTag function while initializing your application. Insert the following snippet at the top level of your initialization code:

import { loadLinkedinInsightTag, trackLinkedinEvent } from "./linkedinAds";

// Replace 'YOURPARTNERID' with your actual LinkedIn partner ID
const LINKEDINPARTNERID = "YOURPARTNERID";

// Load the LinkedIn Insight Tag when the application starts
loadLinkedinInsightTag(LINKEDINPARTNERID);

// Example usage: tracking a sample event when a specific action occurs
function onUserAction() {
    trackLinkedinEvent("UserActionEvent");
}

// For demonstration purposes, simulate a user action after some time
setTimeout(onUserAction, 5000);

Ensure that the import path (./linkedinAds) correctly reflects where the linkedinAds.ts file is saved relative to your main file. This code initializes LinkedIn’s tracking when your application loads and demonstrates how to track an event.

 

Adding a Noscript Fallback to Your HTML

 

Since the LinkedIn Insight Tag also requires a fallback for users with JavaScript disabled, open your project’s main HTML file (often named index.html) and add the following snippet just before the closing tag:

<noscript>
    <img height="1" width="1" style="display:none;" alt=""
         src="https://px.ads.linkedin.com/collect/?pid=YOURPARTNERID&fmt=gif" />
</noscript>

Make sure to replace "YOURPARTNERID" with your actual partner ID.

 

Verifying the Integration

 

• Reload your application in a web browser.
• Inspect the page source and console to ensure the LinkedIn Insight Tag script is loaded successfully.
• Monitor your browser’s network activity for a successful load of the LinkedIn script from "https://snap.licdn.com/li.lms-analytics/insight.min.js".
• Trigger any defined events (such as the simulated user action) to confirm that event tracking works as expected.