Campaign Manager 360 is an ad management platform which optimizes your digital campaigns across websites and mobile. It provides many useful features for ad serving, targeting, verification, and reporting.

RudderStack supports the Campaign Manager 360's Conversions API which lets advertisers provide information about the offline conversions directly to Campaign Manager 360.

Find the open source code for this destination in the GitHub repository.

Getting started

RudderStack supports sending event data to Campaign Manager 360 via the following connection modes:

Connection ModeWebMobileServer
Device mode---
Cloud modeSupportedSupportedSupported

Once you have confirmed that the source platform supports sending events to Campaign Manager 360, follow these steps:

  1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select Campaign Manager 360.
  2. Assign a name to your destination and click Continue.

Connection settings

To successfully configure Campaign Manager 360 as a destination, first authenticate your account by following the below steps:

  1. Click Create Account in the Account Settings section.
  2. From the modal, click the Sign in with Google button.
  3. Choose the required account and grant RudderStack the required permissions.
  4. Click Save to use the specified account, as shown:
Google Account authentication
In case you have authenticated multiple accounts, you can click Edit Credentials to select or delete any other authenticated account, as shown:

Google Account authentication

RudderStack gives an error if you try to delete an account used by any other connection set up for the same destination.

Next, configure the following settings:

  • Profile ID: Enter the user profile ID associated with the request.
Refer to the batchinsert and batchupdate methods of the Campaign Manager 360's Conversions API for more information on the profile ID.
  • Limit ad tracking: Enable this setting to report a conversion and not target it.
  • Child directed treatment: Enable this setting if you want to allow requests from users under the age of 13 (required for COPPA compliance).
  • Non personalized ad: Enable this setting if the conversion is for a non-personalized ad.
  • Treatment for underage: Enable this setting if you want to allow requests from users under the age of 16 (required for European Union's GDPR compliance).
You can also pass values for all these dashboard settings in the track call which will take precedence over the values passed in the dashboard. Refer to the Campaign Manager 360 documentation for more information on these settings.


You can use the track call to capture user events along with the associated properties and send them to Campaign Manager 360.

A sample track call is shown below:

rudderanalytics.track("Product Reviewed", {
"profileId": 437689,
"floodlightConfigurationId": "213123123",
"ordinal": "3",
"floodlightActivityId": "456543345245",
"mobileDeviceId": "mobileDeviceId",
"value": 7,
"encryptedUserId": "encrepyteduserId"
"impressionId": "string",
"limitAdTracking": false,
"childDirectedTreatment": true,
"encryptionInfo": {
"kind": "dfareporting#encryptionInfo",
"encryptionSource": "AD_SERVING",
"encryptionEntityId": "3564523",
"encryptionEntityType": "DCM_ACCOUNT"
"requestType": "batchinsert"

Property mappings

The following table lists the event property mappings between RudderStack and Campaign Manager 360:

RudderStack propertyCampaign Manager 360 propertyData type
Note the following important points:
  • Apart from the above-mentioned properties which are marked as required, you must also send properties.requestType in the conversion event with the value as batchinsert or batchupdate.
  • Every conversion event must contain all the required fields and at least one of the optional fields.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page