> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/integrations/content-management-system-cms/shopify-beta/migrate-shopify-integration.md). # Migrate Shopify integration Prior to the launch of the native Didomi/Shopify integration, Didomi provided two scripts that could be manually added to your organization's Shopify store.
Script 1Propagated consent from Shopify consent categories
Script 2Checkout handling
In this article, we will cover how to remove these previous scripts so that your organization can migrate to the native Didomi/Shopify integration. * [Remove script 1](#remove-script-1) * [Remove script 2](#remove-script-2) * [Configure the native Didomi/Shopify integration](/integrations/content-management-system-cms/shopify-beta.md) {% hint style="info" %} Organizations that have previously implemented script 1 and script 2 should remove those scripts before continuing with the configuration of the Didomi/Shopify native integration. {% endhint %} *** ### Remove script 1 Script 1 enabled your organization to propagate consent values for vendors configured in the Didomi CMP from the four [Shopify consent categories](/integrations/content-management-system-cms/shopify-beta.md#shopify-consent-categories): Analytics, Marketing, Preferences, and Sale of Data. The native Didomi/Shopify integration will handle this propagation once implemented, so this script should be removed from your Shopify store's theme code. Navigate to the admin view of your Shopify store and click **Online Store** on the left-hand panel. Click the ellipsis inline with the active theme for your online store and select **Edit code** from the drop-down menu.
In the Shopify store theme code editor, expand the **layout** menu and select the **theme.liquid** file.
Delete the Didomi SDK script from the `` tag in the file. Below is an example of the Didomi SDK script.
Didomi SDK script example {% code overflow="wrap" %} ```javascript ``` {% endcode %}
Next, locate the following line in the **theme.liquid** file and delete it to stop using the script in your Shopify store theme: {% code overflow="wrap" %} ```liquid {% render 'didomi-shopify-integration' %} ``` {% endcode %} Save the changes made to the file when finished. Finally, expand the **snippets** menu and locate the **didomi-shopify-integration.liquid** file.
Right-click on the file and select **Delete Permanently** from the subsequent drop-down menu.
Confirm the decision to delete the didomi-shopify-integration.liquid file in the subsequent modal and click **Delete**.
### Remove script 2 Script 2 enabled your organization to integrate the Didomi CMP into the Shopify checkout process by using a custom pixel within the Shopify store. In order to remove this script, navigate to the admin view of your Shopify store and click **Settings** on the left-hand panel.
Click **Customer events** on the left-hand panel of the subsequent page.
Select the pixel where the Didomi script is added from the list.
Locate the script in the code editor for the pixel and remove it from the code. Below is an example.
Script 2 example {% code overflow="wrap" %} ```javascript window.dataLayer = window.dataLayer || []; function gtag() { dataLayer.push(arguments); } function areVendorsEnabledInToken() { const cookieName = "didomi_token"; const vendorsToCheck = ["google", "c:googleana-4TXnJigR"]; // Get the value of a specific cookie const getCookieValue = (cookieName) => { const cookies = document.cookie.split("; "); const cookie = cookies.find((c) => c.startsWith(`${cookieName}=`)); return cookie ? decodeURIComponent(cookie.split("=")[1]) : null; }; // Decode Base64 and parse JSON const decodeBase64Cookie = (base64String) => { const decodedString = atob(base64String); return JSON.parse(decodedString); }; // Check which vendors are enabled const checkVendors = (cookieData, vendorsToCheck) => { const result = {}; vendorsToCheck.forEach((vendor) => { result[vendor] = cookieData && cookieData.vendors && cookieData.vendors.enabled && cookieData.vendors.enabled.includes(vendor); }); return result; }; // Retrieve Didomi token from cookies or localStorage const didomiToken = getCookieValue(cookieName) || localStorage.getItem(cookieName); if (!didomiToken) { console.error(`Cookie ${cookieName} not found.`); return null; } return checkVendors(decodeBase64Cookie(didomiToken), vendorsToCheck); } if ( window.location.href.includes("/checkout/") || window.location.href.includes("/checkouts/") ) { gtag("consent", "default", { ad_storage: "denied", analytics_storage: "denied", functionality_storage: "denied", personalization_storage: "denied", security_storage: "granted", ad_user_data: "denied", ad_personalization: "denied", wait_for_update: 500, }); analytics.subscribe("page_viewed", () => { const { google, "c:googleana-4TXnJigR": googleAnalytics } = areVendorsEnabledInToken(); gtag("consent", "update", { ad_storage: google ? "granted" : "denied", analytics_storage: googleAnalytics ? "granted" : "denied", functionality_storage: google ? "granted" : "denied", personalization_storage: google ? "granted" : "denied", security_storage: "granted", ad_user_data: google ? "granted" : "denied", ad_personalization: google ? "granted" : "denied", wait_for_update: 500, }); }); } ``` {% endcode %}
Click **Save** when finished.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.didomi.io/integrations/content-management-system-cms/shopify-beta/migrate-shopify-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.