LinkedIn Conversions Connector Setup Guide
This article describes how to set up the LinkedIn Conversions connector.
The LinkedIn Conversions API (CAPI) is a conversion tracking tool that creates a direct connection between marketing data from an advertiser’s server and LinkedIn. This integration enables advertisers to measure the performance of their LinkedIn marketing campaigns no matter where the conversion happens and use this data to power campaign optimization. The Conversions API can help strengthen performance and decrease cost per action with more complete attribution, improved reliability, and optimized delivery.
API information
This connector uses the following vendor API:
- API Name: LinkedIn API
- API Version: 202406
- API Endpoint:
https://api.linkedin.com/rest
- Documentation: LinkedIn: Conversions API
Connector actions
Action Name | AudienceStream | EventStream |
---|---|---|
Stream Conversion Event | ✗ | ✓ |
Batch Conversion Events | ✗ | ✓ |
Configure settings
Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see About Connectors.
After adding the connector, configure the following settings:
- Ad Account: Required. Select an ad account ID that aligns with your sponsored account.
Deduplication
Deduplication is the ability for the system to identify the same event being sent from both the Insight Tag and CAPI, and then discard one to ensure proper counting. Deduplication enables you to send the same events through both sources, allowing CAPI to work in tandem with your LinkedIn Insight tag to provide maximum visibility into the conversions your campaigns are driving.
To configure this connector action to receive event IDs from the LinkedIn Insights tag in your iQ Tag Management account, look for event attributes using the following naming convention:
linkedin_event_id_<Conversion ID>_<TAG UID>
For example linkedin_event_id_11563522_123
.
Your Conversion ID can be found in your LinkedIn Campaign Manager account while configuring your LinkedIn Insights tag to track a specific event:
- Navigate to Analyze > Conversion Tracking.
- Select Create Conversion > Conversions API or CSV depending upon your use case. For more information, see LinkedIn: Conversion Tracking.
- Select the integration and enter the required Settings values, including the Key Conversion Behavior that you want to track.
- Select Next Step.
- Select any campaigns to be tracked.
- From the left side menu, select Analyze > Insight Tag.
- Click I will use a tag manager and copy the partner ID listed on the page.
- After all required forms are created and you have copied your Partner ID value, click Create .
Automatic deduplication
When the Automatic Deduplication value is set, the connector looks for the corresponding variable within the UDO object. You are no longer required to add an Event ID if this section is populated and you are using Tealium iQ. However, the following approach may still be needed when using EventStream without Tealium iQ.
The connector uses the following order of operations:
- If Automatic Deduplication is set, and the value is found in the data layer, (for example,
linkedin_event_id_10501014_30
) and this value supersedes any mapping for Event ID. - If Automatic Deduplication is set, but the value is not found, the mapped Event ID is used, if it is set.
Create a conversion
You can use Tealium to create a Conversion Event to be tracked within your Campaign Manager interface. Creating a conversion within Tealium negates the need to configure a conversion event for tracking within the LinkedIn Campaign Manager. These values will be used to track the conversion events and be used to associate the conversion event values with campaigns being run. These will appear in the Analyze > Conversion Tracking section. The events will appear with a data source value of Tealium
when viewing within the LinkedIn Campaign Manager platform.
Field / parameter | Description | Example and/or Type |
---|---|---|
Account (account ) |
The Sponsored Ad Account URN that this conversion resides under. This can be either specified in URL query parameter or in the request JSON body. | urn:li:sponsoredAccount:1234567 URN |
Name (name ) |
Short name for this rule, which will be shown in the UI and in reports. | Summer_Sale CRM Conversions / string |
Enabled (enabled ) |
Set to true or false to enable or disable this rule from matching conversions. The initial state can be either, but only rules that are enabled will trigger conversion events. Default is true . |
true |
Post Click attribution window size (postClickAttributionWindowSize ) |
Conversion window timeframe (in days) of a member clicking on a LinkedIn Ad (a post-click conversion) within which conversions will be attributed to a LinkedIn ad. Allowed values are 1 , 7 , 30 , or 90 . Default is 30 |
90 (integer) |
Attribution Type (attributionType )Parameter values:
|
The model that describes how conversion actions are to be counted:
|
Drop-down supporting both of the values in the left section:
|
Type (type ) |
Type of conversion to track for this conversion rule:
|
Associate campaigns to conversions
It is important to associate the conversion events that are generated to the required campaign values. These conversion events can have a one-to-many relationship with LinkedIn campaigns that are running. Tealium will also retrieve conversion events for population into the actions that are to be mapped. Use the Associate Campaigns to Conversions overlay to map your Conversions to Campaigns. After you select your Conversion and Campaign values, select Create Association and wait for the Success message to appear.
Parameter | Description |
---|---|
Conversion | Required. Select the conversion or provide conversion ID as a custom text. |
Campaign | Required. Select the campaign or provide campaign ID as a custom text. |
Actions
The connector’s actions are used to send the contact information from the conversion to LinkedIn.
Enter a name for the action and select the action type from the drop-down menu.
The following section describes how to set up parameters and options for each action.
Stream Conversion Event
Parameters
You must send at least one of the following parameters: Email Address, LinkedIn First Party Ads Tracking UUID, Axciom ID, Oracle Moat ID, or First Name and Last Name. If you send any user information (for example: Company, Title, or Country Code), you must include the First Name and Last Name parameters, regardless if you provide other identity parameters.
Parameter | Description |
---|---|
Conversion | Select the conversion rule created through the API. Conversion ID can be provided as a custom text. |
Email Address (already SHA256 hashed) | Provide an email address that is a plain text and has been already SHA256 hashed. |
Email Address (apply SHA256 hash) | Provide a plain text email address and the connector will trim blank space, lowercase, and hash this value using SHA256 hash. |
LinkedIn First Party Ads Tracking UUID | First Party Cookie ID. Advertisers need to enable enhanced conversion tracking from Campaign Manager in order to activate first-party cookies that appends a Click ID parameter li_fat_id to the click URLs. |
Axciom ID | User identifier for matching with LiveRamp identity graph. |
Oracle Moat ID | User identifier for matching with Oracle Moat Identity. |
First Name | The first name of the contact to match the conversion. Required if Company, Title, or Country Code attributes are populated. |
Last Name | The last name of the contact to match the conversion. Required if Company, Title, or Country Code attributes are populated. |
Company | Represents the company of the contact to match. |
Title | Title name of the contact to match. |
Country Code | ISO standardized two letter country code representing the country of the contact. |
Conversion Time | Epoch timestamp in milliseconds at which the conversion event happened. If not mapped, it will be initialized with the current timestamp. |
Conversion Amount | The monetary value for this conversion. Required to send conversionValue object. |
Currency Code | Currency code in ISO format. Required to send conversionValue object |
Event ID | The unique ID generated by advertisers to indicate each event. This field will be used for deduplication. |
Batch Conversion Events
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following thresholds is met:
- Max number of requests: 1000
- Max time since oldest request: 10 minutes
- Max size of requests: 1 MB
Parameters
You must send at least one of the following parameters: Email Address, LinkedIn First Party Ads Tracking UUID, Axciom ID, Oracle Moat ID, or First Name and Last Name. If you send any user information (for example: Company, Title, or Country Code), you must include the First Name and Last Name parameters, regardless if you provide other identity parameters.
Parameter | Description |
---|---|
Conversion | Select the conversion rule created through the API. Conversion ID can be provided as a custom text. |
Email Address (already SHA256 hashed) | Provide an email address that is plain text and has been already SHA256 hashed. |
Email Address (apply SHA256 hash) | Provide a plain text email address and the connector will trim blank space, lowercase, and hash this value using SHA256 hash. |
LinkedIn First Party Ads Tracking UUID | First Party Cookie ID. Advertisers need to enable enhanced conversion tracking from Campaign Manager in order to activate first party cookies that appends a Click ID parameter li_fat_id to the click URLs. |
Axciom ID | User identifier for matching with LiveRamp identity graph. |
Oracle Moat ID | User identifier for matching with Oracle Moat Identity. |
First Name | The first name of the contact to match the conversion. Required if Company, Title, or Country Code attributes are populated. |
Last Name | The last name of the contact to match the conversion. Required if Company, Title, or Country Code attributes are populated. |
Company | Represents the company of the contact to match. |
Title | Title name of the contact to match. |
Country Code | ISO standardized two letter country code representing the country of the contact. |
Conversion Time | Epoch timestamp in milliseconds at which the conversion event happened. If not mapped, it will be initialized with the current timestamp. |
Conversion Amount | The monetary value for this conversion. Required to send conversionValue object. |
Currency Code | Currency code in ISO format. Required to send conversionValue object. |
Event ID | The unique ID generated by advertisers to indicate each event. This field will be used for deduplication. |
Vendor documentation
This page was last updated: August 27, 2024