What's new in v1.10

Campaign performance measurement method(s) must be specified for iOS campaigns

When creating a new iOS app or updating an existing iOS app, you must specify the primary (preferred) and secondary (fallback) methods for measuring campaign performance. For iOS campaigns, campaign performance measurement configuration is now strictly validated to ensure that at least one reliable measurement method is always specified. The following validations are in place.

• The value of ios_primary_measurementmust must be set to either IOS_PRIMARY_MEASUREMENT_SKAN or IOS_PRIMARY_MEASUREMENT_MMP.
• The value of ios_secondary_measurement can't be set to IOS_SECONDARY_MEASUREMENT_UNKNOWN or IOS_SECONDARY_MEASUREMENT_NONE. If you intentionally do not use a secondary measurement for an iOS app, set the secondary measurement to IOS_SECONDARY_MEASUREMENT_NA.

Requests that do not satisfy these constraints for iOS apps will fail validation until the measurement configuration is updated accordingly.

The category property is no longer available for apps

The legacy category property for specifying an IAB category for APP products has been deprecated in favor of the newer, multi-category taxonomy. The category property is now always returned as an empty string "". Any attempt to set or change the category property for an APP product now returns a validation error. For existing APP products, the existing IAB category specified as the value of the category property is auto-appended to the categories property.

When creating a new app, you can specify one or more IAB categories as value(s) of the categories property to categorize an APP product not already listed in our internal app registry going forward. In the event that the app is already listed in our internal app registry, the stored values override the IAB categories you have specified. When updating an existing app, you can't update IAB categories manually for apps listed in our internal app registry.

Campaign-level launch notices

The Campaign APIs now support explicit launch-time notices by returning launch_notices in the response so you can capture and confirm important acknowledgments when launching.

To take advantage of launch notices, be sure to create a campaign object prior to launch. You must create a campaign with the value of enabling_state specified as DISABLED, and then update the campaign with the value of enabling_state specified as ENABLED, and a launch_notice_confirmation object with the same value(s) of launch_notices from campaign creation. Re-entering the value(s) of launch_notices to launch_notice_confirmation serves as confirmation that you have read and acknowledged the launch notices at the time of campaign launch.