Overview
Tag Management is where you configure the LayerFive tracking implementation for your website. It generates the pixel code that powers Attribution, Signal analytics, and conversion tracking across your storefront.
Navigate to: Administration → Tag Management
The module is organized into four tabs:
| Tab | Purpose |
|---|---|
| PageView Tag | Tracks page visits, sessions, and user behavior across your website |
| Order Tag | Tracks completed purchases and order data for attribution and revenue reporting |
| Shopify Web Pixel | Configures advanced behavioral event tracking via Shopify's Customer Events API |
| Additional Events Tag | Sets up custom event tracking and ad impression/click pixels |
Default Configuration
All four tabs share the same base configuration fields. These are pre-populated by LayerFive during account setup.
| Field | Description | Example |
|---|---|---|
| Store Type | Your e-commerce platform | Shopify |
| Client ID | Your unique LayerFive account identifier — provided by LayerFive | 101 |
| Domain URL | Your primary domain with a leading dot | .billyfootwear.com |
| Collector URL | The first-party tracking endpoint (requires a DNS A-record) | id.billyfootwear.com |
| Login ID / Email Attribute | Passes the logged-in customer's ID for cross-session tracking | {{customer.id}} |
The Client ID, Domain URL, and Collector URL are set by LayerFive at onboarding. Do not modify these unless instructed by your LayerFive account manager.
PageView Tag
Page View Configuration
| Setting | Description |
|---|---|
| Track Page View | Enables tracking of all page view events across your website. Should always be checked. |
| Track additional first-party cookies? | Captures additional marketing cookies to improve attribution matching |
| Cookie Name(s) | Comma-separated list of cookie names to capture. Default: _fbp,_fbc,_shopify_y |
Tracking additional first-party cookies (especially _fbp and _fbc) improves Meta attribution accuracy by preserving Facebook click identifiers even when browser restrictions block third-party cookies.
Form Tracking Configuration
Enable Form Tracking — tracks form submission events across your website. Useful for lead capture, newsletter signups, and contact form conversion tracking.
Link Click Configuration
Enable Link Click Tracking — tracks clicks on links within your website. Useful for understanding outbound navigation behavior and content engagement.
Your Pixel Code
Once configured, the generated pixel code appears at the bottom of the PageView Tag tab.
Copy the code below and paste it onto every page of your website.
Paste this code as high in the <head> of the page as possible.
Use the Copy button to copy the full snippet, then deploy it via your theme's <head> section or through a tag manager.
Order Tag
The Order Tag tracks completed purchases and feeds revenue data into Attribution and Performance reporting.
Key configuration:
-
Is Track Transaction — must be enabled for order tracking to function
-
The generated script captures order attributes such as
{{order.order_number}}to identify individual transactions
Shopify Placement
Add the generated Order Tag script in Shopify at:
Shopify Admin → Settings → Checkout → Order status page additional scripts → Additional scripts
This ensures the tag fires on the order confirmation page after every completed purchase.
Shopify Web Pixel
The Shopify Web Pixel tab configures LayerFive's integration with Shopify's native Customer Events API. This provides richer behavioral data than standard pixel tracking.
Events Tracked
| Event | What It Captures |
|---|---|
page_viewed |
All page visits |
product_viewed |
Product detail page views including product ID, title, price |
collection_viewed |
Category/collection page views |
search_submitted |
On-site search queries and result counts |
product_added_to_cart |
Add-to-cart events including product and quantity |
product_removed_from_cart |
Cart removal events |
checkout_started |
Checkout initiation |
contact_information_submitted |
Checkout contact step completion |
checkout_completed |
Completed purchase events |
Shopify Placement
Deploy the Shopify Web Pixel script at:
Shopify Admin → Settings → Customer events → Add custom pixel → Code
Paste the generated script and save.
Additional Events Tag
Use this tab to configure tracking that goes beyond default page view and purchase events.
Options
| Option | Use Case |
|---|---|
| Custom Events Tracking | Track specific interactions on your site (video plays, CTA clicks, quiz completions, etc.) |
| Ad Impression Pixel | Track ad visibility and impression delivery |
| Ad Click Pixel | Track advertisement click-throughs |
Custom Event Syntax
window.l5plow.trackEvent('event_name', 'Event Display Label', '{value}');
Example:
window.l5plow.trackEvent('custom_submit_event', 'Custom Submit Event', '{Value}');
Each custom event requires three parameters:
| Parameter | Required | Description |
|---|---|---|
name |
Yes | Internal event identifier |
label |
Yes | Display label shown in reports |
value |
Yes | Numeric value or payload |
Save & Reset
| Action | Description |
|---|---|
| Save | Applies current configuration and regenerates the pixel code |
| Reset | Discards unsaved changes and restores the last saved state |
Always Save after making configuration changes, then re-copy and redeploy the updated pixel code.
Troubleshooting
Attribution Coverage % is low The pixel may not be deployed correctly or may be missing from certain page templates. Confirm the PageView Tag is in the <head> of every page, not just the homepage.
Order data isn't appearing in Attribution Verify the Order Tag is placed in Shopify's Additional Scripts section on the order confirmation page, and that Is Track Transaction is enabled.
Shopify Web Pixel events aren't firing Confirm the pixel script is saved under Shopify → Settings → Customer Events, not in the theme files. Shopify Web Pixel requires the Customer Events API placement to function correctly.
Data looks inconsistent after a configuration change After saving changes in Tag Management, redeploy the updated pixel code. The old code on your site won't reflect new settings until it's replaced.
Related Articles