Add Apple Ad Attribution Kit (AAK) version 1.0 extension

[joseph-shi-vungle]

Changes

• Added AAK extension definition in /extensions/community_extensions/
• Documentation for AAK integration
• Schema definitions for AAK objects

Location

Files added under: extensions/community_extensions/adattributionkit/

Testing

• Schema validation passed
• Documentation reviewed
• Example implementation provided

References

• Apple AAK Documentation: [link]

Checklist

• Follows OpenRTB extension guidelines
• Documentation included
• Schema properly defined
• No breaking changes

[AramZS]

Hi @joseph-shi-vungle - this all makes sense to me. I have two concerns that I would consider blocking in this specification:

1. The documentation for sourceapp notes that it should use the iTunes item identifier. However, I would assume that this might be open to another app store if one were to ever rise on Apple devices, or if this were extended for use in non-Apple devices. I think this should be changed to a more generic App Store
2. Basically the same issue for itunesitem. It should not assume iTunes will be the only user of the spec or that iTunes will be the only app store on the device to potentially use it. It should be renamed generically. Something like appStoreID or something along those lines.

[joseph-shi-vungle]

Hi @AramZS ,

thanks for the review. I agree with both concerns.

The spec should not be tied specifically to iTunes, nor should it assume that iTunes/Apple will be the only app store or platform using this field. The intent is to represent the app’s store identifier in a generic way.

I have updated the sourceapp documentation to refer to a generic app store identifier instead of the iTunes item identifier, and we also review the related examples and descriptions to remove any iTunes-specific wording. This should address the blocking concerns, but please let us know if a different generic field name is better.