Integrations

What Verka connects to. What it can do.

Verka works by connecting to the tools and channels you already use. This page explains exactly what access is requested for each integration, what data is read, and what changes can be made — and only with your explicit approval.

On this page

Google Ads Search Console Google Analytics 4 Facebook & Instagram LinkedIn Backend services

Google Ads

Read & write OAuth 2.0 Supports manager accounts (MCC)

OAuth scope

A single scope is requested that covers read and write access to Google Ads accounts.

https://www.googleapis.com/auth/adwords

What we read

RCampaign names, status, budgets, bidding strategy
RAd group structure and ad assets (headlines, descriptions)
RKeyword performance — clicks, impressions, CTR, CPA, cost, conversions
RSearch term report — queries matched to your keywords
RQuality Score per keyword
RImpression share and competitive position
RConversion actions and conversion values
RNegative keyword lists
RAd scheduling and audience modifiers

What we never read

—Customer lists or remarketing audiences with personal data
—User access logs or account audit trails
—Billing details or payment methods
—Any data from sub-accounts that Verka was not explicitly authorized to access

What we can write

All write operations require your explicit approval in Verka. Nothing is applied automatically.

WPause or activate keywords
WAdd negative keywords at campaign or account level
WAdd new keywords from converting search terms
WChange keyword match type
WAdjust campaign budget
WShift budget between campaigns
WSet or adjust Target CPA
WSet or adjust Target ROAS
WModify ad scheduling (bid modifiers by time of day)
WAdd sitelink, callout, and structured snippet extensions
WAdd new responsive search ad (parallel to existing — no history lost)
WExclude geographic locations
WAdd audience targeting
WPause or activate campaigns

Verka uses the Google Ads API via direct REST calls. Each account connection requires a valid OAuth refresh token stored per workspace. Manager account (MCC) connections allow one connection to cover multiple client accounts — standard for agency use. The platform holds a Google Ads developer token required for API access.

Data from your Google Ads account is used exclusively to generate recommendations and reports within your Verka workspace. It is not sold to third parties, not used for advertising targeting, and not aggregated across customers. To perform AI analysis, campaign data is processed by Anthropic (Claude) as a sub-processor under a data processing agreement — Anthropic does not use this data to train its models. Verka's use of data received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Google Search Console

Read only OAuth 2.0

OAuth scope

https://www.googleapis.com/auth/webmasters.readonly

What we read

RList of verified sites on your Search Console account
RSearch queries — impressions, clicks, CTR, average position
RPage-level search performance (same metrics per URL)
RFilterable by date range, country, device, query, or page
RUp to 16 months of historical data

What we write

Nothing. Read-only scope. Verka cannot submit sitemaps, request indexing, or modify any Search Console settings.

Search Console data powers rank tracking, content gap analysis, and CRO page selection. Data is synced daily and used to identify keywords where improvements are most likely to move the needle.

Google Analytics 4

Read only OAuth 2.0

OAuth scope

https://www.googleapis.com/auth/analytics.readonly

What we read

RGA4 properties and accounts you have access to
RSession, user, and event data
RConversion events and goal completions
RTraffic source breakdowns
RLanding page performance

What we write

Nothing. Read-only scope.

GA4 data is used alongside Search Console data for conversion rate analysis and to validate whether recommended changes are moving the right metrics.

Facebook & Instagram

Read & write Meta OAuth 2.0 Instagram via Facebook page connection

Permissions requested

Rpages_show_list — list pages you manage
Rpages_read_engagement — read post engagement
Rpages_read_user_content — read posts on your pages
Wpages_manage_posts — publish to your pages
Wpages_manage_engagement — manage comments
Wpages_manage_metadata — read page settings
Rinstagram_basic — read IG account info
Winstagram_content_publish — publish to Instagram
Rinstagram_manage_insights — read post insights
Rbusiness_management — identify Business account

What we read

RPosts on your Facebook Page (caption, timestamp, media)
RPost engagement — reactions, comments, shares
RPost insights — impressions, reach
RPage follower count
RInstagram Business media and captions
RInstagram media insights — views, reach, likes, comments
RInstagram follower count

What we can write

Only after you approve a specific post in Verka.

WPublish a post to your Facebook Page
WPublish media to your Instagram Business account

Verka only accesses your own Pages and the Instagram Business account linked to that page. No access to individual user profiles, follower identities, or private messages. Tokens are exchanged for long-lived tokens (60-day TTL) and stored per workspace.

Read & write OAuth 2.0

OAuth scopes

Ropenid — standard identity
Rprofile — name and profile picture
Remail — account email address
Ww_member_social — create posts on your behalf

What we read

RYour member profile (name, email)
RPosts published from the connected member account
RPost statistics — impressions, unique impressions, likes, comments, shares, clicks
RFollower count

What we can write

Only after you approve a specific post in Verka.

WPublish a post to your LinkedIn member profile

What is not currently available

—Posting to LinkedIn Company Pages (requires Community Management API, separate LinkedIn approval)
—LinkedIn advertising data (requires Marketing Developer Platform access)

LinkedIn access tokens are valid for 60 days. Refresh tokens last 1 year. Tokens are stored per workspace and never shared between workspaces.

Backend services

These services run in the background. They do not require you to connect an account — they are configured at the platform level and used to power Verka's analysis and generation capabilities.

Anthropic Claude

The AI model that analyses your account data, drafts recommendations, generates content, and explains its reasoning. Models used: Claude Sonnet and Haiku depending on task complexity.

API key — platform-level

DataForSEO

Provides technical SEO audit data, keyword volume, SERP data, competitor domain analysis, rank tracking, and backlink data. Task-based API — requests are submitted and results polled asynchronously.

API key — platform-level

Resend

Sends the daily and weekly briefing emails to your team — summaries of completed actions and items waiting for your approval.

API key — platform-level

fal.ai

AI image generation for creative assets in Creative Studio. Used when you request generated visuals for social media posts or ads. No images are stored beyond what you explicitly save.

API key — platform-level

— Questions

Not finding the answer you need?

For questions about data handling, retention, or integration scope, reach out directly or read the privacy policy.

Read privacy policy →