Core/Dash Advanced Setup

Advanced Setup Options for Coredash

Core/Dash’s standard tracking works out of the box, but every website has unique requirements. Our advanced configuration options give you the flexibility to adapt how data is collected, ensuring your metrics are accurate and actionable for your specific use case.

First Pageview Tracking

First PageView tracking is important because first pageviews are different from subsequent pageviews.  The visitors browser has no cached files it can access quickly and extra DNS lookup or setting up a secure connection between the browser and the server will take more time.

First pageviews obviously make the first impression and are also relevant new traffic sources like ad traffic. That is why traciking and filtering new visitors is important for your site.

Coredash offers flexibility in how the first pageview is tracked. This setting determines whether the initial visit is recorded and how data is stored.

Options:

• Enabled (via Localstorage, default): A modern, lightweight option. Ideal for Single Page Applications (SPAs) where you want to keep request headers light.
• Enabled (via Cookies): The most robust method. It remembers users even if they close their browser, giving you accurate data on returning visits
• Disabled: Turn this off if you have strict privacy requirements or handle session tracking through your own systems.

Page Labels

URLs can be messy and unique, but your templates aren't. Grouping hundreds of product pages under a single label like "Product Detail" gives you aggregated data that is statistically significant. This makes it much easier to spot performance trends across similar page types. 

Define a page label in the JavaScript global scope before Coredash initializes:

window.__CWVL = 'product_detail_template';

Replace 'mypagelabel' with a unique identifier for the page. This label will appear in Coredash reports for easier identification.

A/B Test Segmentation

New features can sometimes introduce performance regressions. By tagging your user sessions with their active experiment variant, you can instantly see if version B is slower than version A.:

window.__CWAB = 'experiment_checkout_v2';

If your "v2" users start seeing slower load times, you’ll know immediately, allowing you to fix the bottleneck before rolling out the feature to everyone..

Track Logged-In Users (anonymously!)

Logged-in users often experience your site differently. Their pages might not be cached, leading to slower server response times. Separating authenticated traffic from anonymous visitors ensures your public-facing performance metrics remain accurate and aren't skewed by backend processing.

Use these flags to distinguish between user states:

• For logged-in users, set:

window.__CWLI = 1;

For logged-out users, set:

window.__CWLI = 0;

This simple step ensures you have clean data for both your marketing pages and your application views.