We need to build a Google Ads Destination Connector that will allow users to send data from Multiwoven to their Google Ads account for campaign management, audience targeting, or conversion tracking. This connector will help users automate and optimize their ad campaigns by syncing data from various sources into Google Ads.
Requirements
Authentication:
The connector should support OAuth 2.0 authentication to interact with the Google Ads API securely.
Configuration:
The connector should require the following configuration parameters:
client_id: Google Ads API Client ID.
client_secret: Google Ads API Client Secret.
refresh_token: OAuth 2.0 refresh token.
developer_token: Google Ads developer token.
customer_id: Google Ads customer ID (Account ID).
Connector Features:
The destination connector should be able to:
Upload data to Google Ads for the following purposes:
Create/Update campaigns.
Upload audience lists.
Update conversion tracking data.
Provide feedback on the success/failure of data uploads.
API Interaction:
The connector should use the Google Ads API. API documentation can be found here:
Google Ads API Documentation
Data Format:
The data sent to Google Ads should follow the required format for each API endpoint (e.g., Campaign creation, Audience list upload).
Error Handling:
The connector should handle errors gracefully, retrying transient errors and providing meaningful error messages for users.
Steps to Implement
OAuth Authentication:
Implement OAuth 2.0 authentication flow to obtain access tokens to interact with the Google Ads API.
Connector Configuration:
Create a config file that accepts the required Google Ads API credentials.
API Integration:
Implement the logic to send data to Google Ads API for campaign management, audience targeting, and conversion tracking.
Testing:
Write tests to ensure the connector functions correctly with different configurations.
Mock API calls in tests to simulate data uploads.
Documentation:
Provide a detailed document explaining how to configure and use the connector.
Include examples of the data structure needed for successful uploads to Google Ads.
Acceptance Criteria
The connector successfully uploads data to Google Ads (e.g., campaigns, audiences, or conversions).
Proper error handling is implemented, and meaningful logs are generated for failures.
Unit and integration tests cover the most common cases (e.g., valid and invalid data).
linear[bot]
commented
1 month ago
Issue Type New Feature / Connector Request
Description
We need to build a Google Ads Destination Connector that will allow users to send data from Multiwoven to their Google Ads account for campaign management, audience targeting, or conversion tracking. This connector will help users automate and optimize their ad campaigns by syncing data from various sources into Google Ads.
Requirements
Authentication: The connector should support OAuth 2.0 authentication to interact with the Google Ads API securely.
Configuration: The connector should require the following configuration parameters:
client_id: Google Ads API Client ID. client_secret: Google Ads API Client Secret. refresh_token: OAuth 2.0 refresh token. developer_token: Google Ads developer token. customer_id: Google Ads customer ID (Account ID).
Connector Features: The destination connector should be able to:
Upload data to Google Ads for the following purposes:
Create/Update campaigns. Upload audience lists. Update conversion tracking data. Provide feedback on the success/failure of data uploads.
API Interaction: The connector should use the Google Ads API. API documentation can be found here: Google Ads API Documentation
Data Format: The data sent to Google Ads should follow the required format for each API endpoint (e.g., Campaign creation, Audience list upload).
Error Handling: The connector should handle errors gracefully, retrying transient errors and providing meaningful error messages for users.
Steps to Implement
OAuth Authentication: Implement OAuth 2.0 authentication flow to obtain access tokens to interact with the Google Ads API.
Connector Configuration: Create a config file that accepts the required Google Ads API credentials.
API Integration: Implement the logic to send data to Google Ads API for campaign management, audience targeting, and conversion tracking.
Testing: Write tests to ensure the connector functions correctly with different configurations.
Mock API calls in tests to simulate data uploads.
Documentation: Provide a detailed document explaining how to configure and use the connector. Include examples of the data structure needed for successful uploads to Google Ads.
Acceptance Criteria The connector successfully uploads data to Google Ads (e.g., campaigns, audiences, or conversions). Proper error handling is implemented, and meaningful logs are generated for failures. Unit and integration tests cover the most common cases (e.g., valid and invalid data).
Resources
Google Ads API Documentation Google Ads OAuth 2.0 Setup