Synvu Limited — Version 1.0, April 2026
Synvu Limited uses the Google Ads API to manage paid search and display campaigns across its portfolio of software products. Rather than managing campaigns manually through the Google Ads web interface or via ad-hoc Bulk Scripts, Synvu uses internal tooling to manage campaign configuration programmatically — version-controlled, peer-reviewed, and applied through automated pipelines.
This integration is not a product, service, or platform offered to customers. It exists solely as an internal tool used by Synvu Limited employees to manage our own advertising. Synvu Limited is not a third-party ads management platform, does not provide Google Ads management services to external clients, and does not share or resell API access in any form.
Scope of access: All usage of the Google Ads API is limited to accounts owned and operated by Synvu Limited. The API is used exclusively to promote Synvu's own software products. No external or third-party account access is requested or used.
Each Synvu product runs independent Google Ads campaigns targeting distinct audiences. The API integration manages campaigns for all four products from a single engineering platform:
Campaign definitions — including structure, ad groups, keywords, match types, bids, budgets, and ad creative — are stored as YAML or JSON configuration files in version-controlled Git repositories. Each product has its own campaign configuration directory.
All changes to campaign configuration go through a pull request and code review process, providing a complete auditable history of every campaign change made across all products.
A Python-based service acts as the bridge between campaign configuration files and the Google Ads API. This service handles authentication, campaign synchronisation, idempotency checks, and error handling.
Before any changes are applied to a live account, the service performs a dry-run validation step that calls the Google Ads API in read-only mode to confirm the proposed configuration is valid.
The API integration layer is invoked via GitHub Actions. The full workflow for every campaign change is:
An engineer modifies a campaign configuration file and opens a pull request for team review.
The CI pipeline runs a dry-run validation step, calling the Google Ads API in read-only mode to verify the proposed configuration is valid and consistent with existing account state.
The pull request is reviewed and approved by a second engineer before merging.
On merge to the main branch, the pipeline applies the configuration changes to the relevant Google Ads account via the API.
Post-deploy, the pipeline queries campaign state to confirm changes were applied successfully and raises an alert if anything is unexpected.
We use internal analysis tools to assist with campaign optimisation. All suggested changes are treated as drafts — reviewed and approved by a Synvu employee before any changes are applied to live campaigns.
Uses the KeywordPlanIdeaService to surface relevant keyword suggestions based on product descriptions, landing page content, and target audience parameters. Suggestions are presented as configuration file additions for human review.
Pulls optimisation recommendations via RecommendationService and surfaces them to engineers for consideration. Recommendations are never applied automatically — each one requires explicit human approval.
Queries campaign performance data via GoogleAdsService and uses internal analysis tools to summarise trends, identify underperforming ad groups, and suggest optimisations for human review before any changes are applied.
The following Google Ads API services are used within the integration:
Create, update, and manage campaigns across all four Synvu products.
Create and manage ad groups within campaigns.
Create and manage responsive search ads and other ad formats.
Manage keywords, match types, and negative keywords at the ad group level.
Set and programmatically adjust campaign budgets.
Configure and manage bidding strategies for each campaign.
Query campaign, ad group, and keyword performance data for reporting and monitoring.
Generate keyword suggestions to support AI-assisted campaign building.
Retrieve and selectively apply Google Ads recommendations after human review.
OAuth 2.0 tokens and the developer token are stored as encrypted secrets within the CI/CD platform (GitHub Actions). Credentials are never committed to source control and are not accessible outside of the CI/CD pipeline execution environment.
Authentication follows Google's OAuth 2.0 service account flow. No credentials are shared with any third party.
Every campaign change is traceable via Git commit history and CI/CD run logs. No campaign change can reach a live Google Ads account without passing through code review and the CI/CD pipeline validation step.
All AI-generated campaign changes require human review and explicit pull request approval before deployment.
Third-party access: The Google Ads API integration is scoped exclusively to Synvu Limited's own accounts. No third-party Google Ads accounts are accessed, managed, or connected. API access is not offered, resold, or shared externally under any circumstances.
Synvu Limited is a privately held UK technology company incorporated in 2024. We design, build, and operate a portfolio of software products serving businesses across cloud security, property intelligence, and digital marketing.
For questions about this API integration or any compliance matter, please contact us directly.
Email: info@synvu.com