The Campaign Manager 360 (CM360) integration connects your CM360 account to Medialake. It browses your user profiles and advertisers, ingests the images, videos, and audio behind your creatives as media files, and reports how the ads using those files performed, day by day. Medialake never edits, traffics, or uploads anything in your CM360 account. The only thing it creates is a temporary report, which it deletes as soon as the numbers are downloaded.
At a glance
Property | Value |
Category | Advertising |
Auth method | OAuth 2.0 — Google sign-in |
Permissions |
|
API | Campaign Manager 360 API (v5) |
Token renewal | Automatic (Google refresh tokens) — expires only after ~6 months unused |
Focus | Creatives and media assets, plus daily performance for the ads that use them |
Performance history | Up to 24 months, with the most recent 30 days refreshed as CM360 updates them |
What it syncs
The CM360 structure — user profiles and advertisers — plus the creatives behind your campaigns. The media inside each creative is ingested as files: images, videos, and audio, each with the creative context it belongs to.
For performance, Medialake also reads the campaigns, placements, and ads that use those creatives, then collects each ad's daily delivery metrics — impressions, clicks, video plays, engagements, conversions, and spend — so you can see how each file performed. See Metrics Reference for what every metric means.
>Connected before performance reporting was added? Reading performance needs an extra Google permission (dfareporting). Existing connections keep syncing files, but performance only starts once you reconnect and approve the new permission. See Authentication.
Pages in this integration
Authentication — the permissions we request, who should connect, and how to revoke access
Data Mapping — the objects we sync and the exact fields we read
Metrics Reference — every performance metric, what it means, and where it comes from
Questions? Contact [email protected].