Each engagement produces a written artefact you can hand to engineering and to whoever owns the Monday pack. We do not install software or run a hosted property.
A written inventory of what your current app actually records, which figures will go dark at cutover, and what the destination build must capture before the old version is retired.
Open the engagement
A timed check in the weeks around freeze: whether the destination build actually emits the events the baseline named, and which charts will need a footnote on the week you switch stores.
Open the engagement
A mapping from the names your legacy app already uses — screen titles, event strings, user properties — onto the vocabulary the destination SDK and the receiving property will accept.
Open the engagement
A comparison of the first complete reporting period on the new build against the baseline, with a short list of missing events, double counts, and figures that should not be charted year-on-year yet.
Open the engagement
A facilitated half-day with product, engineering, and whoever currently owns the weekly numbers, used to agree what must be instrumented before freeze rather than to present a slide deck.
Open the engagement