TikTok Pixel for Shopify: How it work?
TikTok Pixel for Shopify is a JavaScript code snippet you install on your Shopify store that tracks customer behavior (like page views, adding to cart, purchases) and sends that data back to TikTok Ads.
Zotek - TikTok Pixel Meta Pixel Feed simplifies this procedure by requiring less work throughout the setup process. Setup TikTok Pixel
Benefits and features
Once you've successfully set up and verified the pixel on your site, it will share information on when an action is taken on your website, based on the events you've set up. We recommend you set up events that reflect a full customer journey on your site, from viewing a product details page to adding an item to a cart and making a purchase.
Learn more about the Events Manager.
What you can track
By default, TikTok collects ttclid, ttp as the most important parameters that boost the matching.
To enable matching across user sessions and on different devices, TikTok needs you to share additional customer data.
The following parameters are collected whenever available and passed to the server-side events (in encoded format):
user_agentipemailphone_number
In order to get accurate data, you need server-side tracking that captures everything that happens in your online store, including checkout funnel activity and purchases. Zotek TikTok Pixel Meta Pixel Feed's TikTok integration enables better tracking by stitching your TikTok Pixel events together with accurate server-side events.
Event Default:
PageView
Server-side & Browser-side
logs an instance where a customer visited a page. This event is available on the online store, checkout, and order status pages
ViewContent
Server-side & Browser-side
logs an instance where a customer visited a product details page. This event is available on the product page
AddToCart
Server-side & Browser-side
logs an instance where a customer adds a product to their cart. This event is available on the online store page
InitiateCheckout
Server-side
(collect browser-side instead if Coversion API settings is turned off)
logs an instance of a customer starting the checkout process. This event is available on the checkout page. For Checkout Extensibility, this event is triggered every time a customer enters checkout. For non-checkout extensible shops, this event is only triggered the first time a customer enters checkout.
Purchase
Server-side
(collect browser-side instead if Coversion API settings is turned off)
logs when a visitor completes a purchase. It's triggered once for each checkout, typically on the 'Thank You' page. However, for upsells and post-purchases, the Purchase event is triggered on the first upsell offer page instead. The event isn't triggered again on the 'Thank You' page. If the page where the event is supposed to be triggered fails to load, then the Purchase event isn't triggered at all.
Event Custom:
Search
Server-side & Browser-side
logs an instance where a customer performed a search on the storefront. The products returned from the search query are in this event object (the first product variant for each product is listed in the array).
This event is available on the online store page
CollectionView
Server-side & Browser-side
logs an instance where a customer performed a search on the storefront. The products returned from the search query are in this event object (the first product variant for each product is listed in the array). This event is available on the online store page
AddPaymentInfo
Server-side
(collect browser-side instead if Coversion API settings is turned off)
logs an instance of a customer submitting their payment information. This event is available on the checkout page.
CartView
Server-side & Browser-side
logs an instance where a customer visited the cart page.
Last updated