Skip to content
Sign in Start free trial

Docs

Google OAuth setup

Connect Google Analytics and Search Console only for websites you own or are authorized to manage. Google data is used for reporting impact, not outreach sending.

Before connecting

  • Confirm the website exists in AssetLed and belongs to the account.
  • Use a Google user with access to the relevant Analytics property and Search Console site.
  • Confirm the production callback URL is configured for the hosted domain: https://assetledlinkbuilding.com/integrations/google/callback.

Scopes and consent screen

The current implementation requests Google Analytics/Search Console scopes for read-only reporting: https://www.googleapis.com/auth/analytics.readonly and https://www.googleapis.com/auth/webmasters.readonly.

The Google consent screen should clearly identify AssetLed Linkbuilding, the authorized website, and that the connection is for Analytics and Search Console impact snapshots.

Connect and disconnect expectations

  1. Start from Google data.Open Google data, choose the website, and start the OAuth flow.
  2. Return through callback.The app uses /integrations/google/callback to complete the connection after Google authorization.
  3. Sync impact data.Run Sync after connection so reports can include Google Analytics and Search Console impact.
  4. Disconnect by revocation request.If a connection must stop processing, use data deletion or privacy request until a dedicated disconnect control is added to the product.

Data minimization, privacy, and security

AssetLed stores OAuth state and refresh-token material using ASP.NET Core Data Protection and uses Google data only for impact snapshots tied to authorized websites.

See Privacy Policy, Security Contact, Security Practices, data deletion, and privacy request for controls and request routes.