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. Each scenario sets the Admin Response Control field (FCRM__FCR_Admin_Response_Control__c) on the Campaign Member to the code shown in the table.
- Before you start
- Scenario overview
- Scenario 1: Inactive Lead or Contact
- Scenario 2: Active Lead/Contact with active response
- Scenario 3: Active Lead/Contact, no active response
- Scenario 4: Opportunity with no association
- Scenario 5: Opportunity already tied, same Contact
- Scenario 6: Opportunity already tied, other 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
| No. | Scenario | Recommended action | Code |
|---|---|---|---|
| 1 | Inactive Lead or Contact | Update the Campaign Member, then update the Lead or Contact status | 1 |
| 2 | Active Lead or Contact with an active response that isn't tied to an opportunity | Decide whether to keep the existing active response or move its funnel stages to the new response | 1 |
| 3 | Active Lead or Contact without an active response | Update the Campaign Member to match the current status. No Lead or Contact update. | 1 |
| 4 | Campaign Member should be associated with an opportunity that has no association | Set the code and the Opportunity ID in the same update, then adjust dates | 8 |
| 5 | Opportunity is already associated with another response on the same Contact | Follow scenario 4 with a swap code | 72 or 328 |
| 6 | Opportunity is already associated with a response on a different Contact | Clear the existing association, then follow scenario 4 | 1, then 8 |
Note: Scenarios 1 to 3 correct funnel data. Scenarios 4 to 6 correct opportunity association. Run them as separate loads. For records that will be tied to an opportunity, run the association first. Full Circle fills in the funnel stages for you, and swaps with 72 or 328 carry the dates over. Then backfill only the records that aren't tied to an opportunity. 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.
- 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.
- 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/Contact with active response
The person is already active, and a different response that isn't tied to an opportunity 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. Set the new response's Response Status to mirror the Lead or Contact status. The previous response needs an inactive status, and Resolved - Already Engaged usually makes sense.
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/Contact, no active response
The person is already in an active status, but none of their responses is active. This also covers Contacts whose only active responses are tied to opportunities. Leave those responses as they are and activate the new one. 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.
Score Reactivation can pick these records up if your org has enabled the option to include active Leads and Contacts without active responses. Check your reactivation settings before choosing a manual correction.
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.
- 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.
- Check the funnel stage dates. They default to the Opportunity Created Date, which can create negative velocities. Align them where needed.
More detail is in Associate opportunities. For opportunities created going forward, Opportunity Association can make this connection automatically.
Scenario 5: Opportunity already tied, 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.
Funnel stage dates transfer with the swap, so you don't need to set them 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 already tied, other 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.
- On the existing Campaign Member, set Admin Response Control to 1. In the same update, clear its funnel stage checkboxes and dates and its FCRM__FCR_Opportunity__c field. The other opportunity fields on the Campaign Member are formulas and clear on their own.
- On the opportunity, clear Admin Originating Contact (FCRM__FCR_Admin_Originating_Contact__c), Response ID (FCRM__FCR_Response_ID__c) and Admin_CMArchive (FCRM__FCR_Admin_CMArchive__c). You can also clear First Campaign Touch, Last Campaign Touch and Primary Campaign Source. Until these are clear, Full Circle treats the opportunity as still associated and code 8 won't work.
- Confirm the opportunity now reads as unassociated.
- Follow scenario 4 to associate the correct Campaign Member.
Comments
0 comments
Please sign in to leave a comment.