What are the current guidelines for install attribution

The current guidelines for install attribution using AdAttributionKit, as presented at WWDC, include the following key points:

Conversion Types: AdAttributionKit supports different conversion types, including installs, re-downloads, and re-engagements. The conversion type field in the postback will indicate the type of conversion event that occurred (Meet AdAttributionKit).
Postbacks: Postbacks are the outputs of the attribution system, containing conversion signals sent to the ad network and optionally to the developer of the advertised app. These postbacks include a combination of signed compact JWS and a few unsigned fields (Meet AdAttributionKit).
Testing: AdAttributionKit includes a developer mode to facilitate testing. This mode removes time randomization, shortens conversion windows, and speeds up postback transmission to make testing more manageable (Meet AdAttributionKit).
Enrollment and Implementation: Ad networks need to enroll with AdAttributionKit. After enrollment, they should serve ads in the new JWS format and use the AdAttributionKit APIs for updating conversion values on the server side. The framework is fully interoperable with SKAdNetwork (Meet AdAttributionKit).
Privacy: AdAttributionKit is designed with privacy in mind, building on the fundamentals of SKAdNetwork and crowd anonymity. This ensures that user privacy is preserved while still providing valuable attribution data (Meet AdAttributionKit).

For more detailed information, you can refer to the session Meet AdAttributionKit.