At a glance: Web SDK is a simplified and refined version of cookie-less tracking that can be easily generated from the panel by following a few simple steps.
In today’s fast-evolving digital marketing environment, accurate and efficient tracking plays a vital role. Trackier’s Web SDK provides a robust solution for seamless integration and improved data collection directly from web pages. This lightweight implementation enables capturing key user interactions and conversions with higher precision and flexibility, helping optimise overall performance.
Using this approach, you have the ability to add pixels either directly in the code or through GTM. This will provide more precise tracking in situations where certain browsers do not support third-party cookies, without any constraints or limitations.
How is WebSDK different from the S2S postback method?
The Web SDK works through a JavaScript script placed on the website. It tracks user actions directly from the browser, such as page visits, sign-ups, or purchases. Since it depends on the user’s browser and page load, it is generally easier to implement.
On the other hand, S2S (Server-to-Server) Postback works by sending conversion information directly from your server to Trackier’s server after the desired action is completed. It requires storing the Trackier click ID and passing it back in the postback.
Video to watch
Understanding WebSDK
Trackier Web SDK tracking works through two components: a static script and a conversion pixel. The static script is added to every landing page, while the Web SDK conversion pixel is added only to the thank you page.
Whenever a user lands on the first landing page, the static script is automatically triggered. At this stage, it captures and stores important tracking information related to that user, such as the click_id and other unique details required for attribution. Because the same static script is present on all landing pages, it is triggered each time the user moves between pages, ensuring that the tracking information remains available throughout the user journey.
Once the user completes the desired action, such as making a purchase or submitting a form, they are redirected to the thank-you page. The Web SDK conversion pixel placed on this page is then triggered. This pixel reads the tracking information that was previously stored by the static script and sends the complete conversion data to Trackier. In this way, the entire user journey—from the initial click to the final conversion—is accurately tracked and attributed.
Below are the steps to follow in order to implement web sdk
Step 1: Update the campaign URL
To implement the web SDK, it is mandatory to include the below-mentioned parameters in the campaign URL and also for all landing pages.
utm_campaign=trackier_{camp_id}&click_id={click_id} |
Step 2: Placement of static code
It is mandatory to add the below script to all landing pages. This script will make sure we get the session ID or click ID even when the browser or device doesn't support third-party cookies.
This is the script tag that needs to be placed in the <BODY> tag of the website.
Static code/script :
<script src="https://static-cdn.trackier.com/js/trackier-websdk-init.js"></script>
Step 3: Placement of thank you page pixel
We have two options for the thank-you page pixel:
Web sdk
Web SDK for GA
Note:
For a Brand account, you only need to select Trackier Web SDK.
For a Network account, you can choose either Trackier Web SDK or Web SDK for GA.
Trackier web SDK
This pixel will be placed in the body tag of the Thank You page and will be activated on the transaction's thank you page.
This pixel can be generated from your panel by opening the campaign from the manage campaign section, going to the conversion tracking section, and selecting campaign or advertiser trackier Websdk depending on your needs.
Note:-
Advertiser Trackier WebSDK -We recommend using this only in cases when advertiser is not comfortable with adding pixels multiple times.
Campaign Trackier WebSDK- The Campaign Trackier WebSDK is only valid for a specific campaign. We recommend using the campaign level websdk for easier access to the Pixel log in case of an issue, instead of having to navigate to the advertiser's pixel logs.
Your system will automatically add your account's domain and adv_unique id in your web SDK code.
Enable UTM Campaign check
If you are selecting trackier web SDK option in the tracking link section, then you have to enable the UTM campaign check toggle from the basic campaign settings to ensure seamless tracking on both ends.
Web SDK for GA ( Highly recommended )
This pixel will be placed in the body tag of the Thank You page and will be activated on the transaction's thank you page.
This pixel can be generated from your panel by opening the campaign from the manage campaign section. Navigate to the Conversion tracking section, check the Web SDK for GA check box, and then fetch the specified pixel.
Your system will automatically add your account's domain and adv_unique ID in your web SDK code.
Note :
--> If the init() script ( static code ) is not placed, then you can face multiple challenges in tracking, such as:
GA numbers mismatch
Discrepancy in tracking of iOS devices
Tracking challenges in the Incognito tab and Safari
--> This is Mandatory for clients to pick the web SDK for the thank you page from the campaign itself. It is different for every campaign.
--> For custom-generated values, you have to use the respective macros to avoid any discrepancies in the future.
--> In the Ad-network case, you can add the web SDK pixel on the campaign level or on the advertiser level.
We're thrilled to have put together a top-notch team of qualified experts who are available to handle any of your concerns and respond to any inquiries you may have. You can contact us at any time by sending an email to support@trackier.com or using the in-platform chat feature.
