Clan/guild join as a UA moment, not a social feature dump
Checklist for selling clan/guild join as a UA moment that exists in early sessions, under accurate-metadata rules.
Clan join is a UA moment only if the new user can reach it when the ad implies they can. Apple 2.3 Accurate Metadata requires the product to match marketing.
Operator checklist
- Session gate: State the earliest session/level where join is possible.
- Auto-assign vs apply: Creative must match the live flow.
- Benefit shown (chest, war, chat) must be available to the joining cohort.
- Empty-clan risk: Do not advertise active wars if new clans start idle.
- Deep link: If CPP/CSL/deep link promises a clan invite, test the path on install.
- Moderation: Clan chat in ads must not violate network social-ad policies.
- Metric: Join rate and D7 retention are separate; do not treat join as proof of payer quality.
Limits
No observed clan ad is attached. This is an ops checklist, not a creative casefile.
