A validation pass stalls on the export more often than on the parser. The usual failures: debug and production in one file, no source column, a date range that ends before the redesign you care about, or a sample that includes extra personal fields the analytics events do not need.
A file we will actually open
- Timestamps in one timezone, stated in the covering note.
- Event name as sent, not as displayed in a pretty console label.
- Properties as nested JSON or flattened columns, not screenshots.
- A source field: iOS, Android, web, OEM build if it matters.
- Fourteen to thirty days, covering any store release you want examined.
If the tracking plan exists, send it even if it is embarrassing. A neglected spreadsheet is still a claim about what the reports assume. We compare the payload with that claim. If there is no plan, say so; reconstruction may need to sit in front of validation, and we would rather know at enquiry than in week two.
What to leave out
Internal user accounts, if you can filter them. Crash logs. Ads network exports. Identity graphs. They belong to other conversations. The covering note should list the five reports that would cause an argument if the count moved — that list is how Amina ranks the findings, and it cannot be invented in the workshop.
When the file is ready, enquire with the catalogue size and sources. The engagement page spells out the four stages that follow.