All integrations — overview and use cases
Last updated: May 19, 2026
All integrations — overview and use cases
Meta-overview of Wevion's integration ecosystem. Categories: ad platforms, commerce, trackers, files, notifications, CRM. 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.
Platform | Status | Article cluster |
|---|---|---|
Meta (Facebook + Instagram) | ✅ Production | |
Google Ads | ✅ Production | |
TikTok Ads | ✅ Production | |
Taboola | ✅ Production | Same as TikTok |
Snapchat | ✅ Production (env-gated) | Same as TikTok |
LinkedIn / Pinterest / Reddit / X | Roadmap | Not yet implemented |
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.
Platform | Article |
|---|---|
Shopify | |
WooCommerce |
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.
Tracker | Article |
|---|---|
Keitaro | |
Voluum | Same as Keitaro (use Tracker Hub flow, pick Voluum) |
RedTrack | Same |
BeMob | Same |
TG Tracker | Same |
Postback (S2S) |
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.
Platform | Article |
|---|---|
Google Drive |
Use when: you maintain a creative asset library in Drive and want auto-sync to Creative Hub.
Notifications (this cluster + cross-cluster)
For real-time alerts + delivery channels.
Channel | Where covered |
|---|---|
In-app bell | team-115 Notification center (team-workspace) |
Email digest | gs-115 Set up notifications (getting-started) |
Telegram bot |
Use when: you want notifications outside the Wevion web app (especially Telegram for real-time mobile alerts).
CRM (this cluster)
For lead enrichment + contact timeline.
Platform | Article |
|---|---|
HubSpot |
Use when: you use HubSpot as primary CRM and want Wevion lead captures + ad attribution to enrich HubSpot contacts.
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:
Goal | Required integrations |
|---|---|
Launch ads on Meta | Meta connection |
Multi-platform ad management | Meta + Google Ads + TikTok (or whichever combo) |
E-commerce conversion tracking | Ad platform(s) + Shopify or WooCommerce + Meta CAPI |
Affiliate funnel tracking | Ad platform(s) + Keitaro (or another tracker) + Postback |
Real-time mobile alerts | Telegram bot |
CRM lead enrichment | Lead capture (pixel/postback) + HubSpot |
Centralized creative library | Google Drive (folder-sync to Creative Hub) |
Daily performance email | Email digest (built-in, configure preferences) |
Programmatic API access | API keys (team-112) |
Compliance audit trail | Audit log (team-113) |
Integration prerequisites checklist
Before connecting any integration:
Wevion role: manager+ for most; admin+ for HubSpot, API keys
You have admin access on the source platform (BM, Google, Shopify, etc.)
Browser pop-ups allowed for
app.wevion.aiWorkspace 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 | Real-time? | Data depth | Setup complexity |
|---|---|---|---|
Meta | Yes (webhooks + 15-min) | Deep (full Marketing API) | Low |
Google Ads | 15-min polling | Deep | Low-Medium |
TikTok | 15-min polling | Medium | Medium |
Taboola | 15-min polling | Medium | Medium (server-side creds) |
Snapchat | 15-min polling | Medium | Medium (env-gated) |
Shopify | Yes (webhooks) | Deep (orders, products, refunds) | Low |
WooCommerce | 15-min polling + optional webhooks | Deep | Medium |
Keitaro | 15-min polling | Deep (clicks, conversions, breakdowns) | Medium |
Postback | Real-time (event-driven) | Single events | Medium (per-tracker config) |
Google Drive | 5-min polling | File metadata + content | Low |
Telegram | Real-time | Notifications + commands | Low |
HubSpot | Real-time (outbox + queue) | Deep (contacts, properties, timeline, deals) | Medium-High |
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
HubSpot: free integration; HubSpot subscription paid to HubSpot
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 → Wevion forwards to Meta CAPI → attribution + optimization.
Scenario C: B2B SaaS
Connect: Google Ads + Meta + LinkedIn (roadmap) + Shopify (if products) OR landing page → HubSpot + Email digest
Flow: ads → lead captures → Wevion → HubSpot Contacts with attribution → sales follow-up in HubSpot → deal stage updates flow back to Wevion for closed-loop ROAS.
Scenario D: Agency
Connect: per-client workspaces, each with relevant ad platforms + commerce / CRM 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). HubSpot has limited bidirectional (deal stage). 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.
Related
API keys (M2M tokens) — programmatic integration access
Audit log — track integration changes
Data and sync troubleshooting — when integrations misbehave