Partilhar via

Conversions FAQ

  • Artigo

Warning

Deprecation Notice
The Marketing Version 202401 (Marketing January 2024) has been sunset. We recommend that you migrate to the versioned APIs as well as migrate to the new Content and Community Management APIs to avoid disruptions. See the Migration page for more details. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.

  1. When to use Conversions API?

    • To strengthen your existing conversion tracking, you can use the Conversions API and the Insight Tag together to measure and optimize both online and offline events across your customer journey.
    • You need a secure way to connect data to LinkedIn without relying on cookie-based tracking.

  2. What type of events can I send through conversions API?
    You can send both online and offline conversion events through the Conversions API. A complete list of supported conversions is available here.

  3. How often should I share data? Why is it important to send data in real time?
    Conversions should be sent in real time as soon as they occur, or ideally within a day. Sending data in real time ensures that the data can be attributed and utilized by the campaign while it is fresh and relevant. For customers using a LinkedIn Marketing Partner, this near real-time sharing should happen automatically.

  4. Are there any minimums to the number of attributed conversions we will show in reporting?
    Currently, there are no minimums.

  5. How long does it take to process events sent through conversions API and see reporting for those events?
    It takes up to 24 hours to complete ingestion and an additional 48 hours for reporting; hence, it can take up to 72 hours for complete data to appear in reports.

  6. How far back can we attribute conversions?
    Conversions can be attributed for up to a maximum of 180 days. There is a 90-day lookback for each conversion, and the conversion must have occurred within the last 90 days to be attributed.

  7. What is deduplication?
    Deduplication is the process by which the system identifies the same event sent from both the Insight Tag and Conversions API and discards one to ensure accurate counting. It enables you to send the same events through both sources, allowing the Conversions API to work in tandem with your Insight Tag to provide maximum visibility into the conversions your campaigns are driving.

  8. How do I implement deduplication?
    Review the detailed guide here.

  9. Is there a max data load I can send via conversions API?
    Yes, you can send a maximum of 500 requests per minute through your member access token and up to 5000 events per batch request payload.

  10. What are match rates?
    Once the conversion data is sent to LinkedIn, we search for members who were served your ad and either clicked or viewed it within the attribution window set for the conversion. The match rate indicates how effectively we can match conversion events to LinkedIn members. This is important because we can only attribute conversions to members we successfully match.

  11. What are customer parameters? Why do they matter?
    Sending additional customer parameters (also known as user IDs) can help increase match rates. In general, the more IDs you send with each event, the more likely we are to match it to a member. This is important because only matched events can be used for attribution and optimization. Examples of recommended customer parameters include email (SHA256_EMAIL) and LinkedIn's Click ID (LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID).

  12. What customer parameters (also known as user IDs) does conversions API support?
    The Conversions API supports the following: SHA256_EMAIL, LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, ACXIOM_ID, ORACLE_MOAT_ID, firstName, lastName, companyName, title, countryCode, leadGenFormResponse, and externalIds. Please refer to the API documentation for the most up to date list.

  13. Which parameters (user IDs) are required?
    An input request must provide at least one of the following:

    • A valid user ID with idType SHA256_EMAIL
    • A valid user ID with idType LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID
    • A valid user ID with idType ACXIOM_ID
    • A valid user ID with idType ORACLE_MOAT_ID
    • A valid user info combination that requires firstName and lastName We recommend sending both SHA256 EMAIL and LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID for the best matching.

  14. How do I hash identifiers?
    The Conversions API supports hashed emails using SHA-256 without salting.

  15. Is it recommended to convert emails to lower case before hashing them? Yes, it is recommended to convert emails to lowercase before hashing them for better match rates.

  16. What is LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID?
    LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, also known as li_fat_id, is LinkedIn's first party cookie click ID. When enhanced conversion tracking is enabled, LinkedIn automatically adds a click ID to the end of landing page URLs, which allows the tag to use first-party cookie tracking. Enabling first party cookies via enhanced conversion tracking allows you to send this click ID as a parameter for improved conversion tracking accuracy. This helps increase match rates significantly.

  17. How do I enable first party cookies so I can use LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID?
    Check out Enabling Click IDs developer docs. How you choose to set this up will influence which type of conversions (click-through, view-through, or both) you're able to track.

  18. What are the implementation options for conversions API?

    1. Leverage a partner integration: Choose from a variety of LinkedIn Marketing Partners to quickly and seamlessly set up with the Conversions API, such as Google Tag Manager, Zapier, Dreamdata, Supermetrics, Tealium, and Adobe. Refer to the relevant partner's onboarding guide to get started.
    2. Build a direct integration: Work with your developers to build a direct integration with Conversions API.

  19. How do the two implementation options compare?

    • Leverage a partner integration
      • The partner helps facilitate the API connection
      • One-time setup with limited technical effort required from your team
      • May have associated fees that vary by partner
      • Typically fast to implement
    • Build a direct integration
      • Manage your own API connection
      • Offers the most customization and control over data sharing
      • Requires developer resources and ongoing maintenance
      • Implementation can take 2-4 weeks on average

  20. How do I apply for the Conversions API?

    1. Create a new developer application in the Developer Platform (if you/your company does not have an existing developer application with LinkedIn)
    2. Apply to the Conversions API under the Products tab of your app
    3. You can review the full set of steps here.