Expand my Community achievements bar.

SOLVED

s.t() and s.tl() Server Calls (Adobe Experience Platform Debugger and Google Developer Tools Console)

Avatar

Level 5

Hi All,

 

Can someone provide how to see s.t() and s.tl() Server Calls in both Adobe Experience Platform Debugger and Google Developer Tools Console?

 

Thanks!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor and Adobe Champion

Hi, 

 

I am going to assume you have at least basic familiarity with both tools (i.e. the Platform debugger showing all the dimensions and additional information about the calls, and filtering the Adobe calls by "b/ss" in the network panel).

 

In the platform debugger you will see the dimensions as the full names (i.e. "prop1", "eVar1", etc), and if you are logged in, you will even see the names that have been applied to your suite in Adobe (i.e. "prop1 - some name", "eVar1 - some other name", etc).

 

In the Network panel, you will see the URL designations, c# are used for props (c1 = prop1, c2 = prop2...), v# is used for eVars (v1 = eVar1, v2 = eVar2....), you will also see l# for lists and h# for hierarchies, g is your URL, ch is your channel/site section.

 

The way you can tell a s.t() call from an s.tl() call, is the inclusion of the pev values (page events):

  • pe = page event (this will be lnk_o for custom links, lnk_e for exit links, and lnk_d for downloads)
  • pev1 = the link URL (this will be used for exit links report, but hidden for custom and download links, which defer to pev2 value)
  • pev2 = link name

 

In the Platform debugger, you will see them referred to as link Name (pev2), Link Type (pe) and Link URL (pev1):

Jennifer_Dungan_0-1723044281386.png

 

 

On page views, these will be empty, on clicks / actions / etc using the s.tl() call, these will have values passed.

 

View solution in original post

7 Replies

Avatar

Correct answer by
Community Advisor and Adobe Champion

Hi, 

 

I am going to assume you have at least basic familiarity with both tools (i.e. the Platform debugger showing all the dimensions and additional information about the calls, and filtering the Adobe calls by "b/ss" in the network panel).

 

In the platform debugger you will see the dimensions as the full names (i.e. "prop1", "eVar1", etc), and if you are logged in, you will even see the names that have been applied to your suite in Adobe (i.e. "prop1 - some name", "eVar1 - some other name", etc).

 

In the Network panel, you will see the URL designations, c# are used for props (c1 = prop1, c2 = prop2...), v# is used for eVars (v1 = eVar1, v2 = eVar2....), you will also see l# for lists and h# for hierarchies, g is your URL, ch is your channel/site section.

 

The way you can tell a s.t() call from an s.tl() call, is the inclusion of the pev values (page events):

  • pe = page event (this will be lnk_o for custom links, lnk_e for exit links, and lnk_d for downloads)
  • pev1 = the link URL (this will be used for exit links report, but hidden for custom and download links, which defer to pev2 value)
  • pev2 = link name

 

In the Platform debugger, you will see them referred to as link Name (pev2), Link Type (pe) and Link URL (pev1):

Jennifer_Dungan_0-1723044281386.png

 

 

On page views, these will be empty, on clicks / actions / etc using the s.tl() call, these will have values passed.

 

Avatar

Level 5

Hi @Jennifer_Dungan ,

 

Is there documentation to what each of the letters and digit categories mean in the Network b/ss payload query string parameters for Adobe Debugging? In addition to that, also which map to which Workspace Adobe Out-of-Box Metrics?

Avatar

Level 3

@skatofiabah,

 

For understanding the Network b/ss payload query string parameters used in Adobe Debugging, I usually refer to this page from the Experience League:

Link to Adobe Documentation

 

This page provides details on various query string parameters Adobe uses in image requests. While it may not explicitly define each letter and digit category, it offers a valuable starting point for understanding their functionality.

 

Let's see if anyone else has insights on mapping these parameters to specific Adobe Out-of-Box Metrics.