Tracker Hub supports 6 trackers including Keitaro. Connect via API key + Api-Key header. Sync campaigns, conversions, mappings.

Connect Keitaro via Tracker Hub

Tracker Hub supports 6 affiliate trackers: Keitaro, Voluum, RedTrack, BeMob, TG Tracker, and Binom (binom_v2). Connect Keitaro at /trackers by providing your tracker URL + API key. Wevion uses the Api-Key header for authentication (verified in apps/backend/src/tracker-hub/types/tracker.types.ts AUTH_CONFIGS.keitaro).

Who is this for

Affiliate marketers using Keitaro to route traffic + log conversions. Use Wevion's Tracker Hub to bring Keitaro data into unified analytics with your ad campaigns.

The 6 supported trackers

Verified vs apps/backend/src/tracker-hub/types/tracker.types.ts TrackerType + AUTH_CONFIGS:

This article covers Keitaro setup specifically. Others follow similar patterns — switch tracker type in the setup flow.

Before you start

• A Keitaro account running (self-hosted Keitaro instance or hosted)
• The Keitaro URL (e.g. https://your-keitaro.com)
• An API key generated in Keitaro's admin
• Wevion role: manager, admin, owner, super_admin

How to connect

Step 1: Get your API key from Keitaro

In Keitaro admin:

• Settings → API (or Tools → API depending on Keitaro version)
• Generate new API key (or copy existing)
• Note the key — Wevion will store it encrypted

Step 2: Open Tracker Hub in Wevion

In sidebar click Connect → Trackers or visit /trackers. The page lists already-connected trackers + has a Connect tracker button.

Step 3: Select Keitaro

Click Connect tracker → pick Keitaro from the type dropdown. Form expands with:

• Name (your label, e.g. "Production Keitaro" or "Client A Keitaro")
• Tracker URL (your Keitaro base URL, no trailing slash)
• API key (paste)

Step 4: Test connection

Click Test connection. Wevion calls POST /api/v1/trackers/test which makes a test API call to your Keitaro using the provided key. If success: connection valid. If error: shows what failed (auth, URL, network).

Step 5: Save configuration

Click Save. Backend creates tracker_config row. API key encrypted via apps/backend/src/lib/tracker-crypto.ts (AES-256-GCM with the TRACKER_ENCRYPTION_KEY env var). Listed at /trackers.

Step 6: Initial sync

Within 15 minutes, Wevion's first sync pulls: campaigns, offers, landing pages, flows, traffic sources, click logs, conversions (last 30 days backfill).

Status badge: Syncing → Synced when done.

Endpoint reference

Verified vs route files:

What gets imported

After successful sync:

• Campaigns: Keitaro campaigns with traffic routing logic
• Offers: ad offers / products
• Landing pages: landing page configurations
• Flows: traffic flow rules
• Traffic sources: ad platforms / networks
• Click logs: clicks with attribution data (15-min cadence; full backfill on first sync)
• Conversions: conversions with revenue + status (approved / pending / rejected / hold — Keitaro states mapped to Wevion canonical ConversionStatus)
• Sub-IDs: tracking parameters (sub_1 through sub_N — most affiliates use sub_1 for click_id)

Use in:

• Wevion analytics: see which ad campaigns drive Keitaro conversions
• Per-funnel attribution: track full path from ad → click → tracker offer → conversion

Multiple Keitaro instances

Each Keitaro instance = separate tracker_config. Common for:

• Multi-account agencies (one Keitaro per client)
• Multi-environment setups (staging Keitaro vs production)

Repeat steps 2-6 per instance.

Tracker types beyond Keitaro

Same setup flow, different auth field:

• Voluum: needs Voluum URL + email/password (session token auth; 4h TTL auto-refreshed by Wevion via tokenEndpoint: /auth/access/session)
• RedTrack / Binom: API key with the Api-Key header (same pattern as Keitaro)
• BeMob: two keys — access key as X-ACCESS-KEY plus a secret injected as X-SECRET-KEY
• TG Tracker: API key with Bearer prefix

Security

• API key encrypted at rest via AES-GCM
• Wevion's request to Keitaro uses HTTPS
• Audit log records every Keitaro API call (admin view)
• Revoke at Keitaro admin → Settings → API → delete key

Common issues

• "Connection test failed: 401": API key wrong. Regenerate in Keitaro admin.
• "Connection test failed: ECONNREFUSED": Keitaro URL wrong or server down.
• "Connection test failed: timeout": network latency or Keitaro slow. Check Keitaro server load.
• Sync stuck > 30 min: large Keitaro instance (millions of clicks). First sync may take longer; subsequent syncs incremental.
• Wevion shows 0 conversions despite Keitaro logs: mappings not set up. Configure at /trackers/:configId/mappings.

FAQ

Which trackers does Wevion's Tracker Hub support?

Tracker Hub supports six affiliate trackers: Keitaro, Voluum, RedTrack, BeMob, TG Tracker, and Binom (binom_v2). This article covers Keitaro specifically, but the others follow a similar setup at /trackers — you switch the tracker type in the setup flow. Most use an API key, while Voluum uses a session token, TG Tracker uses a Bearer key, and BeMob uses two keys (X-ACCESS-KEY + X-SECRET-KEY).

How does Wevion authenticate with my Keitaro instance?

Wevion authenticates to Keitaro using the Api-Key header with the API key you generate in Keitaro's admin under Settings → API. You paste your Keitaro URL and that key into the Connect tracker form at /trackers, then click Test connection so Wevion makes a test call before saving. RedTrack and BeMob use the same Api-Key pattern.

Are my Keitaro API keys stored securely in Wevion?

Yes. Your Keitaro API key is encrypted at rest with AES-GCM before it's saved to the tracker_config row, and Wevion's requests to Keitaro use HTTPS. An audit log records every Keitaro API call for admins. You can revoke access at any time from Keitaro admin → Settings → API by deleting the key.

How far back does the first Keitaro sync pull data?

Your first Keitaro sync runs a 30-day backfill, pulling campaigns, offers, landing pages, flows, traffic sources, click logs, and conversions. It begins within 15 minutes of saving the connection, and the status badge moves from Syncing to Synced when done. Subsequent syncs are incremental on a 15-minute cadence.

Can I connect more than one Keitaro instance to Wevion?

Yes. Each Keitaro instance becomes a separate tracker_config, which is common for multi-account agencies running one Keitaro per client, or for staging-versus-production setups. Just repeat the Connect tracker flow at /trackers for each instance, giving each a distinct name like "Production Keitaro" or "Client A Keitaro."

FAQ

Which trackers does Wevion's Tracker Hub support?

Tracker Hub supports six affiliate trackers: Keitaro, Voluum, RedTrack, BeMob, TG Tracker, and Binom (binom_v2). This article covers Keitaro specifically, but the others follow a similar setup at /trackers — you switch the tracker type in the setup flow. Most use an API key, while Voluum uses a session token, TG Tracker uses a Bearer key, and BeMob uses two keys (X-ACCESS-KEY + X-SECRET-KEY).

How does Wevion authenticate with my Keitaro instance?

Wevion authenticates to Keitaro using the Api-Key header with the API key you generate in Keitaro's admin under Settings → API. You paste your Keitaro URL and that key into the Connect tracker form at /trackers, then click Test connection so Wevion makes a test call before saving. RedTrack and BeMob use the same Api-Key pattern.

Are my Keitaro API keys stored securely in Wevion?

Yes. Your Keitaro API key is encrypted at rest with AES-GCM before it's saved to the tracker_config row, and Wevion's requests to Keitaro use HTTPS. An audit log records every Keitaro API call for admins. You can revoke access at any time from Keitaro admin → Settings → API by deleting the key.

How far back does the first Keitaro sync pull data?

Your first Keitaro sync runs a 30-day backfill, pulling campaigns, offers, landing pages, flows, traffic sources, click logs, and conversions. It begins within 15 minutes of saving the connection, and the status badge moves from Syncing to Synced when done. Subsequent syncs are incremental on a 15-minute cadence.

Can I connect more than one Keitaro instance to Wevion?

Yes. Each Keitaro instance becomes a separate tracker_config, which is common for multi-account agencies running one Keitaro per client, or for staging-versus-production setups. Just repeat the Connect tracker flow at /trackers for each instance, giving each a distinct name like "Production Keitaro" or "Client A Keitaro."

Last updated: 2026-05-17

Related articles

• Keitaro sync flow — what data, how often
• Postback (S2S) tracking overview
• All integrations — overview and use cases