Workflow-driven affiliate triggers on Vero's behavioral engine.
Vero treats every send as a node in a workflow rather than a campaign in a list. Rekomi sends `affiliate_approved` as a workflow trigger; your existing Vero workflow tree extends naturally without forking the messaging logic.
From paste-API-key to first paid affiliate in 10 minutes.
Paste your Vero API key into Rekomi. Rekomi runs a test call to verify the key, then pulls your list/audience picker live from Vero so you pick the right destination.
Affiliates apply via your public landing page or your bulk invite. Approve them manually, auto-approve on a campaign, or import an existing affiliate CSV from Rewardful.
Approved affiliates land in your Vero list as tagged subscribers within seconds. Rekomi handles idempotency, retries, and per-campaign overrides; you handle the nurture sequence.
The exact Vero fields Rekomi writes.
No surprise fields, no overwrites of contact data you already have. Empty values are omitted so existing nurture data is preserved.
POST /api/v2/users/trackwithid(probe),email, custom dataPUT /api/v2/users/editto update user attributesfirst_name,last_name,rekomi_status,rekomi_tags- Identify-event semantics: Vero's user-track is a behavioral event, not a contact-add
- Sync semantics: 200 on success; idempotent by user ID
What Vero customers actually do with Rekomi.
Behavioral workflow on affiliate-approved event
Build a Vero workflow on the `affiliate_approved` custom event: send email 1, wait for user.tracking_link_clicked event, branch on whether they got conversions in 7 days. Behavioral routing instead of time-based drip.
Affiliate-tier escalation triggers
Vero workflows on `user.rekomi_tier_changed` event fire whenever Rekomi promotes an affiliate to a new tier. Send a personalized 'You're now a top affiliate' message instantly. Same behavioral posture as your product activation flows.
SaaS PLG affiliate qualification
Vero tracks user events from your app. Build a Vero segment of users who hit a threshold (e.g., 30-day active + 5 referrals in your existing product). Use Rekomi's bulk-invite to convert them to formal affiliates with commissions.
Rekomi handles Vero's edge cases so you don't have to.
Every CRM API has quirks. Rekomi's integration code was built and audited against the live Verodocs, these are the ones you'd otherwise hit yourself.
Vero's `users/edit` probe needs a unique ID to avoid colliding with a real user named the probe value. Rekomi appends a UUID suffix to test IDs so the probe never accidentally patches a real user.
Vero uses `Auth-Token` as a custom header (not standard Authorization). Rekomi handles the header convention.
Vero distinguishes track (event) from identify (user attribute update). Rekomi uses identify-style PUT to update attributes, plus tracks `affiliate_approved` as an event so workflows can trigger on it.
Built for SaaS PLG teams running Vero alongside product event-tracking. If your product team thinks in workflows + behavioral events, Rekomi pushes affiliate events into the same engine instead of forcing a parallel messaging system.
Common Vero questions.
Does Vero have an affiliate program?
Vero runs a referral program (varies by tier) for promoting Vero. That's separate from running YOUR affiliate program. Rekomi is the layer for the latter, with Vero as the behavioral messaging engine.
Will Vero's workflows fire on Rekomi events?
Yes, Rekomi's outbound webhooks can post to Vero's Track API as custom events. Your Vero workflows then trigger on `affiliate_approved`, `commission_earned`, `payout_sent`, same authoring as your product workflows.
What's the minimum Vero plan?
Vero Cloud Pro is the typical paid tier. All paid tiers expose the API. Free trial includes API access for evaluation.
Other CRMs that pair well.
Same persona, different stack. Pick the home your existing audience already lives in.
See all 38 integrations
Ten minutes to first click.
14-day free trial. Stripe-native. No card. Live this afternoon.
- 14-day free trial
- Cancel anytime, $0 charged