How to set up LinkedIn Conversions API [Step-by-step guide]

แชร์
ฝัง
  • เผยแพร่เมื่อ 28 ธ.ค. 2024

ความคิดเห็น • 25

  • @Monirul_IslamBD
    @Monirul_IslamBD 6 หลายเดือนก่อน +2

    thanks for the video. Really informative

  • @leffiafan
    @leffiafan 2 หลายเดือนก่อน

    Hi, thank you for your guide.
    LinkedIn updated CAPI and there is no button "Generate Token" anymore. (Timecode 08:10) How should I generate the token for sgtm?

    • @Stape
      @Stape  2 หลายเดือนก่อน

      Hi.
      Linkedin has changed its interface since the video was recorded.
      Unfortunately, it is not possible to update the video as quickly as the platform interfaces are updated.
      Please follow these instructions to generate a token:
      Analyse menu section -> Sources -> Google tag manager -> Generate token

  • @happymakingresults
    @happymakingresults 2 หลายเดือนก่อน

    Hi, thanks for your guide.
    Do i need to have a 2 Purchase event I LinkedIn, one with the conversion and one with the Server conversion? or can I just have one tag in the server GTM that fires with trigger: Client = GA4?

    • @Stape
      @Stape  2 หลายเดือนก่อน

      You need to have two conversions on Linkedin. One for web and one for server source and accordingly you should have a tag on the web that works for the conversion and a tag on the server that works for the required conversion.

  • @dobromirtodorov2399
    @dobromirtodorov2399 5 หลายเดือนก่อน

    Thanks for the tutorial. Since the pageview event for LinkedIn in SSGTM doesn't have event id parameter, how does the duplication works?

    • @Stape
      @Stape  5 หลายเดือนก่อน

      The LinkedIn Conversion API pageview event is specifically created to store the LinkedIn click ID URL parameter into a li_fat_id cookie, even if the LinkedIn browser pixel is blocked. This event does not send a pageview event; it simply sets the cookie when the LinkedIn pixel is blocked. Meaning that there won't be any problem with the deduplication.

  • @dommergaard
    @dommergaard 6 หลายเดือนก่อน

    Thanks for a steady flow of videos this month. Can you do one for ActiveCampaign and Klaviyo too? (:

    • @Stape
      @Stape  6 หลายเดือนก่อน

      yes, definitely. we have ActiveCampaign and Klaviyo in our backlog

    • @dommergaard
      @dommergaard 6 หลายเดือนก่อน

      @@Stape perfect! Do you know when it is ready, and which new videos can we expect in june/july?

    • @Stape
      @Stape  6 หลายเดือนก่อน

      @@dommergaard Videos about email platforms (Active Campaign, Klaviyo, etc.) should be done this autumn. We are currently recording videos about offline conversion tracking for Facebook and Google. These should be released in July.

  • @digitalravi8891
    @digitalravi8891 3 หลายเดือนก่อน

    Great video, as you have created web and server side events on linkedin with different purchase name so does they will get deduplicated using event Id or purchase will be count in both event on LinkedIn?

    • @Stape
      @Stape  3 หลายเดือนก่อน +1

      LinkedIn deduplicates events based on the event_id. To avoid overreporting, you should send an identical event ID with the web and server events. The web event has a higher priority and will be counted as a conversion, and if the same conversion with the same event ID is delivered via CAPI, such an event will be discarded.

  • @EmirElezovic-fi6dg
    @EmirElezovic-fi6dg 5 หลายเดือนก่อน

    Might have missed this but is it possible to add the (dynamic) purchase value to the linkedin conversion? I didn't see it show up in your GTM previewmode and LinkedIn Conversion tracking overview.

    • @Stape
      @Stape  5 หลายเดือนก่อน +1

      You can add dynamic purchase value using the amount property inside the Event Data Override of the LinkedIn CAPI tag in the GTM.

    • @EmirElezovic-fi6dg
      @EmirElezovic-fi6dg 5 หลายเดือนก่อน

      @@Stape Thank you very much! This solved my issue. Great video!

  • @thibaultwalter9165
    @thibaultwalter9165 2 หลายเดือนก่อน

    Thanks you for this helpful tutorial ! I've been following all the tutorial step by step, the tags are fired correctly both in web and server container. My conversions are in statut "Active" inside LinkedIn Ads Manager. However the deduplication isn't working, I have 2 differents unique event id between the tags on web and server container (the 2 last number changed).
    Example : I have a tag call "Demo submit". When I'm testing my setup, both tags are firing in web and server container but the unique event id are different which create duplication.
    Any thoughts on this ?
    Thanks in advance

    • @Stape
      @Stape  2 หลายเดือนก่อน

      Thank you for your feedback.
      Please check that you are using the Unique event ID variable in the web tags and the event data variable with Key Path event_id in the server tag.
      If this is the case and you still have an incorrect event id, please write to Stape support at support@stape.io with the tags and triggers settings. Also, please provide information on what you are using as a transport for Linkedin conversions.

    • @Stape
      @Stape  2 หลายเดือนก่อน

      This problem can also occur if you use tag sequencing.

    • @thibaultwalter9165
      @thibaultwalter9165 2 หลายเดือนก่อน

      @@Stape Thanks for your answer. I don't use tag sequencing neither in the web gtm or the sgtm container. Even if the unique event ID aren't identicals for a given conversion action in web and server container, can I still use the conversion action from the server container to optimise my LinkedIn Ads campaigns ? I see that my conversion action from server is in statut "Active". I did a conversion test, the statut of my tag from server is in 201 and I capture user-data in SHA256 correctly.

  • @jeromechevreau5879
    @jeromechevreau5879 5 หลายเดือนก่อน

    Do you need to implement 2 purchase? one via the insight tag conversion and the other via CAPI? Why is that necessary?

    • @Stape
      @Stape  5 หลายเดือนก่อน

      yes, it's better to configure CAPI and insight tag in parallel, but in this case, you need to configure deduplication to prevent overreporting.
      The two main reasons for configuring both CAPI and Insight tag are: CAPI works when Insight tag is blocked (because of ad blcokers or issues with scripts), which increases the accuracy of conversion tracking and potentially improves the results of your paid campaigns. Also with CAPI, you can send offline events to LinkedIn, such as leads from CRM, phone calls, etc.

  • @JimmyTheCloudDev
    @JimmyTheCloudDev 5 หลายเดือนก่อน

    While following this guide, my tags are firing but failing.
    Context: Instead of doing a purchase event, we're firing when an email sign up trigger fires.
    In our debugger console, we're getting, "You must set 1 out of the 4 acceptable IDs... to resolve this issue"
    I didn't notice of one of those ID's being set in this video. What am I missing?

    • @Stape
      @Stape  5 หลายเดือนก่อน +1

      LinkedIn requires sending one of the following parameters: learn.microsoft.com/en-us/linkedin/marketing/integrations/ads-reporting/conversions-api?view=li-lms-2024-06&tabs=http#idtype. Adding one of those should resolve the issue. We usually add either email or click ID parameters.

    • @JimmyTheCloudDev
      @JimmyTheCloudDev 5 หลายเดือนก่อน

      @@Stape Thank you for responding so quickly!