Tools

Custom Code (Blocks)

Custom Code injects your own scripts and tags — analytics, pixels, verification meta, chat widgets — site-wide, without touching a theme file. Snippets live with the plugin, so they survive theme switches and updates. Where: WP Admin → Tiger Blocks → Tools → Custom Code. Injection points Head — meta tags, verification, and early scripts printed […]

2 min read Updated July 14, 2026

Custom Code injects your own scripts and tags — analytics, pixels, verification meta, chat widgets — site-wide, without touching a theme file. Snippets live with the plugin, so they survive theme switches and updates.

Where: WP Admin → Tiger BlocksToolsCustom Code.

Injection points

  • Head — meta tags, verification, and early scripts printed in <head>.
  • Body open — code that must run immediately after the opening <body> tag (for example a tag-manager noscript fallback).
  • Footer — deferred scripts that load last, just before </body>.

Each box outputs its markup verbatim at the matching WordPress hook, so you paste exactly what a third party gives you.

Theme-safe by design

Because the snippets are stored by Tiger Blocks rather than in your theme’s header.php or functions.php, they keep working when you change or update the theme — your tracking never disappears with a redesign.

Who can edit it

These boxes accept raw code, so they are writable only by administrators who hold the unfiltered_html capability, and every save is nonce-protected. On a multisite, that capability is restricted by default, so the Save button is disabled for users who lack it.

Relationship to Marketing & SEO

Custom Code is the raw-snippet companion to the Marketing & SEO module and shares its storage. If you only need standard analytics or tag-manager IDs, add them as structured fields on the Marketing & SEO screen instead — they are validated and printed for you. Use Custom Code for anything that does not fit those fields.

Troubleshooting

The Save button is greyed out

Saving requires the unfiltered_html capability. On single-site installs administrators have it; on multisite it is limited to super admins. Ask a super admin to add the code, or grant the capability.

My footer script slows the page down

Heavy third-party scripts belong in the Footer box so they load after the page renders rather than blocking it. If a script must run early (a consent manager, say), keep it in Head but load it asynchronously where the vendor supports it.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.