Custom link tracking with First party cookie | Community
Skip to main content
abhishek_kumar1-1
abhishek_kumar1-1
October 16, 2015
Solved

Custom link tracking with First party cookie

  • October 16, 2015
  • 2 replies
  • 1603 views

Hi, 

Recently, I was working on custom link tracking on client site. The site support first party cookie. I have used s.tl() method to track link name clicked by a user and i see the data in site catalyst. 

onclick="

s_sitecatalyst.tl("true", 'o', '<Link name>');"

I am getting data from the above implementation also. The above code can be used on site which accepts 3rd party cookie or 1st party cookie.

But i am wondering, how does first party cookie will affect custom link tracking. Like shown below- 

    onclick="    

        s.linkTrackVars = "trackingServer,trackingServerSecure";
        s_sitecatalyst.trackingServer="<your url >";
        s_sitecatalyst.trackingServerSecure="<url >";
        s_sitecatalyst.tl("true", 'o', '<Link name>');"

The above code i have found in knowledge base. This can be used only if your site accepts first party cookie.

I am sure we will be getting data in both ways but what is the main difference in data collection ? 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by apowersadobe

    Hi Abhishek,

    A first-party cookie implementation sets s.trackingServer and s.trackingServerSecure within its s_code file. If the s object already exists on the page, then it will not generally be necessary to re-specify these values within s.tl() calls. In most cases, the s object is created on page load as the s_code file is loaded, so you will not need to follow this example in most cases. More generally speaking, calling s.t() or s.tl() just sends data to the 3rd- or 1st-party server as specified, with no other effect on execution beyond the destination server.

    Andy

    2 replies

    apowersadobe
    Adobe Employee
    apowersadobeAdobe EmployeeAccepted solution
    Adobe Employee
    October 16, 2015

    Hi Abhishek,

    A first-party cookie implementation sets s.trackingServer and s.trackingServerSecure within its s_code file. If the s object already exists on the page, then it will not generally be necessary to re-specify these values within s.tl() calls. In most cases, the s object is created on page load as the s_code file is loaded, so you will not need to follow this example in most cases. More generally speaking, calling s.t() or s.tl() just sends data to the 3rd- or 1st-party server as specified, with no other effect on execution beyond the destination server.

    Andy

      abhishek_kumar1-1
      abhishek_kumar1-1Author
      October 16, 2015

      Thanks Andy for your response. 

      Terms & ConditionsAccessibility statement

      Loading footer...