# How Zotek work: 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 Pixel](https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/set-up-meta-pixel/meta-pixel-vs-meta-conversions-api)—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:**

<table><thead><tr><th width="148">Event </th><th width="228">Type</th><th>Description</th></tr></thead><tbody><tr><td>PageView</td><td>Server-side &#x26; Browser-side</td><td>logs an instance where a customer visited a page. This event is available on the online store, checkout, and order status pages</td></tr><tr><td>ViewContent</td><td>Server-side &#x26; Browser-side</td><td>logs an instance where a customer visited a product details page. This event is available on the product page</td></tr><tr><td>AddToCart</td><td>Server-side &#x26; Browser-side</td><td>logs an instance where a customer adds a product to their cart. This event is available on the online store page</td></tr><tr><td>InitiateCheckout</td><td><p>Server-side </p><p>(collect browser-side instead if <a href="https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/set-up-meta-pixel-guide/set-up-meta-pixel#upgrade-your-data-with-conversion-api">Coversion API settings</a> is turned off)</p></td><td>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.</td></tr><tr><td>Purchase</td><td><p>Server-side</p><p>(collect browser-side instead if <a href="https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/set-up-meta-pixel-guide/set-up-meta-pixel#upgrade-your-data-with-conversion-api">Coversion API settings</a> is turned off)</p></td><td>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.</td></tr></tbody></table>

**Event custom:**

<table><thead><tr><th width="150">Event</th><th width="224">Type</th><th>Description</th></tr></thead><tbody><tr><td>Search</td><td>Server-side &#x26; Browser-side</td><td><p>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). </p><p>This event is available on the online store page</p></td></tr><tr><td>CollectionView</td><td>Server-side &#x26; Browser-side</td><td>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</td></tr><tr><td>AddPaymentInfo</td><td><p>Server-side </p><p>(collect browser-side instead if <a href="https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/set-up-meta-pixel-guide/set-up-meta-pixel#upgrade-your-data-with-conversion-api">Coversion API settings</a> is turned off)</p></td><td>logs an instance of a customer submitting their payment information. This event is available on the checkout page.</td></tr><tr><td>CartView</td><td>Server-side &#x26; Browser-side</td><td>logs an instance where a customer visited the cart page.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://zotek.gitbook.io/facebook-multiple-pixel/getting-started/how-zotek-work-track-server-side-or-browser-side-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.