Keep a register of every custom script added to your store

A custom-code field can become an unowned collection of tags. Keep a register so every script has a purpose, an authorised owner and a way to be removed.

Record the reason before pasting code

Name the service, the business question it supports and the pages where it needs to run. A script added because someone said it might improve tracking is not a complete requirement.

Identify whether an equivalent integration already exists. Duplicate installation can create confusing data or unnecessary work even when the page still appears normal.

Know who supplied the code

Use the provider's current authorised instructions. Do not paste code from an unknown message or an old screenshot without checking its origin and purpose.

Keep secret credentials out of browser-delivered code. If an integration asks for a sensitive key in a public page, have the implementation reviewed before proceeding.

Define the data boundary

List the information the integration may collect and the permissions or consent required for its use. Confirm the relevant requirements through the appropriate privacy process.

A useful register includes owner, installation location, purpose, data categories, date, test evidence and removal instructions. Store actual secrets elsewhere, not in the register.

Test more than whether the tag appears

Check the storefront's important routes and the measurement outcome the script was meant to provide. Inspect failed and repeated actions where relevant. A tag loading is not proof that its event definitions are correct.

Also observe loading and interaction on a representative phone. If the change slows a buying step or breaks a control, the business value must be reconsidered.

Remove deliberately

When a service is retired, confirm which script and related configuration can be removed. Keep a before-state and verify that unrelated integrations still work.

This guide does not claim that oBizee exposes a custom-head editor on every account. It describes the governance needed wherever such a capability exists. Use the platform evaluation hub to ask who owns these responsibilities before choosing an integration-heavy setup.

Illustrative case to check

The store already sends a purchase event through one integration. A contractor proposes adding another snippet for the same provider. Check the existing installation and event ownership before proceeding. The register should make the potential duplicate visible, with a named person deciding whether the new snippet replaces, supplements or should not be added.