Clan/guild join as a UA moment, not a social feature dump

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

1. Session gate: State the earliest session/level where join is possible.
2. Auto-assign vs apply: Creative must match the live flow.
3. Benefit shown (chest, war, chat) must be available to the joining cohort.
4. Empty-clan risk: Do not advertise active wars if new clans start idle.
5. Deep link: If CPP/CSL/deep link promises a clan invite, test the path on install.
6. Moderation: Clan chat in ads must not violate network social-ad policies.
7. 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.

Download the evidence table.

Research checked 20 September 2026. Local draft; human editorial review pending. No CMS write performed.