How SafeS Pay Uses the Google Ads API

Primary API Purpose

The product uses the Google Ads API for ecommerce conversion reporting workflows. After a merchant-owned site receives a confirmed paid order, SafeS Pay can prepare and upload a purchase conversion tied to the merchant's authorized Google Ads customer account.

Current Google Ads API workflow

• Refresh an OAuth access token for an authorized merchant or server-owned Google Ads connection.
• Upload confirmed click-based purchase conversions with uploadClickConversions.
• Use merchant-provided Customer ID, optional MCC Login Customer ID, Conversion Action ID, timezone, and conversion settings.
• Record upload status, partial failure messages, retry attempts, and audit logs for merchant review.

What We Do Not Do

SafeS Pay is intentionally not an ad management product. The platform does not expose public tools for changing advertising strategy or account structure.

• No campaign creation or campaign edits
• No budget, bid, keyword, asset, creative, placement, or audience management
• No resale of Google Ads account data or anonymous third-party access
• No upload of fabricated, duplicated, or unverified conversion events

Order-to-Conversion Data Flow

Data Categories Used

• Order ID or session ID
• Order amount, currency, and conversion time
• Advertising click identifiers such as GCLID, GBRAID, WBRAID, or DCLID when available
• Google Ads Customer ID, Conversion Action ID, and optional MCC Login Customer ID configured by the merchant or authorized operator
• Optional SHA-256 hashed email for enhanced conversions only when enabled and lawfully authorized

SafeS Pay does not need campaign names, ad creative text, keyword plans, budgets, bid strategies, or audience lists to perform this workflow.

Manager Account / MCC Relationship

When a Google Ads Manager Account (MCC) is used, it is used only as the authorized login customer context for merchant-approved conversion reporting workflows. The MCC relationship helps route API requests to the correct authorized Google Ads customer account and conversion action.

• The merchant or authorized operator provides the Google Ads Customer ID, optional MCC Login Customer ID, Conversion Action ID, timezone, and conversion settings.
• SafeS Pay does not use MCC access to create, edit, or control campaigns, budgets, keywords, ads, audiences, assets, or account structure.
• FutureWave Commerce LLC maintains the SafeS Pay product, website, support mailbox, and compliance communications for Google Ads API and manager-account review.

Security and Access Controls

• OAuth refresh tokens and developer tokens are stored as encrypted secrets where configured in the system.
• Administrative interfaces mask sensitive credentials and do not reveal full secrets after saving.
• Sub-account permissions restrict which merchants, sites, orders, and conversion settings a user can access.
• Webhook verification, idempotency checks, retry records, and audit logs reduce the risk of duplicate or unauthorized processing.

Compliance Contact

For Google Ads API review, privacy, data deletion, or product compliance questions, please contact FutureWave Commerce LLC through the domain-aligned business mailbox below.