Use this article to implement Ingrid Engage tracking: what each implementation phase covers for Ingrid Engage, what Ingrid Engage tracking needs in order to work, and where your tracking page lives.
This article is for retailers implementing Ingrid Engage (order tracking and delivery notifications), and for their developers. Implementing Ingrid Engage follows the same five implementation phases as any Ingrid implementation. This article covers what is specific to Ingrid Engage.
The implementation phases for Ingrid Engage
The table below shows each implementation phase for Ingrid Engage, who leads it, and what it covers:
Phase | Who leads | What it covers for Ingrid Engage |
Ingrid | Where tracking data comes from, your tracking page address, which carrier products to track, and whether notifications are in scope. | |
Joint, then you | Getting order and tracking data into Ingrid, mapping carrier products, and embedding the Ingrid tracking widget on your site. | |
You | Verifying tracking events against the carriers' own tracking, then launching on your domain. |
For Ingrid Engage, configuration and integration share one article because they interleave: the Ingrid tracking widget shows nothing useful until tracking data is flowing.
What Ingrid Engage tracking needs in order to work
Ingrid Engage tracking has two prerequisites, and both are worth confirming during scoping rather than discovering during testing:
Tracking data. Ingrid needs your orders, parcels and tracking numbers. If you use Ingrid Transport, tracking data arrives automatically. If you book shipments elsewhere, your systems have to push the tracking data to Ingrid, which makes it integration work.
Carrier product mappings. Each carrier service needs mapping, so Ingrid knows whose tracking events to fetch. Unmapped carrier products produce no tracking events at all. Ingrid Transport users get carrier product mappings automatically; everyone else maps them manually.
Where your Ingrid Engage tracking page lives
Your shoppers can follow their delivery in one of two places:
On your domain: a page such as yourbrand.com/tracking with the Ingrid tracking widget embedded. This is the default, and the option that keeps shoppers in your brand.
The Ingrid tracking portal: shoppers can check delivery status at tracking.ingrid.com. A reasonable fallback, and useful before your own tracking page exists.
Ingrid Engage tracking events can also feed your CX (customer experience) and marketing platforms, so delivery moments can trigger your own customer communications.
Getting help with your Ingrid Engage implementation
During implementation: your Ingrid implementation consultant is your first contact.
Technical questions: Iris, Ingrid's AI assistant, in the chat on the Ingrid Help Center. If you can't reach Iris, email [email protected].
API (application programming interface) reference: developer.ingrid.com