|
| 1 | +--- |
| 2 | +title: LinkedIn Conversions API |
| 3 | +id: 652e765dbea0a2319209d193 |
| 4 | +beta: true |
| 5 | +--- |
| 6 | + |
| 7 | +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. |
| 8 | + |
| 9 | +This destination is maintained by Segment. For |
| 10 | + |
| 11 | +## Getting started |
| 12 | + |
| 13 | +1. From the Segment web app, click **Catalog**, then click **Destinations**. |
| 14 | +2. Search for “LinkedIn Conversions API” in the Destinations Catalog, and select the destination. |
| 15 | +3. On the LinkedIn Conversions API overview page, click **Add destination**. |
| 16 | +4. Select the source that you want to connect to the LinkedIn Conversions API and click **Next**. |
| 17 | +5. Enter a name for your destination and click **Create destination**. |
| 18 | +6. On the Settings tab, click Connect to `[destination-name]` and follow the prompts to authenticate with LinkedIn using OAuth. |
| 19 | +6. Enable the destination and click **Save Changes**. |
| 20 | + |
| 21 | +### Set up a mapping to Stream Conversion Events |
| 22 | + |
| 23 | +1. On the Mappings tab, click on **+ New Mapping** and Select **Stream Conversion Event**. |
| 24 | +2. Select the events you'd like to map and send to your LinkedIn Conversions API destination. |
| 25 | +3. Create A Conversion Rule or enter a link to an existing rule. |
| 26 | + |
| 27 | +> warning "Ad account link cannot be updated" |
| 28 | +> After you provide a link to your LinkedIn Ad account in this step, you cannot update the Ad account without creating a new LinkedIn Conversions API destination. |
| 29 | +
|
| 30 | +<ol style="counter-reset: none;"> |
| 31 | + <li value="4" markdown=1> |
| 32 | + Configure the mappings to map event fields and user attributes from your source to the Conversion API. |
| 33 | + </li> |
| 34 | + <li value="5" markdown=1> |
| 35 | + Click **Save**. |
| 36 | + </li> |
| 37 | +</ol> |
| 38 | + |
| 39 | +{% include components/actions-fields.html %} |
| 40 | + |
| 41 | +## FAQ and troubleshooting |
| 42 | + |
| 43 | +### Why are my inputs failing? |
| 44 | + |
| 45 | +Your inputs must meet the following criteria: |
| 46 | +- Contains a valid URN with the following format: <br> `urn:lla:llaPartnerConversion:id` |
| 47 | +- The authenticated user must have write access to the ad account used to create conversion rules |
| 48 | +- Contains a userInfo combination that requires firstName and lastName **OR** a userId mapped to at least one of the following idTypes: |
| 49 | + - `SHA256_EMAIL` |
| 50 | + - `LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID` |
| 51 | + - `ACXIOM_ID` |
| 52 | + - `ORACLE_MOAT_ID` |
| 53 | +- `conversionHappenedAt` must be a valid timestamp (milliseconds since epoch) and must have happened in the past 90 days |
| 54 | + |
| 55 | +Any deviations from this specification might lead to failed inputs. |
0 commit comments