# Changing the data pipeline settings Each destination's settings can be accessed from the Littledata dashboard, within the respective destination widget. The global settings are located in the left-side Shopify navigation bar. ## Destination settings Accessed through the destination widget in the Littledata dashboard. ### General settings Found in the **General tab** under each connected destination. **Google Analytics** **Measurement ID** Your data stream's Measurement ID used to send event data.
**API Secret** Measurement Protocol API secret is used for your data stream to establish a secure connection between the Shopify and Littledata servers. **Consent mode** By enabling consent mode, this destination will become responsive to user consent - allowing you to manage data flow based on each user's consent choices. **Google Ads** **Google Ads account** The Google Ads account that is connected to your Shopify store. **Consent mode** By enabling consent mode, this destination will become responsive to user consent - allowing you to manage data flow based on each user's consent choices. **Segment** **Segment write key** Segment write key of the source receiving data. **Consent mode** By enabling consent mode, this destination will become responsive to user consent - allowing you to manage data flow based on each user's consent choices. **Meta** **Pixel ID** Meta Pixel ID of the source receiving data. **Access token** The access token required to send data to the Meta Pixel. **Consent mode** By enabling consent mode, this destination will become responsive to user consent - allowing you to manage data flow based on each user's consent choices. **Pinterest** **Ad account ID** Pinterest Ad Account ID of the source receiving data. **Tag ID** Pinterest Tag ID of the source receiving data. **Conversion access token** Pinterest Conversion Access Token of the source receiving data. **Consent mode** By enabling consent mode, this destination will become responsive to user consent - allowing you to manage data flow based on each user's consent choices. **TikTok** **Pixel code** TikTok Pixel Code of the source receiving data. **Access token** TikTok Access Token of the source receiving data. **Consent mode** By enabling consent mode, this destination will become responsive to user consent - allowing you to manage data flow based on each user's consent choices. **Klaviyo** **Klaviyo account** The Klaviyo account that is connected to your Shopify store. **Attentive** **Attentive account** The Attentive account that is connected to your Shopify store. ### Data customisation settings Found in the **Data customisation** tab under each connected destination. **Order identifier** There are 3 ways to track your orders: * Order ID (e.g. 5028988223651) is Shopify’s internal order identifier. * Order Number (e.g 1024) is the order position in the shop's count of orders (your internal counter) * Order Name (e.g #US1023) is obtained by combining the order number and any suffix or preffix you've set in your store's general settings. *for Google Analytics, Google Ads, and Segment destinations* Default: `Order Name` **Product identifier** There are 3 ways to track your products: * Product ID (e.g. 8663410540836) is Shopify's internal product identifier. * Variant ID (e.g. 46799140684068) is Shopify's internal variant identifier. * SKU (e.g. tshirt-xl-red) is the internal identifier that each merchant can set for a product or variant. *for Google Analytics, Segment, Meta Ads, Pinterest Ads, and TikTok Ads destinations* Default: `Product ID` **Send user data to Google Analytics** GA4 accepts hashed first-party data to better attribute ads and users. You first need to [opt in to detected user-provided data](https://support.google.com/analytics/answer/14077171?hl=en) in your Google Analytics property. {% hint style="info" %} Opting into user-provided data without enabling this option to send the `user_data` object could result in Google not tracking purchases. {% endhint %} Read more about how [user data works in GA4](/integrations/shopify-to-google-analytics/tracking-first-party-data-ga4.md). *for Google Analytics destination only* Default: `OFF` **Order channels exclusion list** You can choose to exclude orders based on the order channel. Choose one from the already known channels, or add a custom one.\ See [how to exclude orders by order channel](/advanced/troubleshooting/how-to-exclude-orders-by-source.md). *for all destinations excluding Klaviyo, Attentive, and Google Ads* **Exclude zero value orders** By default, we track orders with zero value. If you want to exclude them from your destination, turn on this setting. Default: `OFF` **Order tags exclusion list** Add order tags that you want to exclude from your destination. This is useful for sample orders. The tags are case-insensitive. Example: `sample order` **Disable recurring orders** By default we track recurring orders as a separate event. If you want to disable this, set this field to **ON**. *for all destinations excluding Klaviyo, Attentive, and Google Ads* Default: `OFF` **Track pageviews only when page reloads** For some themes, where the URL changes (e.g. a new variant) without a new page load our script will track a new page view. Change to **ON** to disable a new page view on `history.replaceState()` via [browser History API](https://developer.mozilla.org/en-US/docs/Web/API/History_API). *for all destinations excluding Klaviyo, Attentive, and Google Ads* Default: `OFF` **Use page type for list name** Littledata's tracking script uses the `document.location.pathname` as the list name for list events. Setting to **ON** overrides this to use [Shopify's page\_type](https://shopify.dev/docs/themes/liquid/reference/objects/request#request-page_type) as the list name, which has fewer values and may be more helpful in reporting. *for all destinations excluding Klaviyo, Attentive, and Google Ads* Default: `OFF` ### Google Analytics session enrichment Found in the **Session enrichment** tab under the **Google Analytics 4** destination. {% hint style="info" %} [Session enrichment](/integrations/shopify-to-google-analytics/source-medium-customization-payment-gateway.md) is a new version of our Google Analytics tracker that extends Google's Measurement Protocol to give you a more accurate attribution and deeper control over your tracking {% endhint %} **Attribution boost** We improve your orders attribution by matching return purchases to known attribution information such as UTM parameters. Default: `ON` **Attribution boost - recurring purchases** When enabled, this setting ensures that all subsequent recurring purchases retain the original UTM parameters from the first order in the series, maintaining consistent campaign attribution. Default: `OFF` **Source / medium customization** [Create your own rules](/integrations/shopify-to-google-analytics/source-medium-customization-payment-gateway.md) to overwrite how orders get attributed based on different conditions. ### Segment settings Found in the **Tracking customisation** tab under the **Segment** destination settings. **Anonymize IP** This field instructs the Segment library to mask the last 3 numbers of the user's IP address, to support greater user privacy at the expense of some geo-location accuracy. Default: `OFF` **Include revenue on purchase events** Default: `OFF` **User ID** You can [choose an identifier to use](https://segment.com/docs/connections/sources/catalog/libraries/website/shopify-littledata/#user-identity) for logged-in users. {% hint style="info" %} This must match what is configured for server-side events in Littledata's app settings. {% endhint %} Possible values: * Shopify customer ID * Email * MD5 hashed email * Customer metafield * None Default: `Shopify customer ID` **CDN for Analytics JS** If you have a [proxy CDN setup](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/custom-proxy), redirecting to `https://cdn.segment.com`, to load Segment's AnalyticsJS library from your own domain you can specify it here. It must include the full domain, with no trailing slash. Default: `CDNForAnalyticsJS: "https://cdn.segment.com"` (string) **Cookies to track** Grab the values from an array of named cookies and pass them as traits on Segment identify calls. Example: `"iterableEmailCampaignId", "iterableTemplateId"` ### Global settings Found in the left-side navigation sidebar inside Shopify Admin. These settings are agnostic of any destination. **Use note attributes** Allows Littledata to attach notes to cart and order events.
This improves accuracy for reporting and server-side analytics. Default:`ON` **Hide branding** Removes Littledata’s console branding message from your browser logs. Default: `OFF` **Product list links include images** If your product list displays product images inside or directly beside the clickable link, enable this setting. It ensures[ Littledata tracks clicks](/integrations/shopify-to-google-analytics/tracking-product-list-views-and-clicks.md) on product images as product views. {% hint style="info" %} We assume that a product list will consist of a list of links to product images OR a list of links with images in a sibling HTML element; i.e., both the `` and `` tag shares the same parent element. If you need to track only links where the `` tag is a child of the `` tag, turn on this setting. {% endhint %} Default: `OFF` **Product list links include prices** Turn this on if the price is part of the clickable product link. When enabled, Littledata will only track views and clicks where the price is visible, giving you cleaner product list reporting. Default: `OFF` **Debug logs** Debug mode adds extra console logs to track how the script is performing. Default: `OFF` --- # 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/advanced/developer/data-pipeline-settings.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.