# How it works: Shopify to Pinterest ## What you can track {% hint style="success" %} You can check our [Pinterest tracking schema](https://docs.google.com/spreadsheets/d/1WaE-CVcUPQba_IFehB6T8IE6jY9N6oI9FTBuXLnwRxI/edit#gid=277331750) for a full view of events and parameters {% endhint %} Apart from the standard Pinterest events, Littledata enhances your data with the following client-side and server-side events by default: ### Client-side events | **Event name** | **Description** | | -------------- | ------------------------------------------------------------------------ | | ViewCategory | When an user lands on a product or collection page | | AddToCart \* | When the user adds a product to cart | | Checkout \* | When the user places an order (excluding Point of Sale and Draft orders) | \* Only for stores with [Littledata's custom pixel connected](/sources/shopify/littledata-pixel.md) ### Server-side events | **Event name** | **Description** | | -------------- | ------------------------------------------------------------------------ | | AddToCart | When the user adds a product to cart | | Checkout \*\* | When the user places an order (excluding Point of Sale and Draft orders) | \*\* Pinterest's Checkout event is the equivalent of a purchase event. Note: These are all of the server-side events currently supported by Pinterest. Littledata plans to support additional ecommerce events as they are made available. ## Pinterest enhanced match You need to [enable Enhanced Match](https://help.pinterest.com/en/business/article/enhanced-match) in Pinterest to get the most from Littledata's server-side events. Littledata improves this matching quality by stitching collected data to a specific user on Pinterest. For this reason, you might see different values for enhanced match in your event history. As seen above, enhanced match is 100% for Checkout events; this is because the user has shared all their customer data (email, address etc) through the checkout. ![Pinterest events](/files/q665O0aGPmQIb0yhO8mW) For AddToCart events, the enhanced match is 0%. This is because the user was not logged in when that particular event was triggered, thus the customer data is missing entirely. This would also be true if the user has an active ad blocker. **There are other customer parameters that we send:** | Parameter | Descritpion | | --------- | ----------- | | ct | County | | em | Email | | fn | First Name | | ln | Last Name | | ph | Phone | | st | State | | zp | Zip Code | ### User agent and IP address These parameters are also important for Pinterest Tag attribution. User agent and IP address parameters are automatically added to browser events, and we are passing them to server-side events to make sure the enhanced match quality is present. ### How ad clicks are linked to purchases Pinterest Tag is a client-side tracking method that works directly in the browser. When you install Pinterest Tag, a snippet of JavaScript code is added that tracks visitor activity on your website. Tracked conversions appear under Ads > Conversions, where they can be used to measure the effectiveness of the ads, define custom audiences for ad targeting or dynamic ad campaigns, and to analyse the website's conversion funnels. When a user clicks on a Pinterest d, it includes the epik query parameter. If they land on the site with enabled browser tracking, then the epik query parameter is saved inside \_epik cookie. Note that the epik parameter is specific to Pinterest, like [fbp and fbc for Facebook](/integrations/facebook-capi/how-it-works-shopify-to-meta-conversions-api.md) and [ttp and ttc for TikTok](/integrations/tiktok/how-it-works.md). Traffic from organic searches, Google Ads and email campaigns will not contain \_epik. ## Server-side tracking Client-side tracking is useful, but it is only part of the story. Server-side tracking is a more accurate way to track actions and attribute them to Pinterest campaigns. In situations where the Pinterest Tag might be blocked by privacy controls (ad blockers, ITP and iOS 14/15/16 restrictions), Pinterest API for conversions can still track conversions. Server events are linked to a Pinterest ad account and are processed like web events sent via Pixel. This means that server events are used in measurement, reporting and optimisation similar to browser Pixel events. ## Custom parameters The following parameters are included with every event sent to Pinterest. | Parameter | Description | | -------------- | --------------------------------------------------------------------------------------------------------------------- | | market\_handle | The handle of the Shopify Market for this event. Fixed as `unassigned\_market` for orders not attributed to a market. | | market\_id | The internal Shopify Market ID for this event. Fixed as `0` for orders not attributed to a market. | ## Market parameters in Littledata events All events sent to Pinterest include the Shopify Market handle by default. This allows you to analyse ad performance by Shopify market — for example, understanding which markets are driving the most conversions from your Pinterest campaigns, or building market-specific audiences for retargeting and dynamic product ads. This requires Shopify Markets to be active on your store, but does not require any per-market destination configuration within Littledata. --- # 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://help.littledata.io/integrations/shopify-to-pinterest/how-it-works.md?ask= ``` 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.