Introduction
When you are ready to get more out of your monitoring, you can start with custom timing, by creating one (or multiple) of the following:
Be sure to share your tech stack to benefit from our integrated options
Integrated options
Based on your tech stack characteristics and enabling additional tracking dimensions we will already track dimensions per CMS, CDN etc out of the box. For example:
- Shopify is (unofficially) exposing server information via Server-Timing.
You can collect and benefit from this as well, for example to get to the root of TTFB challenges; - CDNs, hosting (observability) or plugin partners are often exposing information via Server-Timing.
Custom timing types
You can manually add and configure custom timings. To do this:
- Go to your Organisation level settings as that's where Custom timing lives.
- Click on Custom timings in de left sidebar
- From there, you can either edit or create custom timing.
Once you created a custom timing, its type can no longer be changed to prevent type mixture in your dataset. Most will automatically become available as metrics while others (mainly custom dimenions) will become available as dimensions and thus filters.
Enabling and disabling
When creating or editing a custom timing, you need to select the domain names where you would want to activate a custom timing.
Additionally, you need to enable Track Timing per domain via its Developer settings in the Features section. This also means that you can disable all custom timing tracking per domain at any time at once.
When Track Timing is not enabled for a domain, that domain will be greyed out in the Custom timing overview table and a popover will alert you about this on hover. Clicking on that domain will then directly take you to the Feature section of that domain.
