Technical overview
How the 1706 Digital Marketing internal operations tool uses Google Ads.
Operating model
This is an operator-managed tool for authorized advertiser accounts, not a public Google Ads API proxy, a credential-sharing service, or a public self-service API. A restricted Telegram interface provides operator intake and status notifications. The informational website does not provide account login or collect Google passwords.
Authorization and workflow
- An authorized operator receives an advertiser's customer ID.
- The advertiser administrator accepts a manager-account link in Google Ads, or grants direct administrative access through Google's own invitation flow.
- The tool verifies the exact active link or direct administrative authorization through Google Ads API before campaign work.
- Search campaign creation is validated first; resulting resources and status are checked afterward. Existing resources are reconciled to avoid duplicates.
- Monitoring, reporting, bidding and geographic controls, and ad-policy maintenance operate only within authorized access. Quota or policy errors stop or defer affected work.
A manager-account link authorizes account access. It is separate from Google's approval of the tool's API access level.
Data and security
The operator holds OAuth and API credentials; they are not issued to advertiser clients. Google API requests use HTTPS. The operator host uses full-disk encryption, and local credential files have restricted filesystem access. This is not a claim of per-file key-management service integration or independent security certification.
Operational records include account and campaign identifiers, processing state, reports and logs. Removing access stops new authorized operations, but does not automatically erase historical records. See our privacy policy for retention, processing and deletion-request information.
Review and support
Reviewers can consult the authorization and revocation guide. Further technical questions or a supervised demonstration can be requested at sirunytrrv11@gmail.com. No public demo contains live client data or credentials.