Authorized account discovery
Discover Google Ads client and manager accounts available to the Google user who completed OAuth, then synchronize eligible customer-serving accounts into that EchoVerse AI workspace.
EchoVerse AI connects to Google Ads only after a signed-in customer explicitly chooses to connect Google Ads and completes Google OAuth. The authorization is used to provide the Google advertising, video, reporting, and approved automation features the customer requests.
Discover Google Ads client and manager accounts available to the Google user who completed OAuth, then synchronize eligible customer-serving accounts into that EchoVerse AI workspace.
Support eligible Search and Demand Gen workflows, campaign configuration, budgets, targeting, ad groups, ads, creative assets, scheduling, pause/resume, and related provider operations.
Support approved video workflows, including eligible YouTube video-asset upload through the Google Ads API and provider processing-state tracking.
Retrieve campaign state and performance metrics needed for customer dashboards, monitoring, operational reporting, and optimization decisions.
Use offline authorization for customer-approved background work such as scheduled publishing, account synchronization, status checks, and reporting when the customer is not actively in the browser.
Maintain provider connection status, identify reconnect requirements, prevent unsupported publication, and reconcile provider-side state with EchoVerse AI.
EchoVerse AI does not request or store the customer’s Google password. Google handles authentication and consent.
Provider account identifiers are synchronized from authorized Google access instead of trusting arbitrary account IDs entered in the browser.
Google user data is used to provide requested EchoVerse AI functionality and is not sold to advertisers or unrelated third parties.
The Google Ads connection is not permission to access unrelated Google products or accounts outside the authorization and supported product functionality.
Connected provider resources are associated with the customer workspace and checked against server-side permissions before use.
Customers can disconnect the Google Ads integration in EchoVerse AI and can also revoke access through their Google Account permissions.
Google OAuth tokens and provider credentials are not exposed in customer-facing JavaScript or public WordPress content. EchoVerse AI uses the authorization while the connection is active and applies workspace permissions and provider-readiness checks before supported operations are attempted.