Returns Digital Marketing (Amplify) performance per property, day and campaign type: impressions, clicks, spend, attributed reservations and revenue, for the properties named in the required x-property-id header. Covers every requested property or none: if the API key or app cannot access a requested property, the property's account status does not allow API access, or the export is not enabled for it, the whole call fails with HTTP 403, listing the rejected property IDs when the denial can be attributed to specific properties. The token must carry the read:marketingPerformance scope, whatever other access it has: select "Read Digital Marketing performance (clicks, spend, bookings, revenue)" under Marketing Performance when creating the API key, or request the scope in the OAuth app. Up to 50 properties and 90 days per call, and 20 calls per minute per API client (HTTP 429 with a Retry-After header above that). JSON responses are paged with limit and offset over rows sorted by propertyId (as a number), date and campaignType in the order METASEARCH, METASEARCH_MANAGED, PMAX, PMAX_MANAGED, RETARGETING, OTA_TRAVEL_ADS; keep paging until a page has fewer than limit rows. Spend is converted from USD with the daily exchange rate of each row's date, so for past dates it can differ from the Performance Dashboard cards, which use today's rate. Rows of the last 14 days are PROVISIONAL. Accept: text/csv returns the same fields for the whole date range as one CSV document, not paged, with a header row naming each field, where spendUsd, spend and revenue are plain decimal amounts in major currency units (spendUsd in USD, spend and revenue in the currency named by currencyCode) and an omitted field is an empty cell; application/json or an omitted Accept returns JSON; anything else is answered with HTTP 406.