Documentation
Import from Binom or Keitaro
Updated 17 Nov 2026
Velotrak imports its own export and JSON from Binom or Keitaro. There is no Voluum importer in the product. The Binom and Keitaro adapters bring paths, offers, and external landers. They do not import flow rules. Free stops at 20 campaigns in one import.
Export what you have
GET /api/export (MCP export_config) writes traffic sources, networks, offers, lander metadata, flows (paths, weights, rotation, rules), and campaigns. Network keys are replaced with a NETWORK_KEY placeholder. CAPI and other integration credentials are not included. Hosted lander files are not included. Copy those files yourself; the landers page is the upload.
Import
POST /api/import and MCP import_config accept format velotrak, binom, or keitaro.
The Binom adapter builds one flow per campaign from that campaign’s paths. Landers come in as external URLs. Flow rules are not parsed. The Keitaro adapter turns streams into paths and landers into external URLs. It does not import rules either. There is no Voluum adapter in the importer. Voluum appears as a traffic-source template name, not as a file you can upload.
Free’s max_import_campaigns is 20. The pricing FAQ says campaigns past the three active ones land paused, so the import can keep them without turning them on. Pro, Team, and Founder store 0 for that cap, which means the import is not capped by this field. Re-importing does not reuse the old network key; the export placeholder is filled again. Update the postback URL at the network after each import.
Templates and demo data
GET /api/templates lists built-in source and network templates. POST /api/templates/apply applies one. generate_demo and clear_demo fill or remove demo data. Both are admin actions, and clear_demo is explicit-only on MCP: a wildcard scope does not grant it, and it asks for diff confirmation.
Compare that with a from-scratch setup on the concepts page. The pricing page states the import cap in the Free plan line.