Advocate redeems → UserEvidence → your ReachDesk campaign → gift sent
We trigger campaigns you already built. Budgets, gift options, approval rules, and branding stay exactly as you set them.
Your part takes about 15 minutes, spread over a few days. We build and test the connection.
Step 1 — Send your CSM five things
Share these with your CSM however you normally reach them — Slack, email, your next call. You'll need someone with admin access to ReachDesk to pull them.
API key: generated in ReachDesk by an admin. Treat it like a password and send it however you prefer to send credentials.
Campaign ID for each gift: the number in the campaign's URL
Sender email: gifts are sent "from" a person. Must be an active ReachDesk user, copied exactly as ReachDesk spells it.
Wallet that pays: personal or team — see note below
Test recipient email: for one trial send before any advocate gets a gift
On the sender email: if your company uses more than one email domain, the address on that person's ReachDesk profile may not be the one they use day to day. Check ReachDesk, don't guess. A mismatch fails every send.
On the wallet: ReachDesk charges the sender's personal wallet by default, and it's usually empty even when the campaign is funded. If your budget sits in a team wallet, say so.
While you're in ReachDesk, set a spend cap on the campaign. It's your safety net and it lives on your side, not ours.
Step 2 — Map each reward in UserEvidence
You do this yourself, no ticket needed:
Open the reward in your UserEvidence admin
Paste the ReachDesk campaign ID into the Unique Identifier field
Save
That's the whole mapping. Leave the field empty on any reward you don't want gifted — swag codes, donations, internal perks. The integration ignores them.
Also turn on "Require approval on redemptions" for the first few weeks. The gift only triggers once someone on your team approves it. Rejecting refunds the advocate's points and sends nothing.
Step 3 — Confirm the test gift
We'll tell you when we've sent a test gift to the address you gave us. Then it's on you to check ReachDesk:
Find the request in your sends list
Confirm the recipient actually got the gift email
We can prove the request was accepted. Only your ReachDesk account can confirm the gift is queued the way you expect. Have whoever holds ReachDesk admin do this check.
Step 4 — Turn the reward on
Once you've confirmed the test, switch the real reward on for your advocates. Done.
Adding another gift later
Tell your CSM before the reward goes live, not after. Send them the new campaign ID and set the Unique Identifier on the reward. We add it to the connection, usually same day.
If you launch first, the advocate redeems, their points are spent, and no gift is sent. Two minutes of warning avoids it.
If a gift doesn't send
What you see | What to do |
| You fix this in ReachDesk. The sender isn't an active user, or the address is spelled differently there. Add the user, or send your CSM the exact address from their ReachDesk profile. |
| You fix this in UserEvidence. The advocate's record needs a first and last name. |
| You fix this in ReachDesk. Fund the wallet, or ask your CSM to switch the connection to your team wallet. |
Nothing appears in ReachDesk at all | Message your CSM. We can see every attempt and its result, and we'll find it. |
Failed gifts aren't retried automatically. Once you've fixed the cause, tell your CSM and we'll trigger the gift again.
If your sender leaves the company or their ReachDesk account is deactivated, every gift starts failing. Send your CSM a replacement address.
Common questions
Do we need Workato or Zapier? No. The connection runs on our side. Nothing is installed in your ReachDesk account.
Can we see what was sent? Yes, in ReachDesk with every other send. Requests we trigger are tagged as coming from your advocacy program.
Can we turn it off? Instantly. Clear the Unique Identifier to stop one gift, or ask your CSM to switch the whole thing off.
What if a campaign ID changes in ReachDesk? Update the matching reward and tell your CSM. Nothing warns you if the two drift apart.
We use a different gifting platform. Sendoso, Tango, and Tremendous work the same way. Ask your CSM.