Connected integrations

Clear access. Visible purpose. User-controlled connections.

Adscriptly uses OAuth so users authorize each provider directly. Provider credentials and connection identifiers remain server-side, and every connection can be revoked in Adscriptly or with the provider.

01

Google Analytics 4

analytics.readonly

Read aggregate acquisition and conversion reporting for a property the authenticated user selects.

Adscriptly does not edit Google Analytics configuration.

02

Google Tag Manager

tagmanager.edit.containers, tagmanager.edit.containerversions, tagmanager.publish

Create or update tags in a selected container and publish a reviewed workspace only after explicit confirmation.

Automatic publishing is disabled. Publishing requires a separate container-specific confirmation.

03

Google Search Console

webmasters.readonly

Read aggregate search-query performance for a verified property the authenticated user selects.

Adscriptly does not modify site ownership or Search Console settings.

04

Meta Ads

ads_read

Read accessible ad accounts and aggregate account performance for an authenticated business user.

The current reviewer workflow is read-only and does not request campaign-management permission.

05

Slack

commands, chat:write

Answer explicit /adscriptly requests and send advertising or analytics notifications configured by an authorized user.

Commands receive only text a user submits directly; neither feature requests broad Slack message-history access.

Control and removal

Disconnect without contacting sales.

Disconnecting in Settings stops future Adscriptly API access. Users can also revoke access directly in Google, Meta, or Slack.

Revocation and deletion are different. Follow the public deletion instructions to remove retained copies after revoking a provider.