Enabling the "OCU Upsells" extension App Embed [OCU]

How to enable the "OCU Upsells" App Embed in Your Theme Editor

Jeff Maxfield avatar
Written by Jeff Maxfield
Updated over a week ago


Beginning on Aug. 10, 2023 for all new OCU installs, in order for OCU Product page widget and Pre-purchase offers to be shown to customers on your storefront, you must enable the "OCU Upsells" app embed extension within your Shopify Theme Editor.

Click the "Enable here." link in the notification banner shown within the OCU app to be taken to the Theme Editor to enable, then click 'Save':

App embeds are app-provided elements that float or appear as an overlay in your theme, or add code to your online store without being visible to your customers. In this case, a piece of code that allows for the OCU Product page widget and Pre-purchase popup to be triggered and shown on your store. App embeds can be activated, deactivated, and customized through the theme editor. App embeds can be used with any theme version.

Enabling the App Embed Manually

If you don't see the in-app notification banner, then follow the quick and easy steps below to enable the "OCU Upsells" app embed manually:

  1. From your Shopify admin, navigate to Sales channels > Online Store > Themes:

  2. Click the "Customize" button for your currently published theme to launch the Shopify Theme Editor:

  3. In the Theme Editor, click into the "App embeds" section located in the left sidebar menu:

  4. Locate the "OCU Upsells" app embed and click the toggle to enable it:

  5. Click the "Save" button in the top-right corner of the Theme Editor:

That's it, the OCU Upsells app embed is now enabled on your store!

Advanced settings > Excluded templates

You may not want OCU Upsells scripts to run on certain pages types or templates, to help improve site performance and speed scores. In most cases, OCU Scripts need to be included on Product and Cart pages so your OCU offers function correctly there.

⚠️ Don't exclude template(s) where OCU Pre-purchase and Product page widget offers should work.

The "Excluded templates" setting allows merchants to exclude template(s) where they don't need scripts for Pre-purchase and Product page widget included:

📝In some cases, OCU Pre-purchase popups are triggered from Cart Drawers that can appear on several templates. If you exclude those templates, the OCU pre-purchase popup will not fire from the cart drawer on those templates.

Default Exclusions:

Some templates are always excluded: register, account, login, reset_password, search, and article. There's no need to include these templates in the exclusion list. You can check the mapping what each name stands for here.

The "Excluded templates" field is empty by default, meaning scripts are run on all templates, except those with default exclusions listed above.

Custom Exclusions:

Merchants can further limit scripts on the following templates as-needed: index, cart, collection, product, page, and blog. It's important to spell these template names correctly, if a certain template name is misspelled, it won't be excluded.



Renders the home page of the store, located at the root URL (/).

Renders the /cart page, which provides an overview of the contents of a customer’s cart.

Renders the collection page, which lists all products within a collection.

Renders the product page, which contains a product's media and content, as well as a form for customers to select a variant and add it to the cart.

Renders the shop’s pages, such as About us and Contact us.

Renders the blog page, which lists all articles within a blog.

To exclude certain templates, enter template name(s) exactly as they appear in your theme files. Separate multiple template values with a comma followed by a space (e.g., index, collection).

📝 Ensure the OCU Upsells extension is enabled for the "Excluded templates" setting to work and click the "Save" button in top-right corner of the theme editor.

If you change Themes, you must set up the "Excluded templates" setting again, if you publish a new theme without having previously configured it there.

Did this answer your question?