![]() |
VOOZH | about |
The CData API Server enables you to access Google Campaign Manager 360 data from cloud-based applications like the Salesforce console and mobile applications like the Salesforce1 Mobile App. In this article, you will use the API Server and Salesforce Connect to access Google Campaign Manager 360 external objects alongside standard Salesforce objects.
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Google Campaign Manager 360 OData services:
To work with Google Campaign Manager 360 data from Salesforce Connect, we start by creating and configuring a Google Campaign Manager 360 connection. Follow the steps below to configure the API Server to connect to Google Campaign Manager 360 data:
Google Campaign Manager uses the OAuth authentication standard. The data provider facilitates OAuth in various ways as described below. The following OAuth flow requires the authenticating user to interact with DoubleClick Campaign Manager, using the browser. You can also use a service account to authenticate.
For authentication guides, see the Getting Started section of the data provider help documentation.
π Connecting to a datasource (SQLite is shown)Next, create a user to access your Google Campaign Manager 360 data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the Google Campaign Manager 360 tables:
Having configured a connection to Google Campaign Manager 360 data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsFollow the steps below to connect to the feed produced by the API Server.
URL: Enter the URL to the OData endpoint of the API Server. The format of the OData URL is https://your-server:your-port/api.rsc.
Note that plain-text is suitable for only testing; for production, use TLS.
Select JSON in the Format menu.
After you have created the external data source, follow the steps below to create Google Campaign Manager 360 external objects that reflect any changes in the data source. You will synchronize the definitions for the Google Campaign Manager 360 external objects with the definitions for Google Campaign Manager 360 tables.
After adding Google Campaign Manager 360 data as an external data source and syncing Google Campaign Manager 360 tables with Google Campaign Manager 360 external objects, you can use the external objects just as you would standard Salesforce objects.
Create a new tab with a filter list view:
π A filtered list view shown on a custom tab. (NetSuite Invoices are shown.)Display related lists of Google Campaign Manager 360 external objects alongside standard Salesforce objects:
π A related list that shows an indirect lookup relationship, which links a child external object to a parent standard object. (Salesforce accounts and associated NetSuite invoices are shown.)You can use the following checklist to avoid typical connection problems:
Ensure that the server you are hosting the API Server on is using TLS 1.1 or above. If you are using the .NET API Server, you can accomplish this by using the .NET API Server's embedded server.
If you are using IIS, TLS 1.1 and 1.2 are supported but not enabled by default. To enable these protocols, refer to the how-to on MSDN and the Microsoft technical reference.
If you are using the Java edition, note that TLS 1.2 is enabled by default in Java 8 but not in Java 6 or 7. If you are using these earlier versions, you can refer to this this Oracle how-to.
Learn more or sign up for a free trial:
CData API Server