Changelog

To reduce response sizes, you can now use paging and sorting with the campaigns endpoint.

1. Invoking the campaigns endpoint with a network account now returns all campaigns across the network.

   (Previously, this would return 0 results.)

2. To reduce the response size, apply paging and sorting.
3. You can also filter for specific campaigns: GET backstage/api/1.0/{network-account}/campaigns/?campaign_ids=123&campaign_ids=456

Conversion Rules now support a configurable view_through_look_back_window.

The Campaign Summary Report now priovides a breakdown of ROAS according to clicks and views.

The Password Credentials flow for Backstage API has been deprecated.

Within a given item (ad), you can now use the custom_dataproperty to store additional information about the creative.

Backstage API now supports 4 bidding strategies.

You can now use the following reports to fetch (near) real-time data:

Going forward, the Verification Pixel (aka 3rd Party Pixel) can be set at the campaign or item level.

When using the campaign_hour_breakdown dimension, always pass a date and time for the reporting interval. (The values passed should reflect the time zone of that account.)