Event Taxonomy Mapping
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.
How this sits next to the baseline
Legacy apps accumulate names. Screen titles in Malay, English remnants from an old contractor, button events that only fire on one flavour: the destination SDK will not guess any of that. This engagement produces a mapping sheet with the old string, the new string, and a note where the vendor will reject a character or a length.
It pairs naturally with a baseline. On its own it is useful when engineering already has a screen list and only the naming work is outstanding.
Duration. One to two weeks for a single client with a known event list.
Fees. Priced by event volume and by how much renaming the destination vendor forces.
Ask about this engagement
Name the app, the destination you are moving toward, and the date you are protecting. We reply within two working days.
Write to the practice