Home Getting Started and Administration

Getting Started and Administration

Getting Started guide. Articles to help you get started with using LayerFive
By Sushil Goel
• 12 articles

Getting Started with LayerFive

Overview This guide walks you through the essential steps to get LayerFive set up for your team — from connecting your data sources to exploring your first dashboards. LayerFive's built-in Onboarding module tracks your setup progress and links you directly to each configuration step. You can return to it at any time. Navigate to: Administration → Onboarding Step 1: Connect Your Data Sources Before your dashboards and reports have meaningful data, you need to connect your ad platforms and e-commerce store. The Onboarding screen shows your connected integrations at the top. Start with the four core sources: | Priority | Source | Why It Matters | | -------- | -------------- | -------------------------------------------------------------------------------- | | 1 | Shopify | Powers all e-commerce and order data across dashboards and Attribution | | 2 | Google Ads | Populates the Google Performance dashboard, Attribution, and Performance Reports | | 3 | Meta | Populates the Meta Performance dashboard, Attribution, and Creative Reporting | | 4 | TikTok | Adds TikTok spend and performance data across channels | To connect additional sources, go to Administration → Integrations Once connected, each source displays a Last Sync timestamp confirming data is flowing. Most integrations complete their first sync within a few hours. Step 2: Complete the Core Setup Steps The Core Setup Steps section in the Onboarding module shows the remaining configuration tasks. Each step includes a Go button that takes you directly to the relevant screen. | Step | What to Do | Where It Takes You | | ------------------------- | ----------------------------------------------- | ---------------------------------------------------------------------------------------- | | Add Timezone and Currency | Set your reporting timezone and currency | Administration → System Settings | | Create a Custom Metric | Build a calculated KPI (e.g. blended ROAS, MER) | Performance Reports → Custom Metrics | | Create a Custom Report | Set up your first segmented performance report | Performance Reports → Create Report | The progress bar at the top of the Onboarding screen tracks completion. Once all steps are done, your account is fully configured. Step 3: Set Up Your Tracking (Tag Management) For LayerFive's Attribution and Signal modules to work accurately, the LayerFive pixel must be deployed on your website. Navigate to: Administration → Tag Management The pixel code is generated automatically based on your account configuration. Copy it and paste it into the <head> section of your website (or into Shopify's customer events pixel settings for Shopify stores). See Tag Management for full implementation instructions. Step 4: Invite Your Team Add colleagues who need access to the platform. Navigate to: Administration → User Management - Click + Create to add a new user - Enter their name, email, and assign a role - Set a default landing page so they log in directly to the view most relevant to their work See User Management for details on roles and permissions. Step 5: Explore Your Dashboards With data flowing, your dashboards will begin populating. Start with the Executive Summary for a top-level view across all channels. Navigate to: Axis → Dashboards Recommended exploration order: 1. Executive Summary — Overall MER, ROAS, revenue, and spend across all channels 2. Meta Performance — Channel-specific metrics for Facebook and Instagram 3. Google Performance — Paid search and shopping performance 4. Shopify Order Analytics — Order volume, AOV, and revenue trends 5. Cohort Analysis — Customer retention and repeat purchase behavior Step 6: Configure Attribution LayerFive's Signal module provides first-party attribution alongside your ad platform data. Navigate to: Signal → Marketing Attribution → Attribution Analytics Key things to review on first access: - Coverage % — The percentage of your orders LayerFive is tracking. If this is low, your pixel may not be fully deployed (see Step 3). - Default Attribution Model — Set in System Settings. Options include Any Click, Last Click, First Click, Equal Weight, and View-Through. - New vs. Returning Customer filter — Lets you separate acquisition performance from retention. Onboarding Progress Tracker The Onboarding screen at Administration → Onboarding shows your real-time setup progress (e.g. 3/4 steps, 75% complete). Use it as your checklist reference throughout the setup process. Troubleshooting Data isn't appearing in dashboards Check Administration → Integrations and confirm all connected sources show a recent Last Sync timestamp. If a source shows "Last Sync: NA", reconnect it. Coverage % in Attribution is low The LayerFive pixel is likely not fully deployed. Revisit Tag Management and confirm the pixel code is placed correctly on your storefront. A user didn't receive their invitation Ask them to check spam/junk folders. If the issue persists, delete the invite in User Management and resend it. Related Articles - Integrations - Tag Management - User Management - System Settings - Attribution Analytics

Last updated on Jun 11, 2026

Integrations

Overview The Integrations page is where you connect LayerFive to your advertising platforms, e-commerce store, and third-party tools. All connected sources feed data into your dashboards, reports, and attribution models. Navigate to: Administration → Integrations The page is divided into two sections: - Connected — Sources currently active and syncing - Not Connected — Available sources you can add at any time Connecting a Data Source 1. Navigate to Administration → Integrations 2. Find the source you want to connect in the Not Connected section (use the search bar if needed) 3. Click Connect 4. Follow the authorization flow for that platform (typically OAuth or API key entry) 5. Once authorized, the source moves to the Connected section and begins its first sync First sync timing: Most integrations complete their initial data pull within a few hours. The Last Sync timestamp on each card updates after every successful sync. Managing Connected Sources Each connected integration card displays: | Element | Description | | --------------------------- | -------------------------------------------------------------- | | Last Sync | Timestamp of the most recent successful data sync | | View connection details | Opens the configuration and credential details for that source | | Disconnect | Removes the integration and stops data syncing | Before disconnecting: Removing an integration will stop all data from that source from flowing into LayerFive. Historical data already synced is retained, but new data will not pull until reconnected. Available Integrations Advertising Platforms | Platform | What It Powers | | ------------------- | -------------------------------------------------------------- | | Google Ads | Google Performance Dashboard, Attribution, Performance Reports | | Meta (Facebook) | Meta Performance Dashboard, Attribution, Creative Reporting | | TikTok | TikTok channel data across dashboards and Attribution | | Bing Ads | Bing channel data in Performance Reports and Attribution | | Pinterest | Pinterest ad spend and performance data | | LinkedIn | LinkedIn campaign data | | Snapchat | Snapchat ad performance | | Reddit | Reddit ad data | | Criteo | Retargeting data from Criteo | | StackAdapt | Programmatic campaign data | | MNTN | Connected TV campaign performance | | Google Ads MCC | Multi-account Google Ads management | E-Commerce | Platform | What It Powers | | --------------- | -------------------------------------------------------------------------- | | Shopify | Shopify Order Analytics Dashboard, Cohort Analysis, Attribution order data | | WooCommerce | WooCommerce order and revenue data | Email & CRM | Platform | What It Powers | | -------------- | ---------------------------------------------- | | Klaviyo | Email channel attribution and performance data | | DotDigital | Email marketing data | | Mailchimp | Email campaign performance | | HubSpot | CRM and marketing data | | Salesforce | CRM data and customer records | | Marketo | Marketing automation data | Analytics | Platform | What It Powers | | -------------------- | --------------------------------------------- | | Google Analytics | Web analytics data alongside LayerFive Signal | | Fathom AI | Privacy-focused web analytics | Note on Google Analytics (GA4): GA4 may return slightly different metric values compared to the GA4 user interface. This is a known behavior documented by Google. See Google's documentation for details. Customer Experience & Support | Platform | What It Powers | | ------------ | ------------------------------- | | Yotpo | Reviews, loyalty, and UGC data | | Gorgias | Customer support ticket data | | Zendesk | Support and service data | | Clearbit | Lead enrichment data | | TypeForm | Form submission and survey data | Notifications & Productivity | Platform | What It Powers | | ----------------- | ----------------------------------------------------- | | Slack | Daily performance digest sent to a designated channel | | Google Sheets | Export and sync data to spreadsheets | | SFTP | Secure file transfer for data exports | AI & Meeting Intelligence | Platform | What It Powers | | ---------------- | ----------------------------------------- | | Fathom AI | Meeting recording and insight integration | | Fireflies AI | Meeting transcription and notes | | Avoma AI | Conversation intelligence | | OpenAI API | AI-powered features within LayerFive | | PostScript | SMS marketing data | Slack Integration: Daily Insights When you connect Slack, LayerFive sends a daily performance digest to your chosen channel. Setup note: After connecting, you must invite the LayerFive bot to your Slack channel for notifications to work. In your Slack channel, type: /invite @Layerfive Daily-Insights Notifications will be sent to the #daily-insights channel (or whichever channel you configured during setup). Troubleshooting Last Sync shows "NA" The integration connected successfully but hasn't completed a sync yet, or the connection needs to be refreshed. Click View connection details to check the status, then disconnect and reconnect if needed. Data looks different from what I see in the ad platform Small discrepancies between LayerFive and native platform reporting are normal, due to differences in attribution windows, conversion counting methodology, and data processing timing. For GA4 specifically, see the note above. I can't see a source I want to connect Use the search bar in the Not Connected section. If the source still doesn't appear, contact your CSM — new integrations are added regularly. My connection keeps dropping This usually means the OAuth token has expired or the underlying account credentials changed (e.g., a password reset). Disconnect and reconnect the integration to refresh authorization. Related Articles - Getting Started with LayerFive - Attribution Analytics - Executive Summary Dashboard

Last updated on Jun 11, 2026

User Management

Overview User Management is where account administrators create and manage platform users, assign roles, control access permissions, and configure each user's default landing page. Navigate to: Administration → User Management The User List The User Management dashboard displays all users on the account in a table with the following columns: | Column | Description | | -------------- | ----------------------------------------- | | # | Row number | | First Name | User's first name | | Last Name | User's last name | | Email | Registered login email address | | Actions | Edit (pencil icon) or Delete (trash icon) | Use the Search bar at the top to find users by name or email. Pagination controls at the bottom let you adjust items per page and navigate between pages. Creating a New User 1. Click + Create in the top right corner 2. Fill in the required fields (see User Details below) 3. Click Save The user is immediately added to the system. They can log in using the email and credentials set during creation. User Details Clicking the edit icon next to any user opens the User Details form. The same form is used when creating a new user. Basic Information | Field | Description | | -------------- | ---------------------------------------------------------------------------------------- | | Email | The user's login email address — used for authentication and any platform communications | | First Name | User's first name | | Last Name | User's last name | | Status | Active (can log in) or Inactive (access disabled) | Role The Role dropdown assigns the user's permission level: | Role | Access | | ----------------- | ----------------------------------------------------------------------------------------------------- | | Account Owner | Full administrative access — can manage users, integrations, billing, and all platform settings | | Standard | Standard platform access — can view dashboards and reports; administrative settings may be restricted | Tip: Assign Account Owner sparingly. Most day-to-day users — analysts, marketing managers, agency team members — should be Standard users. Email Reports Controls whether the user receives automated report emails from the platform. Set to Active to enable or Inactive to disable. Landing Page The Landing Page dropdown sets which module or dashboard the user lands on immediately after login. Options include every major module in the platform: 1. Access Groups 2. Administration 3. Agency 4. Brands 5. Change Password 6. Clients 7. Custom Metrics 8. Integrations 9. Learning 10. Notes 11. Onboarding 12. Onboarding Pending 13. Roles 14. Roles & Permissions 15. Sheets Configuration 16. System Settings 17. Tag Management 18. User Management 19. View Report Setting a relevant landing page reduces navigation friction — a media buyer should land in Google or Meta Performance; an executive should land in Executive Summary or a Custom Dashboard. Deactivating vs. Deleting a User | Action | When to Use | Effect | | ------------------------- | ------------------------------------------------------- | ----------------------------------------------------- | | Set Status → Inactive | Employee leaves temporarily, agency relationship pauses | Disables login; user record and history are preserved | | Delete (trash icon) | Permanent removal | Removes the user and their associated account data | Best practice: Deactivate rather than delete when an employee or agency contact leaves. This preserves historical audit trail and attribution data without keeping an active login. Password Management On the User Details page, administrators can reset a user's password using the Change Password button. Use this if a user is locked out or needs a credential reset. Best Practices - Keep the Account Owner role to two or three people maximum — typically the platform admin and primary CSM contact - Assign landing pages based on each team member's role to reduce time-to-insight on login - Audit the user list periodically, especially after team changes or agency transitions - Deactivate users promptly when they no longer need access Troubleshooting A user can't access a feature or dashboard Check their assigned role. Standard users may have restricted access to certain administrative features. Adjust the role if needed. A user can't log in Confirm their Status is set to Active in User Details. If active, use the Change Password button to reset their credentials. I can't see the User Management option in the navigation Only Account Owner users can access Administration settings. Ask your account's owner to update your role. Related Articles - Getting Started with LayerFive - System Settings - Billing & Usage

Last updated on Jun 11, 2026

System Settings

Overview System Settings is the configuration hub for your LayerFive account. It controls company identity, attribution behavior, tracking parameters, API access, email automation, event definitions, order classification, and UTM mapping — all of which directly affect reporting accuracy and platform behavior. Navigate to: Administration → System Settings The page is organized into six tabs: | Tab | Purpose | | ------------------------ | -------------------------------------------------------------------- | | Company Information | Core account settings — timezone, currency, attribution, Meta config | | Rest API Token | Generate and manage API access keys | | Trigger Email Config | Configure abandoned cart and trigger-based email automation | | Event Config | Define custom tracking events and conversion goals | | Order Config | Classify order tags and define non-online order rules | | UTM Param Config | Map UTM parameters to internal media sources and channel groupings | Company Information This tab contains the foundational settings that apply platform-wide. Configure these during onboarding — changes here affect all dashboards, reports, and attribution models. Company Details | Field | Description | | ---------------- | -------------------------------------------------------------------------------------- | | Company Name | Display name used across the platform and in exports | | Company URL | Your primary website domain (e.g. billyfootwear.com) — used for attribution tracking | | Company Logo | Upload a JPG or PNG (max 2 MB) for platform branding | Timezone & Currency | Field | Description | | ------------ | ----------------------------------------------------------------------------------------------------------------------------- | | Timezone | Sets the default timezone for all report date ranges, attribution windows, and scheduled reports (e.g. America/Los_Angeles) | | Currency | Sets the currency for all revenue, ROAS, and spend metrics (e.g. USD) | Important: Timezone and currency are account-wide settings. Changing them after launch will affect how historical data displays across all dashboards. Align with your team before updating. Attribution Settings | Field | Description | | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | Attribution Look Back Window | How far back (in days) LayerFive considers user interactions when attributing a conversion. Default is 30 days. | | Default Attribution Model | The attribution logic applied by default across reports. Options: Any Click, Last Click, First Click, Equal Weight, View-Through. | The Default Attribution Model can be changed on individual reports and dashboards without changing this global setting. Subscription Product Check Is Subscription Based Product? if your store sells products on a subscription or recurring billing model. This adjusts how revenue and retention metrics are calculated in reporting. Meta Configuration | Field | Description | | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- | | Meta Pixel ID | Your Meta tracking pixel identifier | | Meta Token | API token for Meta integration authentication | | Enable Meta Conversion API | Activates server-side event tracking for Meta, improving attribution reliability by reducing dependence on browser-based tracking | Before enabling Meta Conversion API: Only turn this on after discussing with your LayerFive account manager. Ensure any existing Shopify or third-party Meta CAPI implementation is turned off first to avoid duplicate event reporting. Email Configuration | Field | Description | | ------------------------------- | -------------------------------------------------------------------------------------------------------- | | Subscription Email Sends On | Controls when subscription-related emails are triggered | | Week Starts From | Sets the first day of the reporting week (e.g. Sunday). Affects weekly breakdowns across all dashboards. | UTM Pattern | Field | Description | | -------------------- | --------------------------------------------------------------------- | | Campaign Pattern | Defines whether campaigns are identified by Name or another attribute | | Ad Pattern | Same as Campaign Pattern, applied to ad-level attribution | DNS Forwarding Configuration | Field | Description | | ------------------------ | ----------------------------------------------------------------------- | | Use DNS Forward | Enables a custom first-party tracking domain for improved data accuracy | | Is DNS CNAME Updated | Automatically updated by LayerFive once the CNAME record is verified | Only enable DNS Forwarding after discussing the setup with your LayerFive account manager. Dashboard Configuration Default Screen sets the landing screen for all users who don't have a specific landing page configured in User Management. Use this to set a sensible default for most of your team. Rest API Token Manage API credentials for external integrations and custom development. | Action | Description | | --------------------- | ---------------------------------------------------------------------------------------------- | | View API Key | Displays the current API access key | | Generate New Key | Creates a new key — this invalidates the existing key and will break any integrations using it | | API Documentation | Links to LayerFive's developer API docs | Keep your API key secure. Do not share it in public channels or include it in client-facing documents. Trigger Email Config Configure automated email triggers for customer lifecycle events. Abandoned Cart | Field | Description | | --------------------------------- | ------------------------------------------------------------------------------------ | | Enable Abandoned Cart Trigger | Activates abandoned cart email automation | | Trigger Delay | How long (in minutes) after cart abandonment the email is sent. Default: 60 minutes. | | Send Test Email | Sends a test to validate delivery and email formatting | Event Config Define the custom tracking events that power LayerFive's funnel analytics and attribution reporting. Each event has the following fields: | Field | Description | | -------------------- | --------------------------------------------------------------------- | | Event Name | Internal identifier for the event | | Event Sub Type | Category for grouping related events | | Display Name | The label shown in dashboards and reports | | Value | Monetary or scoring value assigned to the event | | Display Sequence | Controls the order events appear in funnel views | | Is Funnel Event? | Marks the event as a stage in the conversion funnel | | Is Conversion? | Marks the event as a conversion goal — affects ROAS and KPI reporting | | Tracking Code | Implementation code connecting the event to your tracking setup | Click Save Config after adding or editing events. Events marked as conversions will influence attribution model calculations. Make sure only intentional purchase or lead events carry this flag. Order Config Define how incoming orders are classified in LayerFive. Use this tab to: - Add order tags that help segment order sources (e.g. TikTok Shop, Marketplace, IMSMP) - Mark orders as non-online (offline sales, marketplace orders) to keep them separate from direct e-commerce attribution This improves the accuracy of ROAS and revenue attribution reporting by preventing offline or manually created orders from inflating digital campaign performance. UTM Param Config Map UTM parameters to LayerFive's internal media source taxonomy. This standardizes how traffic sources are classified across all reports and attribution models. Mapping Fields | Field | Description | | ----------------- | ----------------------------------------------- | | UTM Source | The raw UTM source value from your URLs | | UTM Medium | The raw UTM medium value | | Media Source | How LayerFive labels this source in reports | | Media Type | Paid, Organic, Referral, etc. | | Media Channel | Channel grouping (e.g. Display, Search, Social) | Example Mappings | UTM Source | Media Source | Media Type | Media Channel | | ---------- | ------------ | ---------- | ------------- | | adroll | AdRoll Ads | Paid | Display | | 6sense | 6sense | Paid | Display | Click Generate Custom to add new mapping rules. Use the + button in the table to add additional rows. Consistent UTM mapping eliminates the "unknown" and "other" buckets in channel reporting and makes attribution more reliable. Set this up early in your onboarding. Best Practices - Configure timezone and currency before your team starts using dashboards - Set the attribution look back window to match your typical purchase cycle (30 days works for most DTC brands; consider longer for high-consideration categories) - Only enable Meta Conversion API and DNS Forwarding after consulting with your LayerFive account manager - Standardize UTM mappings early — retrofitting these later requires re-processing historical data - Protect your API key and rotate it immediately if you suspect it's been compromised Related Articles - Getting Started with LayerFive - Tag Management - User Management - Attribution Analytics

Last updated on Jun 11, 2026

Theme Configuration

Overview Theme Configuration lets administrators customize the visual appearance of the LayerFive platform — including color scheme, chart colors, and default profile avatars. Navigate to: Administration → Theme Configuration Changes here apply account-wide. Individual users can override the Light/Dark mode preference from the appearance toggle in the top navigation bar. Default Theme Mode Sets the default display mode for all users on the account. | Option | Description | | --------- | ------------------------------------------------------------------------- | | Light | Light background, dark text — default for most accounts | | Dark | Dark background, light text — easier on screens in low-light environments | Theme Colors LayerFive uses three color roles across the interface. You can configure separate palettes for Light and Dark modes. | Color Role | Where It Appears | | ----------- | ------------------------------------------------------------- | | Primary | Main UI elements — buttons, active navigation, key highlights | | Accent | Secondary UI elements and decorative components | | Warn | Alert states, warnings, and caution indicators | To change a color, click the color swatch and enter a hex value or use the color picker. Tip: If your brand has defined hex codes, use those here to create a white-labeled feel for your team. The default LayerFive palette uses #FD5108 (Primary), #FE7C39 (Accent), and #D84315 (Warn). Surface Colors Controls background and card surface colors for both Light and Dark modes. | Setting | Description | | -------------------- | ------------------------------------------------------------------------- | | Light Background | Background color in Light mode. Supports solid Color, Gradient, or Image. | | Light Card | Color of card/panel surfaces in Light mode | | Dark Background | Background color in Dark mode | | Dark Card | Color of card/panel surfaces in Dark mode | For gradient backgrounds, set two colors and an Angle (deg) to control the direction of the gradient. Default Profile Avatar Shown in the header when a user has no profile image uploaded, or if their image fails to load. Select a default avatar from the tile grid. This applies to all users without a custom profile photo. Chart Trend Colors Controls the color palette used for data series in charts and trend visualizations across all dashboards. Separate palettes can be configured for Light and Dark modes. - Use + Add color to add a new color to the palette - Click the ✕ icon next to any color to remove it - Chart series are assigned colors in order from left to right, top to bottom Keep chart palettes accessible — avoid color combinations that are difficult to distinguish for users with color vision deficiencies (e.g. red/green-only palettes). Aim for sufficient contrast between adjacent series colors. Saving Your Configuration At the bottom of the page: | Action | Description | | ---------------------- | ---------------------------------------------------------------- | | Preview | Shows a live preview of your current configuration before saving | | Reset to default | Reverts all theme settings to LayerFive defaults | | Save configuration | Applies all changes account-wide | Always use Preview before saving to confirm the changes look correct across both Light and Dark modes. Related Articles - Getting Started with LayerFive - System Settings - User Management

Last updated on Jun 12, 2026

Tag Management

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 - Getting Started with LayerFive - System Settings - Attribution Analytics - Integrations

Last updated on Jun 10, 2026

Onboarding

Overview The Onboarding module is your guided setup checklist for getting LayerFive fully configured. It tracks progress across the core setup steps and links you directly to each configuration area so you don't have to navigate manually. Navigate to: Administration → Onboarding Onboarding Progress At the top of the page, a progress bar shows how many of the required steps are complete. Example: 3 / 4 steps — 75% Complete The bar updates automatically as you complete each step. Once all steps are done, your account is fully set up. Connect Your Data Sources The top section of the Onboarding page shows your currently connected integrations. These are the same connections managed in Administration → Integrations. Connected sources display a Last Sync timestamp. Sources that haven't synced yet show Last Sync: NA. Click Show more integrations to see and connect additional data sources beyond the ones displayed by default. Recommended core connections to complete before moving on: | Source | Why | | -------------- | ----------------------------------------------------------------------- | | Shopify | Required for order data, Cohort Analysis, and Attribution coverage | | Google Ads | Required for Google Performance dashboard and Attribution | | Meta | Required for Meta Performance dashboard and Creative Reporting | | TikTok | Required for TikTok channel data in Attribution and Performance Reports | Core Setup Steps Below the integrations section, the Core Setup Steps list shows the remaining configuration tasks. Each step has a Go button that navigates you directly to the relevant screen. | Step | Description | Destination | | ----------------------------- | -------------------------------------------------------------------------------------------- | ------------------------------------ | | Add Timezone and Currency | Set your reporting timezone and preferred currency so all dashboards display data correctly | Administration → System Settings | | Create a Custom Metric | Define a calculated KPI relevant to your business (e.g. blended ROAS, MER, efficiency ratio) | Performance Reports → Custom Metrics | | Create a Custom Report | Build a segmented performance report tailored to your reporting needs | Performance Reports → Create Report | Completed steps are marked with a checkmark. Steps not yet completed show an open circle. What to Do After Onboarding Is Complete Once the progress bar shows 100%, your account's core configuration is in place. From here: 1. Deploy your tracking pixel — Go to Administration → Tag Management and place the generated pixel code on your website. This is essential for Attribution accuracy. 2. Invite your team — Add users in Administration → User Management and configure their roles and landing pages. 3. Explore your dashboards — Start with the Executive Summary for a full-funnel view, then drill into channel-specific dashboards. 4. Review your Attribution data — Check Signal → Attribution Analytics and confirm your Coverage % is above 80%. Brands & Agency Tabs If your account manages multiple brands or operates as an agency, the Onboarding section also contains: - Brands — Configure settings and tracking for individual brand accounts - Agency — Manage agency-level access and multi-client configurations Contact your LayerFive CSM if you need help setting up a multi-brand or agency structure. Related Articles - Getting Started with LayerFive - Integrations - System Settings - Tag Management - User Management

Last updated on Jun 12, 2026

Billing & Usage

Overview The Billing & Usage page shows your current plan and the features included with your LayerFive subscription. Navigate to: Administration → Billing & Usage Access: Only users with the Account Owner role can view this page. My Plan The My Plan tab displays your active subscription. Each plan shows its current status (Enabled) and a full list of included features. Plan Features Depending on your plan, included features may cover: | Feature Category | Examples | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Reporting | Custom Reports, Custom Dashboards, Custom Metrics, Custom Dimensions, Creative Analytics | | Sharing & Collaboration | Dashboard Sharing, Performance Linked Note Taker, Project/Task Management, Marketing Calendar | | Integrations | Ad Platform Integrations, Non-Ad Data Source Integrations (with daily insight limits) | | AI Features | AI Performance Insights (with daily insight limits), AI Auto Task Generation, AI Auto Task ROI Insight, LayerFive Navigator (AI Agents) | | Access & Security | Role-based Access Control, Unlimited Users | | Data | Data Retention (24 months) | Upgrading Your Plan To upgrade or change your plan, click Connect Now on the plan card, or contact your LayerFive Customer Success Manager directly. Plan changes are managed through your CSM — they can advise on the right tier based on your current usage, team size, and reporting needs. Troubleshooting I can't access a feature I expect to have Check the features listed under your active plan. If the feature is listed but not accessible, contact your CSM. If it's not listed, it may require a plan upgrade. I can't see the Billing & Usage page Only Account Owner users can access Administration settings. Ask your account's owner to check your role in User Management. Related Articles - Getting Started with LayerFive - User Management - Integrations

Last updated on Jun 12, 2026

Setting Up the Shopify Custom Pixel

Introduction Shopify Custom pixels help you collect customer events on even more pages of your online store, such as the checkout and post-purchase pages. If there isn't an app pixel available that meets your requirements, then you can use custom pixels on your store to track customer events without having to modify your theme code. Custom pixels are loaded in a Lax sandbox, designed for improved security and control over the data that you send to third parties. Not all pixel functionality works in the sandbox, and you might need to consult your third-party service provider for help. Manage Custom Pixels You can manage your custom pixels in the Customer events section of your Shopify admin. 2.1 Add a Custom Pixel Before you begin: Make sure to remove or modify any existing pixels to prevent duplicate counting of customer events. Existing pixel/tag code should be manually removed from any place it exists, such as theme.liquid, checkout.liquid (Plus merchants only), and the Additional scripts in your checkout settings. Steps 1. From your Shopify admin, go to Settings → Customer events 2. Click the Add custom pixel button to open the event editor. 3. In the Add custom pixel popup, add the name of the pixel L5-Tracker. 4. Click Add pixel. Provide your pixel a unique name. If you enter the name of a custom pixel that already exists, then you'll be prompted to give your pixel a different name. 5. Once the Custom pixel is created, it will provide you with a code editor window. 6. Navigate to your Tag Management page, and Copy your Pixel code which is seen when you scroll to the end of the page. 2.2 Connect a Custom Pixel After a custom pixel has been added, you need to connect the pixel to your store so that it can start tracking customer events. Steps 1. From the Customer events page in your Shopify admin, click Custom pixels. 2. Custom pixels that aren't currently connected are displayed under the heading Disconnected pixels. Click Connect on the appropriate custom pixel line. Once connected, the pixel status updates to Connected and begins tracking customer events on your store. Troubleshooting My pixel still shows "Disconnected" Adding the pixel and connecting it are two separate actions. After saving, make sure you've clicked Connect — either from the Code Editor Window or from the ⋯ menu on the pixel line in the Custom pixels list. I'm seeing duplicate events This usually means an older pixel or tag is still firing alongside the new one. Confirm you've removed any previous LayerFive or tracking code from theme.liquid, checkout.liquid (Plus merchants only), and the Additional scripts section of your checkout settings. I don't have my Client ID Your Client ID is provided by the LayerFive support team. Reach out to your CSM if you don't have it. Events aren't appearing Confirm you replaced both CLIENT_ID and DOMAIN placeholders with your actual values, and that your domain is formatted with a leading dot and no http/https prefix (e.g. .example.com). Related Articles - Tag Management - Attribution Analytics

Last updated on Jun 16, 2026

Configuring DNS for Signals Gateway

Overview As part of setting up Meta Conversions API through Signals Gateway, you'll route your tracking data through a custom first-party domain that you own. This requires adding two DNS records with your domain provider. This article explains what these records do and how to add them. It's the most technical step in the Meta CAPI setup, so we've broken it out separately. This step is part of the broader Meta Conversions API setup. Start there if you haven't already named your account and chosen your domain. Why This Step Matters Routing data through your own domain (e.g. routing.yourbusiness.com) instead of a third-party domain improves how reliably your conversion data is measured and reduces data loss from browser privacy restrictions. The DNS records you add are what make this routing possible — and they prove to the system that you actually own the domain. What You'll Need - Access to your DNS provider account (e.g. GoDaddy, Cloudflare, Namecheap, Google Domains) - The two CNAME records provided by LayerFive during setup - About 10 minutes, plus up to an hour of waiting for changes to take effect If someone else on your team manages your DNS, you can share the setup instructions with them directly from the setup screen. The Two Records You'll Add During setup, LayerFive provides two CNAME records for you to add to your DNS provider: | Record | Purpose | | --------------------- | ------------------------------------------------ | | Routing record | Directs your tracking traffic to Signals Gateway | | Validation record | Confirms that you own the domain | Each record has a Record Name and a Destination (sometimes called "Points To" or "Target" depending on your provider). You'll copy these exactly as shown in the setup screen. How to Add a CNAME Record The exact steps vary by provider, but the general process is the same: 1. Log in to your DNS provider account 2. Navigate to the DNS management section for your domain (often labeled "DNS," "DNS Settings," "Manage DNS," or "DNS Records") 3. Choose to add a new record and select CNAME as the record type 4. Enter the Record Name exactly as provided by LayerFive 5. Enter the Destination / Points To value exactly as provided 6. Save the record 7. Repeat for the second record Copy values exactly. DNS records are precise — an extra space, a missing character, or a trailing dot can cause the record to fail validation. Copy and paste directly from the setup screen rather than typing the values manually. Checking Status Back in the LayerFive setup screen, each record shows a status indicator: - Waiting — the record hasn't been detected yet - Verified / Connected — the record is correctly in place The status updates automatically as the records are detected. Important Timing | Detail | What to Know | | ------------------------------ | -------------------------------------------------------------------------------------------------------- | | Propagation time | DNS changes typically take about 1 hour to take effect — sometimes longer depending on your provider | | Completion deadline | The process must be completed within 48 hours, or you'll need to start the domain setup again | | Need to change the domain? | Use the reset your domain link on the setup screen to change your domain or restart | Don't worry if the status still shows "Waiting" immediately after adding your records — DNS changes are rarely instant. Check back after an hour. Troubleshooting My records still show "Waiting" after more than an hour - Double-check that the Record Name and Destination values match exactly what LayerFive provided - Confirm you selected CNAME as the record type, not A, TXT, or another type - Some providers automatically append your domain to the record name — check whether your provider has done this, which can create a duplicated domain in the record My DNS provider won't accept the record - Some providers don't allow CNAME records at the root domain level. Since your Signals Gateway domain uses a subdomain prefix (e.g. routing.), this usually isn't an issue — but confirm you're adding the record to the subdomain, not the root - Check whether an existing record with the same name already exists and is conflicting I missed the 48-hour window Use the reset your domain link to restart the process. You can reuse the same domain or choose a new one. I'm not comfortable editing DNS settings That's common — DNS changes can feel risky. Share the setup instructions with whoever manages your website or domain, or reach out to your CSM and we'll walk through it with you on a call. Related Articles - Setting Up Meta Conversions API (Signals Gateway) - Setting Up Google Conversions API - Tag Management

Last updated on Jun 16, 2026

Setting Up LayerFive UTM Parameters

Overview Add these L5 parameters to all your ad campaigns to ensure that LayerFive tracks and attributes them accurately, without being affected by platform changes. This guide covers setup for Meta, Google Ads, Klaviyo, Marketo, other email/SMS platforms, and other ad platforms. General rule: If you already have other parameters in a URL or template, each set of L5 parameters should be preceded by an ampersand (&). For Meta Add these parameters to your Meta campaigns: l5s=fb&l5m=social&l5ss={{site_source_name}}&l5adid={{ad.id}}&l5p={{placement}} If you already have other parameters, the L5 parameters should be preceded by an ampersand. For Google Ads Please use the Google Ads Tracking Template. Add the following LayerFive-specific tracking parameters to an already existing tracking template: l5s=gads&l5m=search&l5cid={campaignid}&l5adid={creative}&l5kw={keyword}&mkt_network={network}&l5p={placement}&l5t={targetid} If you already have some parameters in the tracking template, you should include an & before adding the above parameters. If you are not already using Tracking Templates, please include {lpurl} before the L5 params. Refer to Google's documentation on setting up Tracking Templates for more details. Your tracking template could look like this: {lpurl}?l5s=gads&l5cid={campaignid}&l5adid={creative}&l5kw={keyword}&mkt_network={network}&l5p={placement}&l5t={targetid} Important: If you are creating a new tracking template, please test and confirm that your ads are showing and that clicks on your ads land on the target page of your site. Any errors in setting up your tracking template may result in your ad clicks not landing on your site. For more information on Google Ads' supported URL parameters, see Google's help article: Set up tracking with ValueTrack parameters. For Klaviyo Ensure you have the following UTM parameters configured in your Klaviyo settings. Go to Settings → Other → UTM Tracking, and configure utm_source, utm_medium, utm_campaign, and utm_term using the values below: | UTM Parameter | Campaign Value | Flow Value | | ----------------------------- | ------------------ | ------------------ | | Source (utm_source) | Klaviyo | Klaviyo | | Medium (utm_medium) | Message type | Message type | | Campaign (utm_campaign) | Campaign name | Flow message name | | Term (utm_term) | Klaviyo profile id | Klaviyo profile id | Note: To ensure the utm_term value is interpreted correctly by your analytics tools, Klaviyo recommends formatting this value using alphanumeric characters and separating words with the + character. Do not use personal data in UTM parameters. Click Save in Klaviyo once configured. For Marketo Add an l5_mktid parameter as a UTM parameter, and set the value to {{lead.Id}}. If you already have the Marketo Lead ID added to your URL parameters but under a different parameter name, let your LayerFive account manager know — we can use the pre-existing parameter instead. Ensure that every landing page link in your email template populates the lead ID in a URL parameter. For reference, see Marketo's documentation on tokens: experienceleague.adobe.com/en/docs/marketo/using/product-docs/demand-generation/landing-pages/personalizing-landing-pages/tokens-overview If you use Salesforce: If you have a Salesforce Lead ID (or Contact ID) available in a token/variable, set up another URL parameter, l5_sfcid, and pass the Salesforce ID. For Other Email/SMS Marketing Platforms Include an l5_emid or l5_smsid parameter in the landing page URL parameters, and set it up to send the contact ID from your email or SMS marketing platform. LayerFive will integrate with your email/SMS marketing platforms and connect the dots to identify visitors who click on an email or SMS link. For Other Ad Platforms Follow the same pattern as for Meta and Google Ads. For TikTok Ads: l5_source=tiktokads&l5_cid={__CAMPAIGN_ID__}&l5_adid={__AID__} (See TikTok's documentation for the full list of TikTok UTM parameters.) For LinkedIn Ads: l5_source=linkedinads&l5_cid={CAMPAIGN_ID}&l5_adid={CREATIVE_ID} (See LinkedIn's documentation for the full list of LinkedIn UTM parameters.) Every ad platform has its own syntax and parameter names for campaign and ad IDs. Please review the ad platform's documentation. If you have questions, contact your LayerFive account manager or email support@layerfive.com. Why This Matters LayerFive's L5 parameters are what allow attribution to work reliably across all your channels. Unlike standard UTM tracking, the L5 parameters are designed to keep attributing your campaigns correctly even when ad platforms change how they handle tracking — which is increasingly common as privacy restrictions evolve. Setting these up across every campaign and channel is one of the highest-impact things you can do to improve your Coverage % and the accuracy of your attribution data. Related Articles - Tag Management - System Settings — UTM Param Config - Attribution Analytics - Setting Up the Shopify Custom Pixel

Last updated on Jun 16, 2026

Connecting Meta CAPI (Signals Gateway Setup)

Overview Signals Gateway is LayerFive's server-side connection to Meta's Conversions API (CAPI). It sends event data directly from your website to Meta, improving the accuracy and reliability of your Meta attribution by reducing dependence on browser-based tracking. Setup is a guided three-step flow: connect your Meta account, optionally configure a custom tracking domain, and set up your data pipeline. Most accounts can complete the full setup in under 15 minutes (longer if you choose to configure a custom domain, since DNS changes take time to verify). Where to start: This setup flow appears the first time you connect Meta CAPI. If you've already completed it and need to make changes, use View Configuration from the Setup Complete summary screen, or check with your CSM for the direct path in your account. Step 1: Get Started — Connect Meta CAPI This is the first step in setup. You connect your Meta Business Account before any domain or pipeline configuration happens. Navigate to Edge and Select CAPI What to do: 1. Click Configure META CAPI and click Connect 2. LayerFive handles the Meta authentication and connection automatically in the background 3. No manual entry of Business ID, Dataset ID, or Access Token is required at this step 4. On success, you're automatically advanced to Step 2 Only the Signals Gateway pipeline type is supported. You won't see a pipeline type selection screen — clicking Connect takes you straight into the Meta CAPI connection. Once connected, this step appears as Meta CAPI connected on the final summary screen, with a Disconnect option available. Step 2: Configure DNS (Optional) This step is optional. You can skip it and move directly to Pipeline Setup, or complete it to route your data through a first-party custom domain — which generally improves measurement accuracy by making your tracking look like part of your own website rather than a third-party connection. What you'll need if you choose to set this up - A domain associated with your business - Access to make changes to your DNS settings through your DNS provider Screen 1: Optimize Data Routing (Intro) Explains the benefit of custom domain routing. Two options: | Button | What Happens | | ------------ | ----------------------------------- | | Optimize | Proceeds to the domain setup form | | Skip | Proceeds directly to Pipeline Setup | Screen 2: Choose Your Signals Gateway Domain You'll set up a subdomain on a domain you already own. | Field | Example | | ---------------------- | ---------------- | | Prefix (subdomain) | routing | | Root domain | mybusiness.com | Requirements: - Must be based on a domain you already own - You need access to update DNS settings through your DNS provider - The Signals Gateway domain can't already be in use elsewhere Screen 3: Configure DNS to Connect Domain You'll create two CNAME records with your DNS provider to verify domain ownership and route traffic to Signals Gateway. Here's an example: | Type | Record Name | Routed Traffic Destination | Status | | ----- | ------------------------------------------- | ------------------------------- | ------- | | CNAME | signals.yourdomain.netlify.com | signals.sgl5.com | Waiting | | CNAME | _3a3d5ee...signals.yourdomain.netlify.com | _d0f276a...cm-validations.aws | Waiting | Important timing notes: - DNS changes typically take about 1 hour to propagate and reflect as verified - You must complete this process within 48 hours, or you'll need to start the domain setup again - If you need to change domains or restart, use the reset your domain link on this screen Once verified, this step appears as Custom domain verified on the final summary screen, with a View DNS records option. If you skipped this step, it won't appear on the summary at all. Step 3: Pipeline Setup By this point, Meta CAPI is already connected (Step 1). This step focuses on naming your pipeline and configuring your Signals Gateway Pixel. Screen 1: Set Up Signals Gateway Pixel You'll be asked: Does your website have a Meta Pixel? If Yes (recommended): - Your existing Meta Pixel settings are applied to the new Signals Gateway Pixel - Event data is sent to the same Meta dataset you already use - Running both pixels together typically performs better - Installation is faster since settings carry over If No: - The Signals Gateway Pixel will be set up fresh and will send first-party website data directly to Meta - You'll configure a new pixel and its events from scratch Both paths include a Connect Meta Pixel step — the only difference is when it happens in the sequence. On the Yes path, it comes right after Get Started. On the No path, it comes after you've added your pixel code. Screen 2: Connect Meta Pixel You'll manually connect your Meta business portfolio so Signals Gateway can create or link the pixel using your existing Meta Pixel settings. | Field | Where to Find It | | -------------------- | ---------------------------------- | | Meta Business ID | Dataset Settings → Details → Owner | | Dataset ID | Dataset Settings → Details | | Access Token | Dataset Settings → Conversions API | The Connect button activates once all three fields are filled in. Screen 3: Setup Method Choose how you'll add the Signals Gateway Pixel to your website: | Method | Best For | | --------------------------- | ---------------------------------- | | Manually add pixel code | Direct website code edits | | Shopify | Stores using Shopify's admin panel | | Google Tag Manager | Teams managing tags through GTM | Screen 4: Add Pixel Code The instructions shown depend on the method you chose in the previous screen. Manual: - A base code snippet is shown for you to paste into your website's <head> section, just above </head> - Copy instructions — share these with a developer - Copy base code — add the pixel yourself - The base code automatically records page views; you can select additional web events to track Shopify: - A custom code snippet is shown (includes your Pixel ID and Host) - Deploy it via Shopify Admin → Settings → Customer Events - Use the Copy custom pixel code button Google Tag Manager: - Your Pixel ID, Pixel Host, and Pixel Script are each shown with individual Copy buttons - Paste these into the Tag Configuration page in your GTM account (Template Preview) Screen 5: Connect to Meta / Finish The final screen in pipeline setup. Confirms your Meta connection and completes the process. Clicking Continue takes you to the Setup Complete summary. Setup Complete — Summary Screen Once all steps are finished, you'll land on a summary screen confirming everything is connected. Progress Tracker Shows your completed steps in sequence: - Get Started ✓ - Configure DNS ✓ (only shown if you completed this step; omitted if skipped) - Pipeline Setup ✓ Summary Cards Meta CAPI connected This account is connected to Meta CAPI. Action available: Disconnect Disconnect is destructive. It removes your pipeline, your custom domain and DNS configuration, and unlinks your Meta account entirely. Only use this if you intend to fully remove the integration. Custom domain verified (only shown if DNS setup was completed) Events route through your custom domain (e.g. signals.l5id.com). Action available: View DNS records Your data pipeline is configured Your Signals Gateway pipeline is set up and provisioned. Events will appear in the CAPI dashboard once they start flowing. Actions available: Delete configuration | View Configuration Delete configuration removes only the pipeline setup — it does not affect your Meta CAPI connection or your DNS/domain setup. This is the safer option if you just need to reconfigure your pipeline without starting over completely. View Configuration opens your existing pipeline setup in edit mode, so you can review or update any step without starting from scratch. Troubleshooting My DNS records show "Waiting" after more than an hour DNS propagation can occasionally take longer than expected depending on your provider. Double-check the records were entered exactly as shown, including the full record name. If it's been several hours, use the reset your domain link to restart the process. I ran out of time on the DNS setup (48-hour window) You'll need to restart the domain configuration from Screen 2 of Step 2. Your Meta CAPI connection from Step 1 is unaffected — you won't need to reconnect Meta. I'm not sure whether to choose Yes or No for "Does your website have a Meta Pixel?" Check Meta Events Manager for your business. If you see an existing pixel actively receiving events, choose Yes — this lets Signals Gateway share its configuration instead of starting from scratch. If you're not sure or don't have one yet, choose No. I accidentally clicked Disconnect on the Meta CAPI card This is destructive and removes your entire setup, including your custom domain and pipeline. You'll need to go through the full setup flow again, including reconnecting Meta and reconfiguring DNS if you had it set up. I need to change my pipeline configuration but don't want to lose my Meta connection or domain Use Delete configuration on the pipeline card, not Disconnect on the Meta CAPI card. This removes only the pipeline, leaving your Meta connection and DNS setup intact. Related Articles - Tag Management - System Settings - Integrations - Attribution Analytics - Glossary of Terms

Last updated on Jun 25, 2026