Once you've synced Salesforce to Sendoso, we recommend running a quick end-to-end test before rolling the integration out to your team. A single low-value test send confirms that recipients are added to your Salesforce campaign, that campaign member statuses update as the gift progresses, and that activity is logged on the Contact or Lead record.
The core test takes about 10 minutes to set up. Status updates then continue to sync as the gift moves through its lifecycle (for example, Offer Sent → Engaged → Delivered).
Before you begin
Make sure the following are in place before you start testing:
- Salesforce is synced to Sendoso. If you haven't connected yet, see Setting Up: How to Sync Salesforce.
- The integration user has the required permissions. The full list is in Integration Technical Details.
- A test Contact or Lead already exists in Salesforce. Use a record with an email address you control (for example, your own work email) so you can open and redeem the gift.
- A Salesforce campaign to map to. You can use an existing campaign or create a new one from within Sendoso during campaign setup.
Tip: If you connected a Salesforce Sandbox, you can run this entire test there before connecting your production org.
Important: Don't use Test Mode for this test. Sends made in Test Mode don't push any data to Salesforce, so the campaign member, statuses and Tasks won't appear. Turn Test Mode off and send a real gift instead.
Step 1: Create a test campaign and map it to Salesforce
Start with a low-value gift so your test costs almost nothing. A $5 Amazon eGift works well because it moves through statuses quickly and you can redeem it yourself.
- In Sendoso, go to Campaigns and click Create Campaign.
- Select a low-value eGift (for example, a $5 Amazon gift card) and name the campaign something easy to find, such as SFDC Integration Test.
- When you reach the Campaign Tracking step, select Salesforce and choose your synced Salesforce account.
- Select an existing Salesforce campaign, or create a new one directly from Sendoso.
- Review the campaign member status mapping so you know which statuses to expect in Salesforce, then save the campaign.
Note: We recommend a 1:1 relationship between Sendoso campaigns and Salesforce campaigns. For more detail, see Setting Up: Salesforce Campaign Best Practices and FAQs.
Step 2: Send a gift to a test Contact or Lead
- Find your new test campaign from the Sendoso Send page.
- Enter the recipient's details. Use the exact email address that's on your test Contact or Lead in Salesforce.
- Complete the send.
Important: Sendoso finds the Salesforce record by matching the recipient's email address. If no Contact or Lead in Salesforce has that email, the send still goes out, but nothing will sync back to Salesforce. This is the most common reason a first test appears not to work.
Step 3: Confirm the campaign member and status updates
Within a few minutes of sending, your test recipient should appear as a member of the mapped Salesforce campaign.
- In Salesforce, open the campaign you mapped in Step 1.
- Scroll to the Campaign Members related list and confirm your test Contact or Lead is listed.
- Check the Status column. It should show the first status for the send (for example, Offer Sent).
- Open the eGift email yourself and redeem it. Refresh the campaign and confirm the member status updates (for example, Engaged, then Delivered).
If you've mapped the campaign's Actual Cost and Total $ Spent fields on the Writeback Mapping tab, you'll also see them update. Sendoso keeps these in sync automatically as you send from the campaign.
Step 4: Confirm the Task on the Contact or Lead
Sendoso logs gift activity as a completed Task on the recipient's Contact or Lead record.
- In Salesforce, open your test Contact or Lead.
- Look in the Activity timeline (or the Activity History related list).
- Confirm a completed Task appears for each gift status you've enabled, dated the day the status changed.
Note: Tasks are only created for the statuses you've turned on. To review or change them, go to Integrations > Salesforce > Task Activity. If you don't see a Task for a status like Engaged, check that it's enabled there. See Setting Up: Additional Salesforce Tracking Fields and Activity Mapping.
Optional: Additional tests
Once the core test passes, these optional checks confirm the rest of your setup.
Writeback Mapping
If you've mapped fields under Integrations > Salesforce > Writeback Mapping (for example, Total $ Spent on Contact, Gift Amount or Tracking URL), open the test record in Salesforce and confirm those fields now hold data from your test send.
Note: Your Salesforce admin needs to create these fields and give the integration user Edit access to them before Sendoso can write to them.
Sending from the Chrome Extension or Salesforce Lightning Component
If your team will send from inside Salesforce or Gmail, repeat Steps 2–4 using the Sendoso Chrome Extension or the Sendoso Lightning Component on the Contact or Lead page. Select the same test campaign, send to your test record, and confirm the campaign member status and Task appear as before.
Automations
If you plan to use Automations, build a simple Automation that sends from your test campaign, then trigger it for your test Contact or Lead. Confirm the send appears in Sendoso and that Steps 3–4 behave the same way.
Congrats! Your Salesforce integration is tested and ready for your team.
Best practices and considerations
- Create your campaign member statuses first. Sendoso maps gift statuses to campaign member statuses that already exist on the Salesforce campaign. Campaigns you create in Salesforce only include Sent and Responded, so add any other statuses you want (such as Delivered) in Salesforce before you map them. If you create the Salesforce campaign from Sendoso, the matching statuses are created for you.
- Create a Campaign Type for gifting. Create a "Gifting" or "Direct Mail" campaign type in Salesforce to organize these campaigns and simplify reporting.
- Default Mappings doesn't load in a Sandbox. This is expected. The Default Mappings page loads once you connect your production org, so plan to set up the default field mappings after you move to production.
- You don't need to redeem the gift. If the first status appears on the campaign member and the first Task appears on the Contact or Lead, the sync is working.
- Check field-level access, not just object access. The integration user needs Read access to the standard Salesforce fields on the objects Sendoso uses, and Edit access to every field Sendoso writes to.
- Fix permissions, then retry any Sync Errors. After you update permissions, go to Integrations > Salesforce > Sync Errors and click Retry on the failed rows to push the data again.
- Watch for anything that blocks Task creation. Validation rules or triggers on the Task object, or Einstein Activity Capture, can stop Sendoso from creating Tasks even when permissions are correct.
- Re-test after permission changes. If your Salesforce team later changes the integration user's profile or permission sets, run a quick test send to confirm data still syncs.
- Creating a Salesforce campaign from Sendoso has one limit. It only works if your org has no custom required fields on Campaign. If there are, campaign creation fails with an error message in Sendoso.
FAQs
My test recipient wasn't added to the Salesforce campaign. What should I check?
First, confirm the email you sent to exactly matches the email on the Contact or Lead in Salesforce. Next, confirm the Sendoso campaign is mapped to a Salesforce campaign in its tracking settings. Finally, check the Sync Errors tab under Integrations > Salesforce for a specific error message.
How long does it take for data to appear in Salesforce?
Usually within a few minutes of each status change. Status updates continue to sync as the gift moves through its lifecycle, so later statuses like Delivered may appear hours or days after the send.
The campaign member was added, but I don't see a Task. Why?
Tasks are only created for statuses enabled under Integrations > Salesforce > Task Activity. Also confirm the integration user has Create access on the Task object, and that Access Activities and Edit Tasks are checked on the integration user's permission set.
Can I test without affecting my production Salesforce data?
Yes. You can connect a Salesforce Sandbox from the Salesforce integration page and run this test there first. When you're done testing, disconnect the Sandbox and connect your production org. Then edit each Sendoso campaign and map it to a Salesforce campaign in your production org. Campaigns mapped to Sandbox campaigns don't carry over.
I'm seeing a sync error. What does the integration user need?
Most sync errors come from missing permissions. The integration user needs Marketing User checked, API Enabled, and Read, Create and Edit on Campaign, Campaign Member and Task, plus Read and Edit on Contact and Lead. For the full list (including Account access, Access Activities and Approve Uninstalled Connected Apps), see Integration Technical Details. For specific error codes, see Troubleshooting: Checking Salesforce Error Messages.
Will Sendoso reimburse the cost of my test sends?
Test sends are real gifts, so they're charged to your funding source like any other send. If you'd like a concession for gifts sent while testing the integration, reach out to your Customer Success Manager or Onboarding Specialist.
I have duplicate Contacts or Leads with the same email address. Which record gets the data?
When you send from the Sendoso platform, Sendoso writes to the first Contact or Lead it finds with that email address. To control exactly which record is updated, send from the Sendoso Chrome Extension or Lightning Component on that record. Sendoso then writes to the record you sent from.
The recipient didn't exist in Salesforce when I sent the gift. Can the data still sync?
Yes. Once the Contact or Lead exists in Salesforce with the matching email address, contact our support team and ask them to push the send data to Salesforce retroactively.
I built an Automation, but my test send didn't trigger right away. Is something wrong?
Probably not. Automations triggered by Salesforce campaign membership check for new members about once an hour, so allow up to an hour before you troubleshoot. If the send still hasn't triggered after an hour, check your Automation setup in Sendoso and make sure you've mapped fields in the Edit Default Mappings section of the Automation.