Purpose and current status
CandorReviews Campaign Workflow is a developer project associated with CandorReviews. It is separate from the public product guides on this website. Its purpose is to connect an internal preparation and review workflow with authorized Google Ads accounts, not to replace the Google Ads interface or Google Ads Editor.
The Google Ads integration is in development. This public website provides project documentation; it does not currently connect Google accounts, collect OAuth tokens, display account reports or submit campaign changes. Google Ads API approval, verified-brand status and completed production functionality are not claimed. There is no public registration, subscription or working Google sign-in button on this page.
Who the application is for
The intended operator is an independent developer using an internal workflow for accounts they own or have explicit permission to manage. This is not an open account-access service or a claim that CandorReviews is an advertising agency, incorporated company, Google partner or Google-certified provider.
A product-review website does not itself grant access to an advertiser account. Account access must come from valid Google authorization and the permissions on the relevant Ads account. The app must not access an unrelated account merely because it is reachable through a manager-account hierarchy.
Prepare, validate and approve
The planned workflow starts with campaign inputs prepared outside Google Ads. Quality-control checks cover required fields, destination URL format, campaign naming, duplicate assets, applicable text limits, keyword settings, proposed targeting and budget values. Passing a local check does not establish Google policy approval or guarantee ad delivery.
An authorized operator reviews the proposed changes and target account before submission. The application is intended to show what will change and require an explicit approval step for writes. Reporting or browsing this public website must never silently authorize a campaign launch or a budget change.
Planned campaign and reporting functions
Where implemented and permitted, the integration will support creating or updating Search campaigns, ad groups, responsive search ads, keywords, negative keywords, budgets and targeting settings. Only functions actually implemented and described to the operator should be enabled.
Read operations are intended to retrieve authorized account identifiers, campaign structure and status, policy-related results and aggregate performance such as impressions, clicks, cost and conversions. Failed operations and API responses will support error investigation and reconciliation. The app is not designed to collect individual ad viewers' identities or Google passwords.
Authorization and account boundaries
A future connection must use the appropriate official Google OAuth flow and a correctly configured client. The operator will authenticate on Google, see the requesting app and requested permissions, and choose whether to authorize access. Credentials must never be requested by a form on this product-review website.
The implementation will request only permissions needed for its available functions. Access to campaign management does not remove the need for account-level authorization, write approval, Google Ads policies or service-specific limits. Google Ads account creation, user invitations, billing management, scraping and policy circumvention are not part of this project description.
Google data and the public website
Google account credentials, tokens, account reports and campaign exports must not appear in public HTML, browser storage used by this website, product articles, image assets or the public deployment bundle. The public saved-article feature is unrelated to the planned Ads integration.
Current collection through this website: none for Google account data and Ads account data. The privacy policy explains the intended integration separately from the existing static website. Production access must not be enabled until the real implementation, data storage arrangements and published disclosures agree.
Privacy, revocation and support
Read the Google user data section of the privacy policy and the revocation and deletion instructions. An operator will be able to revoke a future connection from their Google Account connections settings. Revocation stops future authorization; it does not automatically undo campaign changes already applied in Google Ads.
Contact chesticksantbab@gmail.com for application, privacy or deletion questions. The Google authorization screen must show the same app name and support address. Publishing this contact does not mean the integration is connected or approved; this page must not be presented as a functioning production connection.
Relationship to CandorReviews
CandorReviews remains a product-information publication. Its guides, commercial disclosures and manufacturer images are separate from any authorized Google Ads account information used by this developer project. Reading an article does not enroll the reader in the application or request Google permissions.
Google and Google Ads are trademarks of their respective owner. Their names describe an intended integration, not endorsement or a business relationship. Brand verification, API access approval and any required OAuth data-access verification are separate processes controlled by Google.
Keep in touch
Questions about an article or this website? Contact CandorReviews.