All integrations — overview and use cases
All Wevion integrations: ad platforms, commerce, trackers, files, notifications. Categories, use cases, prerequisites. No user-facing CRM integration.
Written By Salvatore Sinigaglia
Last updated About 5 hours ago
All Wevion integrations: ad platforms, commerce, trackers, files, notifications. Categories, use cases, prerequisites. No user-facing CRM integration.
All integrations — overview and use cases
Meta-overview of Wevion's integration ecosystem. Categories: ad platforms, commerce, trackers, files, notifications. For security & access (API keys + audit log) see team-112 + team-113 — those are documented in the team-workspace cluster, not duplicated here.
Who is this for
Admins and mediabuyers wanting a single map of "what can Wevion connect to". Bookmark this article when onboarding a new workspace or planning integration strategy.
Integration categories
Ad platforms (PRD-13)
The core of Wevion — ad campaign management requires at least one connected ad platform.
Start here for ad-platform setup: gs-104 connect your first ad platform.
Commerce (this cluster)
For e-commerce attribution, product catalog sync, order tracking.
Use when: you run an e-commerce store and want Wevion to track orders + attribute to ad campaigns.
Trackers (this cluster)
For affiliate marketing, funnel tracking, off-site conversion tracking.
Use when: you run affiliate funnels, app installs via tracker, or need server-side conversion tracking that bypasses browser limitations.
Files (this cluster)
For asset management + brief docs.
Use when: you want Drive access to your Creative Hub files. Wevion owns a per-user Drive folder (via a Service Account) and grants your Gmail writer access to it — you work directly in the Wevion-owned folder.
Notifications (this cluster + cross-cluster)
For real-time alerts + delivery channels.
Use when: you want notifications outside the Wevion web app (especially Telegram for real-time mobile alerts).
CRM
There is no user-facing CRM integration in Wevion. HubSpot is not a self-serve integration you can connect with your own account — there is no HubSpot connect flow in the product (com-116 HubSpot in Wevion). To get ad-derived leads and conversions into your own systems, use Postback / server-to-server conversions, commerce (Shopify, WooCommerce), or trackers (see the sections above).
Security & access (cross-cluster — DO NOT duplicate here)
For programmatic access + auditing. Covered in the team-workspace cluster:
- API keys (M2M tokens): see team-112 Generate and rotate API keys — full lifecycle, scopes, rotation, security
- Audit log: see team-113 Read your audit log — schema, filters, retention, compliance use cases
These topics are intentionally NOT duplicated in the commerce cluster (anti-pattern: same content in two places drifts).
Use case → integration matrix
Pick by what you want to achieve:
Integration prerequisites checklist
Before connecting any integration:
- Wevion role: manager+ for most; admin+ for API keys
- You have admin access on the source platform (BM, Google, Shopify, etc.)
- Browser pop-ups allowed for
app.wevion.ai - Workspace defaults set (team-106) — esp. timezone + currency
- Plan quota available for the integration (see acc-112)
Connection quality tiers
Not all integrations are equal in terms of data richness:
Integration costs
Most integrations are free (included in your Wevion plan):
- Ad platforms: free (you pay ad platforms separately for ad spend)
- Shopify / WooCommerce: free
- Keitaro / other trackers: free (you pay tracker vendors separately)
- Postback: free
- Google Drive: free
- Telegram: free
Quotas apply to:
- Ad accounts: counted toward
max_ad_accounts(see acc-112) - Some integration-specific limits per plan (rare)
Cross-integration scenarios
Scenario A: E-commerce performance buyer
Connect: Meta + Google Ads + Shopify + Telegram + Meta CAPI
Flow: launch ads → user clicks → lands on Shopify → buys → Wevion attributes via Shopify order + Meta CAPI → reports + optimizes → real-time Telegram on rule firings.
Scenario B: Affiliate marketer
Connect: Meta + Keitaro (Tracker Hub) + Postback + Telegram
Flow: launch ads → user clicks → tracker routes to offer → conversion logged in tracker → tracker postback to Wevion's Meta postback store → conversion shown as the postback source in reporting → optimization. (Wevion stores the conversion; it does not forward it to Meta CAPI.)
Scenario C: B2B SaaS
Connect: Google Ads + Meta + LinkedIn (roadmap) + landing page → Postback / server-to-server conversions + Email digest
Flow: ads → lead captures on your landing page → conversions sent to Wevion via Postback (server-to-server) → attribution + reporting in Wevion → optimize by source. (Wevion has no user-facing CRM integration; route leads into your own CRM from your landing page or lead tool.)
Scenario D: Agency
Connect: per-client workspaces, each with relevant ad platforms + commerce as needed + Telegram per account manager
Strategy: separate Wevion workspace per client (clean data isolation, separate billing), each with own integrations + per-client Drive folder for creative.
Common questions
- "How many integrations can I connect?": most no hard cap. Ad accounts count toward quota.
- "Can I disconnect an integration without losing data?": yes, data preserved; only sync stops.
- "Are integrations bi-directional?": most are one-way (source → Wevion). Drive is two-way if you give Editor permission.
- "Webhook URL changed — what do I do?": most integrations regenerate webhook secrets on re-install. Otherwise contact support.
- "How do I sunset / migrate from one integration to another?": connect new + verify data flowing + then disconnect old. Order matters — don't disconnect old until new is healthy.
FAQ
What can Wevion integrate with?
Wevion connects across five integration categories: ad platforms (Meta, Google Ads, TikTok, Taboola, Outbrain, and env-gated Snapchat), commerce (Shopify, WooCommerce), trackers (Keitaro, Voluum, RedTrack, BeMob, TG Tracker, Binom, plus the Meta-only Postback store), files (Google Drive), and notifications (in-app, email, Telegram). There is no user-facing CRM integration. At least one connected ad platform is required for campaign management.
Do Wevion integrations cost extra?
Most Wevion integrations are free and included in your plan — ad platforms, Shopify, WooCommerce, trackers, Postback, Google Drive, and Telegram. You still pay ad platforms and third-party vendors separately. Quotas apply mainly to ad accounts, which count toward your plan's max_ad_accounts limit.
Can I disconnect an integration without losing data?
Yes. In Wevion, disconnecting an integration preserves your existing data; only the ongoing sync stops. When migrating from one integration to another, connect the new one and confirm data is flowing before disconnecting the old — order matters, so don't remove the old integration until the new one is healthy.
Are Wevion integrations one-way or bi-directional?
Most Wevion integrations are one-way, pulling data from the source into Wevion. Google Drive uses a Wevion-owned per-user folder shared to your Gmail — you edit files directly in that folder. Real-time depth varies: Meta, Shopify, and Telegram are real-time, while trackers and WooCommerce poll roughly every 15 minutes.
What do I need before connecting an integration?
Before connecting any integration in Wevion, check that you have the right role (manager+ for most, admin+ for API keys), admin access on the source platform, pop-ups allowed for app.wevion.ai, workspace defaults like timezone and currency set, and available plan quota for the integration.