Use this article to configure Ingrid Engage and integrate it into your site: providing tracking data, setting up carrier product mappings, building your tracking page, and getting shoppers to it.
This article is for merchants and project teams in phases 2 and 3 of an Ingrid Engage implementation. Ingrid Engage configuration is joint work; you lead Ingrid Engage integration.
Configuration and integration are covered together because for Ingrid Engage they interleave: the tracking widget, part of Ingrid Engage, cannot show anything useful until data is flowing, and data is not worth verifying until the tracking widget is somewhere you can see it.
Phase 2: Ingrid Engage configuration
Providing tracking data to Ingrid Engage
Ingrid Engage needs orders, parcels, tracking numbers, and carrier product mapping in order to track anything.
If you use Ingrid Transport, this happens automatically. If you book shipments elsewhere, your systems push the data to Ingrid. See the developer documentation for how.
Providing the order ID alongside the tracking number is worth doing: it lets the tracking widget show events from before the parcel ships, such as order confirmed and order prepared, which is often the period shoppers are most anxious about.
Carrier product mappings in Ingrid Engage
Carrier product mappings connect a tracking number to the carrier service behind it, so Ingrid Engage knows which carrier's events to fetch. Without a mapping, a shipment produces no events.
If you already use Ingrid Transport, all carrier products are mapped automatically.
If not, mapping is manual, and the process differs depending on whether the product is booked through Ingrid or externally.
Carrier product mappings live in the Ingrid Merchant Platform under Delivery Tracking → Product mappings. See Carrier product mapping in Ingrid Engage, and the developer documentation for the detail.
Once carrier product mappings are configured and your tracking settings are finalized with your implementation consultant, Ingrid Engage starts retrieving events from carriers.
How Ingrid Engage harmonizes carrier events
Carriers differ widely in which events they emit and how they word them, and because parcels are polled continuously, raw carrier feeds often contain near-duplicate events.
Ingrid Engage filters the redundant events and formats the rest consistently, so the progress a shopper sees looks the same regardless of which carrier is delivering. This is worth knowing during testing: if an event you expected is missing, the first question is whether the carrier emitted it at all.
Phase 3: Ingrid Engage integration
Your Ingrid Engage tracking page
Create a page on your own domain, commonly yourbrand.com/tracking, and embed the tracking widget. The tracking page needs nothing else: Ingrid Engage handles order number and email input itself.
Getting shoppers to your Ingrid Engage tracking page
There are three routes to the tracking page, and most merchants use more than one:
An authorized link. The link contains the tracking data already, so it opens a personalized view directly. This is what you put in delivery notifications.
A general link to your tracking page with no data attached. The tracking widget waits for the shopper to identify their order by entering their order number and email.
A tracking section on your site. Shoppers navigate to it rather than following a link, then enter their details in the same way as with a general link.
The Ingrid tracking portal as an alternative to your own tracking page
Shoppers can also check parcel status at https://tracking.ingrid.com. Embedding the Ingrid Engage tracking widget on your own site keeps shoppers in your brand and your flow, so it is the better default. The portal is a legitimate fallback, though, and it improves self-service where you have not built a tracking page yet.
What the Ingrid Engage tracking widget looks like
In the tracking widget, delivery, progress, and order details are folded by default, giving an at-a-glance view that the shopper can expand.
Split deliveries are tracked per parcel in the tracking widget, each parcel with its own progress bar.
For installation and the application programming interface (API) detail behind all of this, see the developer documentation.
Who does what in Ingrid Engage configuration and integration
Ingrid:
Sets up your Ingrid Engage tracking account to reflect your requirements
Guides the data flow between your systems and Ingrid
Reviews any customization beyond the standard setup
You:
Integrate Ingrid Engage into your stack, so orders and tracking numbers reach Ingrid
Embed the tracking widget on your tracking page
Run a first tracking test and confirm that what Ingrid Engage shows matches the carrier's own portal