Adding tracking codes
Dirigible loads marketing and analytics tags from Appearance → Customize → Scripts & Embeds. Prefer the named ID fields when your vendor gives you one. Use Custom Embeds only when you must paste a full HTML or <script> snippet.
Open the right panel
- Go to Appearance → Customize.
- Open Scripts & Embeds.
- Use Analytics & Tracking for IDs, or Custom Embeds for raw snippets.
- Click Publish when you are done.
Analytics & Tracking — ID fields
Paste only the ID (not a full gtag or Pixel install snippet) into the matching field. Leave unused fields blank.
| Field | What to paste | Shape |
|---|---|---|
| Google Analytics ID | GA4 Measurement ID | G-XXXXXXXXXX |
| Google Tag Manager ID | GTM container ID | GTM-XXXXXXXX |
| Facebook Pixel ID | Meta Pixel ID | digits only |
| LinkedIn Partner ID | LinkedIn Insight Tag partner ID | digits / ID string |
| StackAdapt ID | StackAdapt pixel ID | as provided by StackAdapt |
| Hotjar ID | Hotjar site ID | digits |
Verification fields (not page-view analytics):
| Field | What to paste |
|---|---|
| Google Site Verification ID | Meta verification value (often google-site-verification=…) for Search Console |
| Facebook Domain Verification ID | Meta domain verification token |
For creating a GA4 Measurement ID and confirming Realtime data, see Google Analytics.
GA vs Tag Manager
You usually do not need both Google Analytics ID and Google Tag Manager ID for the same tags. If GTM already loads your GA4 tag, leave Google Analytics ID empty so events are not double-counted. Follow your analytics or marketing team’s plan.
Load behavior for these IDs
| Control | What it does |
|---|---|
| Tracking Load Strategy | After Page Load (default) or First Interaction (first click or scroll) before third-party SDKs request. |
| Track Admin Sessions | When off (recommended live), logged-in administrators are not tracked. Turn on only while debugging. |
| Enhanced Ecommerce Tracking | With WooCommerce, sends purchase events to GA4 or GTM when an order completes. |
| Ecommerce Debug Mode | Logs ecommerce events to the browser console — testing only. |
If GDPR Banner is enabled under Scripts & Embeds → GDPR Banner, these ID-based trackers wait until the visitor accepts — see Setting up the GDPR cookie banner.
Custom Embeds — raw snippets
Open Scripts & Embeds → Custom Embeds when a tool has no dedicated ID field, or your agency sends a full install snippet.
| Field | Where it loads | Typical use |
|---|---|---|
| Tracking Embed | Near the end of the page (with other tracking/footer output) | Extra pixels or tags that belong with analytics but have no ID field |
| <head> Embed | Document head | Snippets the vendor requires in <head> |
| <body> Embed | Near the start of the page body | Widgets that must open early in the body |
| <footer> Embed | Footer | Chat, scheduling, or late-loading widgets |
Paste complete markup as the vendor supplies it (including <script> tags when they give you a script).
Prefer the Analytics & Tracking ID fields when they exist — those respect Tracking Load Strategy and the GDPR Banner. Raw Custom Embeds print as pasted and are not gated the same way.
What not to do
- Do not paste a full Google Analytics or GTM install snippet into an ID field — paste only
G-…orGTM-…. - Do not install the same GA4 property via both Google Analytics ID and a GTM container that already fires that tag.
- Do not paste the same snippet into a Custom Embed and a page block — double loads break widgets and skew reports.
- Do not leave Track Admin Sessions on for production unless you intentionally want staff traffic in the reports.
Tips
- Test one new tag at a time, then verify in a private window (and with the cookie banner accepted, if enabled).
- Keep staging analytics off when possible so test traffic does not pollute live reports.
- Fonts and performance toggles live in other Scripts & Embeds panels — they are not tracking codes.