Salesforce Integration FAQs 🌠

Our integration is a one-click integration, done on a user by user basis.

No, the Salesforce integration is done on a user per user basis and is a one click integration. Depending on your permissions, you may need an admin user to set up campaigns and edit campaign member statuses. Otherwise, it really is easy to integrate.

Yes, as long as the fields live within the lead, contact. campaign or opportunity objects, we can use these in our triggered campaigns.

We don't currently support using those custom fields within the e-gift card emails.

Yes, we map our Reachdesk campaigns to Salesforce campaigns. When an interaction happens or changes with a Reachdesk campaign, we will update the campaign member status in Salesforce accordingly.

You can do both, but how you choose to do this depends on how granular you'd like to report. We'd recommend mapping on a 1-2-1 basis (one Reachdesk campaign to one Salesforce campaign), so you can really see over time, which types of initiatives are working best for you with regard to deliveries/claims, as well as influence on opportunities. Some customers have a high level gift card campaign for example, which they then map all gift card campaigns to, but this wouldn't show you which particular gift card/initiative drove the most influence on opportunities.

We do not edit or overwrite any information in your lead, contact and opportunity objects. We use the information to process a Reachdesk campaign. We write to campaigns and campaign member statuses. We also write to tasks on the lead and contact level. More on this here.

We read from all available fields on the lead, contact, opportunity and campaign objects. We write to campaigns and campaign member statuses. We also write to tasks on the lead and contact level. More on this here.

Yes, the connector that is used to send a Reachdesk campaign will also receive email notifications that the campaigns have been sent and delivered (for physical gifts).

If you don't already have campaign type set up for direct mail and e-gifting, we'd recommend setting up a new type for both. One for physical gifts and one for e-gifts. This is because the statuses differ for these two types of sends, so will require different statuses to be added in your setup (as per this doc).

There are usually a few reasons as to why this could be happening.

2. The contact/lead you have sent to must exist in Salesforce. If they don't they won't sync into the campaign in the first place.

If you are still having issues, please reach out to us.

Reachdesk doesn't map to task type, so this will be something happening on the Salesforce side and is to do with the default set up when a task comes in. There is a thread here which talks to this point and explains how to change.

The sync and subsequent updates to tasks and campaigns is pretty instant, but on some occasions it could take up to 15 minutes.

Yes, as long as that information is within the lead, contact, campaign or opportunity objects in Salesforce, we can use it in our triggers in Reachdesk.

Salesforce will use the information from the connector used to sync to campaigns from Reachdesk to Salesforce. When writing to tasks, the sender of the Reachdesk gift will write to the task activity (as long as they have the Reachdesk <> Salesforce connection on).

We only pull and process information from your Salesforce. So in terms of what we process, it will only ever be a lead or contact's name and their email/physical address. This is disposed of once it has been used for its intended purpose. For triggered campaigns, we will read something being added/updated in the contact, lead, campaign and opportunity objects.

We only pull information from Salesforce, and will not update/overwrite any field information. We simply map Reachdesk campaign activity back to the activity record, and change campaign member statuses. As above, we can trigger off of any fields within those objects: lead, contact, campaign or opportunity.

Yes you can, as long as you map the Reachdesk campaign to a Salesforce campaign (remember to map the statuses too). The contact/lead you're sending to must also exist in Salesforce already.

What happens if I try to send/trigger a campaign and there is no balance?

The send will look like it's happened but it will sit in 'pending'. If you try to approve, you will be notified that it cannot be sent as there is no budget. Once you have topped up you can approve that send. Try to estimate potential spend to avoid this happening.

What happens if I try to send/trigger a campaign when there is no stock?

The send will look like it's happened but it will sit in 'pending'. If you try to approve, you will be notified that it cannot be sent as there is no stock. The send can sit there until stock is in, or the engage expires.

How often do you call the API?
- 1 API call to check the matching contacts/leads/opportunities/campaign member for each triggered campaign. This happens twice an hour.
- 1 API call per engage sent to update the status. The campaign member status update should be 'close to' instantaneous when an action happens with the engage (opened/clicked/etc).