Tracking Locations


If you started instrumenting your Interactions, chances are you already ran into some Collisions.

Example of a collision of the footer element in the browser's console:

Collision: duplicated footer

Unique Locations

To make modeling easier it's important to ensure all Tracked interactive Elements are uniquely identifiable. Assigning a unique identifier to each Element is not always possible, most often impractical. Think of reusable components.

This is where our LocationStack comes in handy in the form of Tracked Context and Element components.

Tracked Contexts and Elements

Our taxonomy comes with a number of LocationContexts aimed at describing the UI unambiguously.

For each of these, the React SDK offers a TrackedContext component.

There are also some HTML semantic aliases, called TrackedElements, aimed at tracking JSX HTML Elements. We may add more of these in the future.

Here is a full recap:









Example of collision

Let's see how these Components can help us in making all Interactions uniquely identifiable in the UI.

Here is an example page with a collision:

import { Layout } from "./components/ui";
import { ComponentProps } from "react";
import { TrackedAnchor, TrackedContentContext } from '@objectiv/tracker-react';

<TrackedContentContext<ComponentProps<typeof Layout>>
Component: Layout,
id: 'layout'
<TrackedAnchor href="/signup">Sign up</TrackedAnchor>
<TrackedAnchor href="/signup">Sign up</TrackedAnchor>

The same link has been used multiple times across the page.

React Tracker will notify of the collision of the second link with the first one.

Solving a collision

To solve the issue, we can simply make the Location of these Elements richer:

import { 
} from '@objectiv/tracker-react';

<TrackedContentContext<ComponentProps<typeof Layout>>
Component: Layout,
id: 'layout'
<TrackedAnchor href="/signup">Sign up</TrackedAnchor>
<TrackedDiv id={'body'}>
<TrackedAnchor href="/signup">Sign up</TrackedAnchor>

You may have noticed that the TrackedDiv in the example above is not strictly necessary to solve the collision. So, why did we add it?

More on that in our best practices around what to track and why.

Best practices

Solving Collisions should not be an issue to deal with frequently.
Check out how to avoid them in the first place by reading what we think are good practices around tracking Locations.

What's next?

This is pretty much it for the basics of tracking with React SDK.
Check out the API Reference and its examples for more details about all the available Components, Hooks and APIs.