Commerce & tracker integrations — complete guide

Last updated: May 19, 2026

Commerce & tracker integrations — complete guide

TL;DR: Beyond ad platforms, Wevion integrates with e-commerce (Shopify, WooCommerce), 5 trackers (Keitaro, Voluum, RedTrack, BeMob, TG Tracker) for postback attribution, Google Drive (Creative Hub storage), Telegram (notifications + tracker callbacks), and HubSpot (CRM). These power true cross-platform attribution + automate workflows.

Table of contents

E-commerce platforms (Shopify, WooCommerce)

Pull orders / products / inventory for cross-reference with ad spend (CDM = Commerce Data Model overlay).

Platform

Auth

Verified scope

Shopify

OAuth

read_orders + read_products + read_inventory

WooCommerce

Basic Auth

consumerKey:consumerSecret REST API

Use case: overlay commerce data on ad campaigns (am-121 postback vs Meta conversions) for true attribution beyond what ad platforms report natively.

Trackers (5 supported)

Trackers consume postback events from ad clicks → log conversions → emit to Wevion. Provides single-source-of-truth attribution.

Tracker

Notes

Keitaro

Most popular; full integration

Voluum

Cloud-based

RedTrack

Affiliate-friendly

BeMob

Free-tier available

TG Tracker

Telegram-based tracking

Postback configuration

Postback URLs configured at the tracker side, calling Wevion endpoints:

  • POST /api/v1/postback/config — config postback target

  • POST /api/v1/postback/conversions — conversion event ingestion

  • GET /api/v1/postback/conversions/currencies — currency support

  • com-109 postback S2S overview — full flow

Result: tracker_* fields enrich your analytics (tracker_clicks / conversions / revenue / cost / profit / roi / cr / cpa / roas).

Google Drive integration

Wevion's Creative Hub stores files via Google Drive Service Account (NOT user OAuth). Workspace-level config:

Telegram bot

Same bot handles 2 separate workflows:

  1. Notifications (PRD-21): real-time alerts + daily/weekly digest

  2. Tracker callbacks: postback events via bot

Bot commands verified: /start /status /stats /help /unlink.

HubSpot CRM

OAuth-based. Bidirectional sync of contacts + events.

Properties prefix verified: wevion_* (post-rebrand from adrow_*).

Use case: enrich ad audience with CRM segments + push conversion events back to HubSpot for marketing automation.

Troubleshoot

FAQ

Can I use multiple trackers simultaneously?

Yes. Each ad account can have its own tracker config. Wevion ingests postbacks from any configured tracker.

Does Drive Service Account count against my Google quota?

It uses the Wevion-deployed Service Account's quota (separate from individual users' Drive quotas). Quota per Google Workspace tier of the Service Account.

Telegram bot is for notifications OR tracking?

Both — same bot infrastructure handles both workflows. Linking for notifications doesn't enable tracker callbacks (separate config).

HubSpot properties prefix?

wevion_* (current). Older deployments may have adrow_* (legacy pre-rebrand). Verify in HubSpot UI.

What's CDM (Commerce Data Model)?

Wevion-internal model that overlays commerce data (Shopify / WooCommerce orders) on ad campaigns for true attribution. See cdm_* tools in Wavo (ai-105).

Can I migrate trackers (Keitaro → Voluum)?

Setup new tracker integration first → verify postbacks flow → disable old. Historical postbacks remain in Wevion.

Next steps

Related