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. Changes happen only with your explicit approval.
On this page
Google Ads
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
- WCreate new Search and Performance Max campaigns (always created paused)
- WAdd search themes and audience signals in Performance Max
- WAdjust targets and pause ads in Demand Gen
- WExclude placements
- WUndo an applied change within seven days
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 only to produce proposals in 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.
Data from your Google Ads account is used only to produce proposals in 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
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 and content gap analysis. Data is synced daily and used to identify keywords where improvements are most likely to move the needle.
Google Analytics 4
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 shown in your overview alongside Google Ads, Search Console and social media.
Facebook & Instagram
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
- Rinstagram_basic: read IG account info
- Winstagram_content_publish: publish to Instagram
- Rread_insights: read Page statistics
- Winstagram_manage_comments: reply to Instagram comments
- 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 or reply in Verka.
- WPublish a post to your Facebook Page
- WPublish media to your Instagram Business account
- WReply to a comment, after you approve the reply
Not available yet
- ×Meta ads open once Meta approves our access.
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.
LinkedIn
OAuth scopes
- Rrw_organization_admin: find the Pages you administer and read Page statistics
- Rr_organization_social: read the Page's posts
- Ww_organization_social: publish to the Page, as the company
- Rr_organization_social_feed: read comments on the Page's posts
- Ww_organization_social_feed: reply to comments
What we read
- RPosts on the Company Page
- RStatistics per post
- RComments on the Page's posts
- RFollower count
What we can write
Only after you approve a specific post or reply in Verka.
- WPublish a post to the Company Page
- WReply to a comment
Not available yet
- ×Publishing opens once LinkedIn approves our app. Until then, Verka writes your posts as drafts.
- ×LinkedIn ads
Verka always posts as the Company Page, never from a personal profile. 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)
Questions
Not finding the answer you need?
For questions about data handling, retention or integration scope, email [email protected].
Read the privacy policy →Get started with Verka.
Leave your email and we'll be in touch to set up your account with you.