What's new in v1.11

reason in error response now returns more granular values

The reason field within the details object included in error responses now returns more specific, granular reason values than in prior versions. If your integration parses or matches on reason, review the updated set of values and update your error-handling logic accordingly.

app.autoinline_enabled and app.storekit_enabled are deprecated

The app.autoinline_enabled and app.storekit_enabled properties on App product are now deprecated.

• When creating a new app, both fields are enabled by default.
• When updating an existing app, the existing stored values for both fields are preserved regardless of what is submitted in the request.

iOS App products must specify measurement methods for create or update operations

Building on the validation introduced in v1.10, iOS App products can't be created or updated at all unless both app.ios_primary_measurement and app.ios_secondary_measurement are specified. Requests missing either value will result in a validation error.

Campaign launch requires explicit acknowledgment of launch notices

Campaigns that receive launch_notices value(s) in the response (introduced in v1.10) must now echo the same value(s) back as launch_notice_confirmations in order to launch. If a campaign has outstanding launch_notices value(s) needing confirmation, launching the campaign will fail.

The updated campaign launch flow is as follows. 1) Create the campaign with enabling_state set to DISABLED, 2) review any launch_notices returned, 3) and finally update the campaign with enabling_state set to ENABLED and launch_notice_confirmations matching the launch_notices value(s).

app.category is no longer available

The app.category property, deprecated in v1.10 in favor of app.categories, is fully removed. The app.category property is no longer returned or settable on App product. Use app.categories instead to specify one or more IAB categories going forward.