Hi Jusaha,You can only add a 'numeric' as a child of another classification (i.e. you need to add a 'text' classification and then add a 'numeric' to that).Hope this helps,Barry

SOLUTIONThere's a fairly simple, but round-about, way of doing this:Create an event ("1st HIT (any)") that is configured with "Unique Event Recording = Record Once Per Visit"Use a Processing Rule to set the event on every server call   It will now record "1st HIT (any)" for the first server call (Pa...

Hi Jor,Broadly speaking, the approach to this is to store the calculated value and pick it up on the next page load; the value is then analysed against "Previous Page Name" (or a dedicated "Performance Timing Page Name" variable).That's the approach taken in Adobe's performanceTiming plugin with an ...

Actually, if you're only interested in the page load times (and not the asset timings), the call should just be:s.performanceTiming()You should be able to read the contents of the cookie (where the timings are stored for reading on the next page) by inspecting it in the Console before navigating:s.U...

That's right:  the measurements are collected on the next page load, which is why the article instructs the setting of a "Performance Timing Page Name" variable as well (the measurements will be analysed against this variable, and ​not​ the Page Name).Do you customise s.linkTrackVars for Exit and / ...

OverviewThe 'performanceTiming' plug-in is extremely useful; however, the conditional logic triggering its s.performanceWrite function should be more robust.DetailThe s.performanceWrite function (which calculates the performance timings and writes them to a cookie) is triggered as part of an interva...

If you use a List Variable, you'll get the timing measurements for the individual assets that make up the page (e.g., individual JavaScript libraries) - this will be a lot of data.If you just configure the ten (10) events in s.pte, you'll get nine (9) calculated timings for the performance of the pa...

artemperchyk,The problem is possibly because the value of "600" is being captured; this is how "invalid" values are represented.Please see the notes at the bottom of this page:Adobe Analytics: performanceTiming plugin · alcazes/Adobe-Analytics-from-A-To-Z Wiki · GitHub You may need to exclude values...

The events (apart from Performance Instances) must be configured as "Numeric".The values captured are in seconds.Any invalid values (i.e. negative timings or timings that exceed the limit of 600 seconds) are recorded as 600 seconds.