Use this article to test your Ingrid Engage setup, plan your go-live, and know what to expect once Ingrid Engage is live.
This article is for merchants and project teams in phases 4 and 5 of an Ingrid Engage implementation. You lead both Ingrid Engage testing and go-live. Ingrid supports you, helps resolve what you find, and runs hypercare alongside you after launch.
Phase 4: Ingrid Engage testing
Ingrid Engage testing is different from Ingrid Promise testing in one important way: it depends on real carrier events. You cannot fully verify Ingrid Engage without shipments that actually move, so plan for real bookings rather than only synthetic tests.
What to verify when testing Ingrid Engage
Tracking data arrives. Confirm your orders, parcels, and tracking numbers reach Ingrid, either from Ingrid Transport automatically or from your own systems if you push them.
Carrier product mappings resolve. Every carrier product in use should be mapped, so Ingrid Engage can fetch that carrier's events. An unmapped product means no events.
Events appear and are accurate. Compare what the tracking widget, part of Ingrid Engage, shows against the carrier's own tracking portal for the same shipment. They should agree.
The tracking widget loads on your site in every market and language you serve, with the correct locale.
Both entry routes work: an authorized link with predefined data, and the general tracking page where the shopper types their details.
Multiple parcels behave correctly where you ship split deliveries: each parcel should track separately.
Notifications fire as configured, if you use email or text message (SMS) updates, and read correctly in every language.
Test Ingrid Engage with at least one real shipment per carrier. Carriers differ in which events they emit and when. A carrier product mapping that looks correct in configuration can still produce gaps once real events arrive, and that only shows up with a live parcel.
Phase 5: Ingrid Engage go-live
Replicate your configuration into staging. Ingrid copies your Ingrid Engage tracking configuration across before launch, so from go-live onward you have a configured staging environment to test changes in. The two environments do not sync, so this is a deliberate copy.
Confirm the tracking page is live on your own domain, and linked where shoppers will look for it: order confirmation, account pages, and your delivery notifications.
Choose your rollout shape. Launch Ingrid Engage in every market at once, or in a pilot market first. See Big bang or phased.
Launch. You lead the Ingrid Engage cutover.
Hypercare. Ingrid runs hypercare alongside you after launch, which matters for Ingrid Engage because event quality across carriers is only visible at real volume.
Handover. When hypercare ends, the Ingrid Customer Success and Support teams become your ongoing contacts.
What Ingrid Engage go-live produces
A Branded order tracking page live on your domain
Accurate, harmonized events for every carrier product you use
A configured staging environment for testing future Ingrid Engage changes
Shoppers reaching tracking without contacting your support team