A dedicated desktop application built to consolidate, monitor, and optimize campaign performance across client accounts under Carlos Franco's Google Ads Manager (MCC).
PPC Hub acts as the nerve center for managing local campaigns. It bridges the gap between manual account optimization and full programmatic control, replacing manual browser tasks with organized, API-driven workflows.
By connecting directly to the Google Ads API, the console delivers live account intelligence that allows rapid, data-backed adjustments without the layout overhead of the web browser.
Consolidates active client accounts into a single performance matrix, pulling spend, clicks, conversion metrics, and impression shares.
SELECT campaign.id, campaign.name, metrics.cost_micros, metrics.impressions, metrics.clicks, metrics.conversions, metrics.search_budget_lost_impression_share, metrics.search_rank_lost_impression_share FROM campaign WHERE segments.date DURING LAST_30_DAYS
GoogleAdsService.SearchStream
Tracks keyword health components (ad relevance, landing page experience, expected CTR) dynamically to flag accounts requiring landing page adjustments.
SELECT ad_group_criterion.keyword.text, ad_group_criterion.quality_info.quality_score, ad_group_criterion.quality_info.creative_quality_score, ad_group_criterion.quality_info.post_click_quality_score, ad_group_criterion.quality_info.search_predicted_ctr FROM ad_group_criterion WHERE ad_group_criterion.type = 'KEYWORD' AND ad_group_criterion.status = 'ENABLED'
GoogleAdsService.Search
Transmits offline walk-in and tour conversion data back to Google's bidding models, linking in-store conversions with click identifiers (GCLID) and call records.
API Endpoint: ConversionUploadService.UploadClickConversions
This loops offline transaction values back to Smart Bidding, ensuring campaign bids optimize against physical sales revenue rather than online page actions alone.
Allows fast keyword bid strategy triage when campaigns are choked by sudden competitor auction entrants or budget caps.
API Endpoint: CampaignService.MutateCampaigns
All mutation calls are gated behind user confirmation. The API is never permitted to perform automated bidding adjustments without human confirmation in the tool's interface.
PPC Hub is a local desktop application built with a zero-cloud security architecture. It ensures client privacy and developer token safety by avoiding remote web servers for credential storage.
Authentication is achieved via the standard Google Ads OAuth 2.0 flow. The application opens a local browser window directing the MCC administrator to Google's authentication page. Upon authorization, Google generates an authorization code that the application exchanges for local access and refresh tokens.
All credential assets—including OAuth client IDs, client secrets, developer tokens, access tokens, and refresh tokens—are stored in an encrypted configuration file situated in the user's home folder (~/.config/ppchub/credentials.json). No credential data is transmitted to, stored on, or shared with third-party servers.
All data transactions between PPC Hub and the Google Ads API flow directly through HTTPS (TLS 1.2+) endpoints to Google. PII uploads (such as emails or telephone numbers collected via customer inquiries for offline-conversions feedback) are fully hashed client-side with SHA-256 before transmission.