# Appsflyer Event Validation

> Validate that expected AppsFlyer SDK events and callbacks were triggered during an end-to-end Unity app scenario using logs, callback payloads, and test evidence.

- Skill: `appsflyersdk/appsflyer-event-validation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add appsflyersdk/appsflyer-event-validation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/appsflyersdk/appsflyer-event-validation/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: appsflyersdk (https://skillmd.com/u/appsflyersdk)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/appsflyersdk/appsflyer-event-validation

---


# AppsFlyer Event Validation

Use this skill when validating whether AppsFlyer-related events actually fired during an app scenario.

## Goal

Compare expected AppsFlyer events against real evidence from logs, callbacks, or assertions.

## Workflow

1. Identify the scenario under test.
2. Define the expected AppsFlyer events or callbacks for that scenario.
3. Collect evidence from: Unity console logs, Android logcat, iOS simulator logs, C# callback payloads.
4. Match expected events against actual evidence.
5. Classify each expected event as: Confirmed triggered | Missing | Duplicate | Unclear | Blocked by environment.
6. Summarize the result.

## Output Format

Return:
- Scenario
- Platform
- Expected AppsFlyer events
- Confirmed triggered events
- Missing events
- Duplicate or unexpected events
- Relevant evidence
- Final status: Passed | Failed | Inconclusive | Blocked

## Rules

- Do not assume an event fired because the app launched.
- Confirm events only from logs, callbacks, or assertions.
- If logs are insufficient, say `needs more logging`.
- Separate verified facts from assumptions.