How Zotek works: track server-side or browser-side data ?

Zotek - TikTok Pixel Meta Pixel Feed uses a combination of browser-side and server-side tracking to increase Event Match Quality Score and improve attribution of sales to Meta Ads.

CAPI works in parallel with the Meta Pixel to help you boost the performance, measurement, and data collection of your Meta campaigns, including Facebook Ads and Instagram Ads.

Meta CAPI is not a replacement for Meta Pixelarrow-up-right—instead, it is an enhancement that enables deeper, first-party data to help you understand performance in more detail and run more effective ads.

What you can track?

Here's what you can track with Zotek - TikTok Pixel Meta Pixel Feed

Event Default:

Event
Type
Description

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 settingsarrow-up-right 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 settingsarrow-up-right 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:

Event
Type
Description

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 settingsarrow-up-right 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