Microsoft Advertising Connector¶
The Jitterbit Harmony Microsoft Advertising Connector establishes access to Microsoft Advertising.
The Microsoft Advertising connector provides an interface for creating a Microsoft Advertising connection, the foundation used for generating instances of Microsoft Advertising activities. Activities interact with Microsoft Advertising through the connection and are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).
The Microsoft Advertising connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector can be used only with Private Agents. In addition, it is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
- Getting Started: Initial steps for establishing a connection.
- Advanced Features: User-defined views and SSL configuration.
- Data Model: The data model that the connector uses to represent the endpoint.
- Advanced Configurations Properties: Properties that can be defined to configure a connection for both basic and advanced configurations.
Together, a specific Microsoft Advertising connection and its activities are referred to as a Microsoft Advertising endpoint:
- Query: Retrieves records from a table at Microsoft Advertising and is intended to be used as a source in an operation.
Prerequisites and Supported API Versions¶
The Microsoft Advertising connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.
This connector requires the use of a Private Agent.
Refer to the documentation for information on the schema nodes and fields.
OAuth authentication is supported as described in Configure OAuth Connections.
If you experience issues with the Microsoft Advertising connector, these troubleshooting steps are recommended:
Ensure the Microsoft Advertising connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging for Private Agents to generate additional log files and data.
Enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.verbose.logging.BingAds" level="TRACE"/>
Check the agent logs for more information.