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