Rustomjee × Mitasys
What has been built on the MoEngage container, what each event actually measures, and the evidence behind every change. Written for the people who need to validate it: MoEngage, Rustomjee and the website team.
Every element on the live site that sends an event to MoEngage, highlighted on a screenshot of the real page. Hover any box to see which event it sends, which trigger matches it, and what that event collects. The boxes are measured from the container's own triggers rather than drawn by hand, so a trigger that stops matching the site fails the build instead of failing silently.
Every attribute we send to MoEngage, checked against what MoEngage actually received rather than against what the tags are configured to send. Three attributes have never once arrived, one is empty in 46 of 47 events, and 17 tags send a value MoEngage already collects for free. The proposal removes 20, adds 4, and rewires 2, with the measured evidence for each.
A second enquiry from the same browser was overwriting the first person's profile rather than creating its own, so one number pointed at someone else and the other at nothing. What caused it, the change now live on the MoEngage container, and the four independent checks that prove it works. Includes a simulator: submit enquiries as three people, with the gate off and on, and watch what happens to each profile.