Campaign Member Correction Scenarios

When responses don't land where they should, the fix depends on two things: the state of the Lead or Contact, and whether an Opportunity is involved. This article lists the six most common correction scenarios and the recommended action for each. Find the one that matches your records, then follow the linked article for the full steps.

• Before you start
• Scenario overview
• Scenario 1: Inactive Lead or Contact
• Scenario 2: Active Lead or Contact with an active response
• Scenario 3: Active Lead or Contact without an active response
• Scenario 4: Opportunity with no association
• Scenario 5: Opportunity associated with a response on the same Contact
• Scenario 6: Opportunity associated with a response on a different Contact

Before you start

A few checks keep corrections clean, whichever scenario applies:

• Try reactivation first. If reactivation can reach the records, it reprocesses them for you. The manual backfill guide explains when a data load is the better choice.
• Know which statuses are active. Your Status Mapping defines which Lead, Contact and Response Status values count as active. A Lead can have only one active response, while a Contact can have more than one when the extra responses are tied to open opportunities. Responses and Active Responses covers the difference.
• Export before you change anything. Keep a copy of the records' current values so you can restore them if a load doesn't go as planned.
• Test a few records first. Run three to five records per scenario, check them, then load the rest in smaller batches.
• Plan for your own automation. Flows, routing and alerts that watch Response Status, funnel stages or Lead and Contact status can fire on every record you update.

Scenario overview

Note: Scenarios 1 to 3 correct funnel data. Scenarios 4 to 6 correct opportunity association. Run them as separate loads, funnel first. When any opportunity association code is set, the update isn't processed as a response.

Scenario 1: Inactive Lead or Contact

The person is in an inactive status and has no active response. This is the standard correction.

1. Update the Campaign Member with Admin Response Control set to 1. In the same update, set the Response Status and every funnel stage checkbox and date the record should have. The backfill decision table shows which values to use.
2. Update the Lead or Contact status to the matching active status in a separate load.

For the full walkthrough, see Build and run the load.

Scenario 2: Active Lead or Contact with an active response

The person is already active, and a different response is currently tracking their funnel. Your team decides which response should own it:

• Leave it as is. The existing active response keeps the funnel, and the new response stays inactive. No update is needed.
• Transfer the funnel. Remove the funnel stage values from the existing response and populate them on the new response. Use Admin Response Control set to 1 on both updates so Full Circle doesn't reprocess either record.

Note: If the existing response is tied to an opportunity, and that's the association you're changing, use scenario 5 instead.

Scenario 3: Active Lead or Contact without an active response

The person is already in an active status, but none of their responses is active. Follow scenario 1, with two differences:

• Response Status should match the person's current Lead or Contact status, according to your Status Mapping.
• Lead or Contact status stays as it is. There's no second load.

Records in this state won't be picked up by Score Reactivation, which watches inactive Leads and Contacts, so a manual correction is usually the only path.

Scenario 4: Opportunity with no association

The Campaign Member should be tied to an opportunity, and the opportunity has no response associated yet. A blank Response ID on the opportunity confirms it.

1. Update the Campaign Member with Admin Response Control set to 8. In the same update, set FCRM__FCR_Opportunity__c to the opportunity ID. Both must be set together, or the association won't process.
2. Adjust the relevant date fields. If a funnel stage date should differ from what the association set, update it directly.

More detail is in Associate opportunities. For opportunities created going forward, Opportunity Association can make this connection automatically.

Scenario 5: Opportunity associated with a response on the same Contact

The opportunity already references a different response, and both responses belong to the same Contact. Follow scenario 4, but use a swap code instead of 8:

• 72 swaps the association and keeps the previous response, which moves to Resolved - Already Engaged.
• 328 swaps the association and deletes the previous response. Deletion is permanent, so export the record first.

Both codes are listed in the useful codes table. If your org uses field swapping, the fields in that field set are copied from the previous response to the new one during the swap.

Scenario 6: Opportunity associated with a response on a different Contact

The opportunity already references a response that belongs to someone else. A swap code won't work here, because swaps require both responses to be on the same Contact and return error FCRM-101203 otherwise.

1. On the existing Campaign Member, set Admin Response Control to 1. In the same update, clear its funnel stage checkboxes and dates, along with the opportunity fields tied to the existing association.
2. Confirm the opportunity now reads as unassociated.
3. Follow scenario 4 to associate the correct Campaign Member.