---
title: "Tracking implementation"
canonical: "https://ingrid-support.refined.site/space/KB/14647368/Tracking%20implementation"
format: markdown
---
Implementing Ingrid Tracking follows the same [five phases](https://support.ingrid.com/space/KB/18219063/Implementation) as any Ingrid project. This page covers what is specific to Tracking: what it needs in order to work, and where your tracking lives.

## The phases for Tracking

| Phase | Who leads | What it covers for Tracking |
| --- | --- | --- |
| [1. Scoping](https://support.ingrid.com/space/KB/485457923/Tracking+scoping) | Ingrid | Where tracking data comes from, your tracking page address, which carrier products to track, and whether notifications are in scope. |
| [2–3. Configuration and integration](https://support.ingrid.com/space/KB/486735882/Tracking+configuration+and+integration) | Joint, then you | Getting order and tracking data into Ingrid, mapping carrier products, and embedding the widget on your site. |
| [4–5. Testing and go-live](https://support.ingrid.com/space/KB/486899720/Tracking+testing+and+go-live) | You | Verifying events against the carriers' own tracking, then launching on your domain. |

Configuration and integration share a page because for Tracking they interleave — the widget shows nothing useful until data is flowing.

## What Tracking needs in order to work

Two prerequisites, and both are worth confirming during scoping rather than discovering during testing:

1. **Tracking data.** Ingrid needs your orders, parcels, and tracking numbers. If you use Ingrid Transport, this arrives automatically. If you book shipments elsewhere, your systems have to push it — which makes it integration work.
2. **Carrier product mappings.** Each carrier service needs mapping so Ingrid knows whose events to fetch. Unmapped products produce no events at all. Ingrid Transport users get this automatically; everyone else maps manually.

## Where your tracking lives

- **On your domain.** A page such as *yourbrand.com/tracking* with the widget embedded. This is the default and the one that keeps shoppers in your brand.
- **The Ingrid portal.** Shoppers can check status at [https://tracking.ingrid.com](https://tracking.ingrid.com). A reasonable fallback, and useful before your own page exists.

Tracking events can also feed your CX and marketing platforms, so delivery moments can trigger your own customer communications.

## Need help

- **During implementation:** your implementation consultant is your first contact.
- **Technical questions:** [support@ingrid.com](mailto:support@ingrid.com)
- **API reference:** [developer.ingrid.com](https://developer.ingrid.com/delivery_tracking/)