getting Started
Overview
The LinkedIn Conversions API establishes a direct connection between advertisers' servers and LinkedIn, enabling them to measure the performance of their LinkedIn marketing campaigns, regardless of where conversions occur. This data can be used to optimize campaign performance. The Conversions API helps improve performance and reduce cost per operation by providing more complete attribution analysis, greater data reliability, and optimized delivery methods.
condition
Account ID | LinkedIn Ad Account ID |
Token ID or conversion ID mapping + Access Token One set of the above two sets is provided. | CDP Authorized Account Token ID Alternatively, a comma-separated mapping of conversion IDs to event names (e.g., LEAD=22285180) plus a LinkedIn Access Token. |
The conversion ID and access token can be obtained as shown in the image:
In LinkedIn Ads Campaign Manager , select Direct API on the right side under Data - Signals manager .
The diagram indicates that the corresponding event conversion ID and access token can be obtained respectively.
Configuration
Scenario 1: Account opening application from NAS, i.e., Topkee's advertising account.
Step 1. Use the following unified token ID: 590708082141560832
Step 2. Select the corresponding event
Scenario 2: Directly using the Direct API access token
Step 1. Log in to your LinkedIn account and generate an access token.
Step 2. Manually create a conversion event, obtain the conversion ID, and set it in the ConversionID Mapping field.
Step 3. Select the corresponding event
Note: In this scenario, the API can only send events and cannot automatically create conversion tags. Scenario 1 is recommended.
Transformation problem
1. How much data can be sent via the Conversions API?
You can send up to 600 requests per minute and up to 300,000 requests per day using your member access token. For bulk requests, each bulk request load can contain up to 5,000 conversion events.
2. What is the longest timeframe that a conversion event can be traced back to?
Conversion events can be traced back up to 180 days. Each conversion event has a 90-day retrospective period, and the conversion event must have occurred within the past 90 days to be attributable.
3. How long does it take for events sent via the Conversions API to be processed?
Complete and generate the corresponding report? Data import can take up to 24 hours, and report generation can take another 48 hours; therefore, complete data may take up to 72 hours to appear in the report.
For other common conversion issues, please refer to : Common Conversion Issues and Answers
