Run multiple referral configs
This article's section starts at 0:00 in the video.
One referral program rarely fits everyone: you might want VIPs to earn 20% while everyone else earns 10%. DollarBack supports multiple referral configs, targeted by customer tags and resolved by a drag-and-drop priority order. This page shows how to add a second config and predict which one wins.
Prerequisites
A first referral config live. See Set up your referral program.
The customer tag you'll target (e.g.
vip) already applied to the right customers in Shopify admin.
Step 1. Add the second config
Go to DollarBack admin → Referral and click Add Config.
Set an Internal Title ("VIP referrers") and a distinct Code Prefix (e.g.
VIP). Prefixes can't be changed after saving, and a distinct prefix makes it obvious at a glance which program a code belongs to.In Customer Tags, select the tag(s) this config targets, e.g.
vip.Set its own referrer reward, referee discount, and usage limits; each config carries a full set.
Save. Code generation runs for the newly matched customers; the editor locks while it does (Referral codes & bulk sync).
Step 2. Set the priority order
Configs are evaluated top-to-bottom. As the banner on the page puts it: "Drag and drop configs to set priority. If a customer matches multiple configs (overlapping tags), the config at the top takes precedence."
Drag your VIP config above the general one. Rule of thumb: most specific on top, catch-all (no tags) at the bottom.
Which config wins
For any given referrer, DollarBack picks the first config from the top whose Customer Tags match that referrer's tags. A config with no tags matches everyone, which is why an untagged catch-all placed first would swallow every customer, including your VIPs.
Priority
Config
Tags
A vip customer gets
An untagged customer gets
1
VIP referrers
vip
✓ this one
(none)
2
Everyone
(none)
(none)
✓ this one
The winning config decides everything for that referral: the code the customer holds, the referrer reward, the referee discount and its conditions, and the reward expiry.
Selection follows the referrer's tags, not the referee's. Conditions like new-customers-only still apply to the referee, but which program is in play is decided by who owns the code.
The Combination Rules section is the exception: those toggles are shared across all configs.
Verify it works
Sign in as a tagged (vip) customer. Their widget and account should show a code with the VIP prefix and the VIP reward messaging. An untagged customer should still see the general code. Place a test referee order against each code and confirm in Analytics → Referral that each row is attributed to the expected config.
Common issues
A VIP customer still shows the general code → the VIP config sits below the catch-all; drag it to the top, or the customer isn't actually tagged.
A customer matches no config → they hold no code and can't refer; make sure a no-tags catch-all config exists if everyone should participate.
Reward amounts look inconsistent across referrers → they're on different configs; check the attribution rows in Referral analytics.
Related articles
Last updated