Learn the most common reasons why Campaign data is not appearing in your Salesforce account and how to resolve them.
If your Salesforce integration shows as connected but data is not appearing in Salesforce (or your Salesforce sandbox), this article walks through the most common causes and how to resolve them. Common problems include:
- Integration status shows “Connected” but no records appear in Salesforce
- Campaigns sync but Contacts or Opportunities do not
- Some records sync while others silently fail
- Sandbox environment remains empty after connecting the integration
- Opportunities fail with a DUPLICATE_VALUE error on the RallyUp_ID__c field
- General donations do not sync, but item-based transactions (e.g., auction bids) do
What should I confirm before troubleshooting my Salesforce integration?
- Salesforce Nonprofit Success Pack (NPSP) is installed. The RallyUp Salesforce integration is built for NPSP and may not work without it.
- Three custom fields exist on your Salesforce Campaign object, each with the External ID checkbox enabled: RallyUp Campaign ID, RallyUp Team ID, and RallyUp Participant ID.
- Required field mappings are configured in the RallyUp integration settings.
Cause 1: No transactions have occurred yet
The RallyUp Salesforce integration is webhook-based, meaning it syncs data in real time when specific events happen. It does not retroactively sync historical data.
- Transactions integration: Triggers only when a donor completes checkout on a RallyUp campaign.
- Peer-to-Peer integration: Triggers only when a participant or team registers.
Solution: Run a test donation on one of your Campaigns to trigger the sync. Use a live or draft Campaign — the integration sends data from both. After the test donation completes, check Salesforce for the new Contact, Opportunity, and Campaign records.
Cause 2: Salesforce flows or automations are blocking the sync
If your Salesforce org has custom flows, Process Builder rules, or Apex triggers on the Contact, Opportunity, or Campaign objects, they can block the incoming data from RallyUp. This happens when a flow requires a field that RallyUp does not provide.
Example: A custom flow on Opportunity create/update (such as “Opportunity – Create/Update – After”) that requires a field like weaverTemplateId for a tax receipt system will cause the Opportunity record to fail, even though Campaigns and Contacts may succeed.
Solution:
- Check your Salesforce Setup for any active flows, Process Builder processes, or Apex triggers on the Contact, Opportunity, and Campaign objects.
- Look for flows that require fields RallyUp does not populate. Common culprits include tax receipt automation, custom approval processes, and third-party app integrations.
- Temporarily deactivate suspect flows, then run another test donation.
- If records sync after deactivation, update the flow to handle cases where the triggering field may be blank.
Cause 3: Required Salesforce fields are not mapped
Salesforce objects can have required fields that must be populated on record creation. If RallyUp does not supply a value for a required field, the record creation will fail silently.
Common required fields that cause issues:
- Opportunity Stage: Salesforce requires a Stage value on every Opportunity. If this field is not mapped from RallyUp, Opportunities will fail to create even when Campaigns and Contacts succeed.
- Campaign Name: If a RallyUp Campaign has no title (displays as “Untitled” in the UI but is blank in the backend), Salesforce will reject the Campaign record with the error: Required fields are missing: [Name].
For Opportunity Stage: Verify that the Opportunity Stage field has a mapped value or a default value configured. RallyUp does not currently offer a Stage mapping, so you will need to set a default Stage value directly in Salesforce using a flow or default field value on the Opportunity object.
For Campaign Name: Make sure every RallyUp Campaign has a title before running the integration.
Cause 4: Partial sync (some objects sync, but others do not)
The integration processes Campaign, Contact, and Opportunity records in separate steps, and a failure in one step does not necessarily block the others.
Solution: Identify which object types are syncing and which are not. For the failing object type, check for required fields, active automation, and validation rules.
Cause 5: Duplicate value error on RallyUp_ID__c
Salesforce may reject Opportunity records with a DUPLICATE_VALUE error on the RallyUp_ID__c field when an Opportunity with that RallyUp transaction ID already exists. This is common during sandbox testing with repeated transactions.
Solution: Delete existing duplicate Opportunities before retesting, or have your Salesforce admin temporarily relax the uniqueness constraint on RallyUp_ID__c in the sandbox.
Cause 6: General donations are not syncing (item-based transactions only)
In some cases, item-based transactions (such as Auction bids or Raffle entry purchases) sync successfully while general donations do not. This can happen when field mapping only populates required fields for item-based transaction types.
Solution: Compare a successful item-based transaction with a failed general donation to identify field differences. Review field mappings and Salesforce validation rules on the Opportunity object.
Frequently Asked Questions
Why does my Salesforce integration show as “Connected” but no records appear?
This usually happens because the RallyUp Salesforce integration is webhook-based and only syncs data in real time when a transaction occurs. It does not retroactively sync historical data. Run a test donation on one of your Campaigns to trigger the sync, then check Salesforce for the new Contact, Opportunity, and Campaign records.
Why do Campaigns sync but Contacts or Opportunities do not?
RallyUp processes Campaign, Contact, and Opportunity records as separate steps, so a failure in one step does not necessarily block the others. This is often caused by Salesforce flows, Process Builder rules, or Apex triggers that require a field RallyUp does not provide, or by a required field like Opportunity Stage that has no mapped or default value. Check Salesforce Setup for active automation on these objects and verify your required field mappings.
Why am I seeing a DUPLICATE_VALUE error on RallyUp_ID__c?
This error appears when Salesforce already has an Opportunity record with that RallyUp transaction ID, which commonly occurs during sandbox testing with repeated transactions. Delete the existing duplicate Opportunities before retesting, or ask your Salesforce admin to temporarily relax the uniqueness constraint on RallyUp_ID__c in the sandbox.
Why is my Salesforce sandbox still empty after connecting the integration?
An empty sandbox usually means no qualifying transaction has occurred yet, since the integration only syncs going forward from the moment it triggers. It can also happen if Salesforce Nonprofit Success Pack (NPSP) is not installed, or if the required custom fields with External ID enabled are missing on your Campaign object. Confirm these prerequisites, then run a test donation to trigger the sync.
Why do general donations fail to sync while Auction bids or other item-based transactions succeed?
This typically points to a field mapping issue, where your configuration only populates the required fields for item-based transaction types and leaves gaps for general donations. Compare a successful item-based transaction with a failed general donation to spot the field differences, then review your field mappings and any Salesforce validation rules on the Opportunity object.