Integrating LinkedIn Ads with SHOPLINE
To help merchants run remarketing and conversion campaigns on LinkedIn, SHOPLINE supports two integration methods: the LinkedIn Insight Tag (for client-side tracking) and the Conversions API (CAPI) (for server-side tracking). Both tools allow you to sync user behavior data with the LinkedIn Ads system.
This guide will walk you through how to configure both the Insight Tag and CAPI, the types of events supported, and how to view server-side event status in your admin panel.
Integration Methods
You can integrate LinkedIn Ads with your SHOPLINE store using two primary methods for comprehensive event tracking:
- Insight Tag: This enables frontend event tracking by capturing user actions directly from your website.
- Conversions API (CAPI): This supports more robust, server-side tracking by sending event data directly from your server to LinkedIn.
Setting Up the Insight Tag (Partner ID)
The Insight Tag is LinkedIn’s frontend tracking tool. It captures user browsing and click behavior for ad performance analysis and building remarketing audiences.
-
Log in to LinkedIn Campaign Manager. Click Measurement > Conversion tracking in the left menu.
-
Click Create conversion and select Insight Tag conversion.
-
Choose Manual conversions setup and expand the Insight Tag code section.
-
Copy the Partner ID (the number following linkedin_partner_id=).
-
Set the trigger to Page load, and enter the URLs for the desired conversion pages (e.g., product page, order success page).
-
Click Next step to complete and save the setup.
-
Return to SHOPLINE Admin. Go to Channels > LinkedIn, then click Configure Partner ID in the Client-Side reporting section.
-
Paste the copied Partner ID and click Save.
Once configured, SHOPLINE will automatically deploy the Insight Tag across your site to enable frontend tracking.
Notes:
|
Setting Up the Conversions API (CAPI)
To ensure more stable and accurate event tracking, we recommend also setting up LinkedIn’s server-side integration, the Conversions API. Follow the steps below to complete the configuration:
- Log in to LinkedIn Campaign Manager.
-
Go to Data > Signals manager. Under Sources, click Direct API.
-
In the Direct API access token section, click Generate access token.
- Copy the token.
-
Return to SHOPLINE Admin. Go to LinkedIn > Server-Side reporting, and click Configure CAPI.
-
Paste the access token. The system will automatically retrieve your ad accounts. Select the one you'd like to use for attribution.
- Click Save to complete the configuration.
SHOPLINE will then automatically read the Conversion Rules from your LinkedIn ad account and map the corresponding events. These mappings will be visible on the admin panel.
Note: If the correct ad account is not selected, events will fail to match with the Conversion Rules and will not be properly attributed. |
Supported Events & Limitations
While LinkedIn supports a wide range of event types, SHOPLINE currently supports the following standard e-commerce events:
Event Name | Trigger Description |
ViewContent | User views a product detail page |
AddToCart | User clicks the "Add to Cart" button |
InitiateCheckout | User enters the checkout process |
Purchase | User completes the order and payment |
Lead | User submits a form (e.g., subscription form) |
CompleteRegistration | User completes the registration process |
AddPaymentInfo | User adds payment details |
Search | User performs a search |
Viewing Server-Side Event Status (CAPI Only)
SHOPLINE allows you to view the status of CAPI events in the admin panel, so you can confirm whether events have been successfully uploaded. The interface displays:
- Enabled event types (e.g., ViewContent, Purchase)
- Conversion Rule binding status (displays "Unbound" if no rule is matched)
- Timestamp of the most recent upload
- Upload status (Success / Failure) and failure reason (e.g., missing fields)
- Whether event format meets requirements (e.g., email encryption, correct timestamp format)
Note: Since the Insight Tag is loaded and reported directly by LinkedIn, SHOPLINE cannot monitor its event status. As a result, frontend events will not appear in the admin panel. |