What is Trackingplan

Overview

The Trackingplan Way

Automonitoring

Events

Properties

User Attributes

Pages

Acquisition

Automated Alert System

Getting Started

Installing Trackingplan

Post-Install Warm-Up

Inside Trackingplan

Dashboard

Destinations

How to…

Manage Warnings

Marketing Observability

Enhance Collaboration

Extend detection

Catch pre-launch errors

Automonitoring

<aside> 💡 Trackingplan is installed in minutes, doesn’t require technical skills to set up or use, and will start listening in real-time to all the data your sites and apps are sending to your third-party services right after its installation. That makes us the only solution that delivers value from day one across product, business, and marketing people.

</aside>

From that moment on, Trackingplan will automatically start creating your dashboard. We will send you a message once it’s ready.

<aside> ☝🏻 During this time, all teams involved in the data collection process will be able to keep working as they used to, without causing any company disruption.

</aside>

Frame 206.png

How does Trackingplan discover your data schema?

Trackingplan works by listening to the requests your code makes to your current analytics services. These requests are asynchronously forwarded to the Trackingplan server, where they are parsed and analyzed looking for changes and potential errors in the received data.

Frame 202.png

In other words, Trackingplan SDK attaches a listener to all the remote tracking requests emitted by your analytics providers’ SDKs. This listener works in the background as non-blocking and, therefore, does not interfere with the original request that the provider's client makes.

The technical procedure for listening to the requests is very simple: The JavaScript methods used to make the requests are wrapped by our code. This way, when the analytics services use them to send the tracking info, two things happen:

  1. First, the original action is performed (i.e. the request is sent to the analytics provider).
  2. In a non-blocking manner, and only if the request URL matches with a known analytics services domain, the request is forwarded to our server.

Here’s what our script listens to, which includes the three most typical methods used to communicate with analytics providers:

<aside> ☝🏻 Note that this implementation is similar to the one used in your actual analytics providers, browser extensions, testing suites, and debugging tools.

</aside>

What does Trackingplan monitor

With Trackingplan, you can automatically track a variety of third-party trackers and pixels to ensure they’re working the way you want them to.

Trackingplan helps prevent disruptions in your data flow by ensuring your data is transferred to you and your backend or other third-party services, keeping an eye on your trackers and pixels in an easy-to-read dashboard.

<aside> 📌 These are the items Trackingplan helps you monitor:

← Previous

Next →