New Features
Pre-Opportunity Funnel Swap
Response Management now includes the ability to manually reassign funnel data from one campaign member response to another before an opportunity is created. This feature gives administrators and marketing operations teams a straightforward way to correct situations where funnel milestones - such as MQL dates, inquiry checkboxes, and other funnel stage fields - are attached to the wrong campaign member record.
Background
Currently, only the active response tracks funnel progression. Occasionally, the system may set a default or system-generated response as the active response when a more meaningful campaign response - such as an inbound email or marketing engagement - comes in shortly after. When this happens, the funnel data ends up on the wrong campaign member, and the more meaningful response is left without any funnel history. Previously, correcting this required a manual, time-consuming process. The Pre-Opportunity Funnel Swap feature makes this correction simple and fast.
Who does it benefit?
Marketing operations teams and Salesforce administrators who need to correct funnel data attribution on campaign member records before an opportunity is associated.
What problem does this new feature solve?
When the wrong campaign member becomes the active response - due to reactivation logic, system defaults, or the order in which responses come in - funnel milestones and dates end up on the wrong record. This creates inaccurate attribution data that is difficult and time-consuming to fix manually. The Pre-Opportunity Funnel Swap feature allows administrators to move funnel data to the correct campaign member record quickly, with full control over exactly what gets moved.
Enablement Instructions
Step 1 — Configure funnel stage order
Before using the Swap Funnel feature, you must define the order of your funnel stages in your configuration.
Navigate to Funnel Metrics Configuration and set the stage order for your active funnels. This is required regardless of whether your organization uses one funnel or multiple, and must be completed before the feature will work correctly.
Step 2 — Add the Swap Funnel button to your page layouts
The Swap Funnel button can be added to three locations depending on your team's preferred workflow:
- Lead or Contact record — Allows you to see the current active response and select a different campaign member to swap funnel data to.
- Campaign Member record — When clicked from a specific campaign member, that record is automatically selected as the destination for the swap. No selection is needed.
To add the button, navigate to the relevant page layout in Salesforce Setup and add the Swap Funnel button to the desired record page.
Step 3 — Using the Swap Funnel feature
When the button is clicked, a panel will appear showing the current active response. From there, select the destination campaign member - the record you want to become the new active response with the funnel data transferred to it. You will also have the following options:
- Swap funnel fields - Moves all funnel stage checkboxes, dates, and milestone fields from the source to the destination record (on by default).
- Swap sync fields - Moves any configured sync fields along with the funnel data.
- Swap response date - Transfers the response date from the source to the destination record.
- Delete source response - Deletes the original campaign member record after the swap. This is the recommended option when the source record is a system default or placeholder response, as it keeps your data clean.
Note: This feature only works on campaign member records that are not yet associated with an opportunity. Once an opportunity is attached to a response, the funnel cannot be swapped using this tool.
Fixes
Date-to-Datetime Conversion Now Uses End of Day
Resolved an issue where date fields converted to datetime values were using midnight (12:00:00 AM) as the time, which could cause Full Circle to stop looking for matching data after the very start of the day. For example, if a response was created at 10:00 AM, the system might not recognize it as occurring within the same day. Date fields will now convert to the last moment of the day (11:59:59 PM) to ensure that all activity occurring throughout the day is captured correctly.
Who does it benefit?
All Full Circle Response Management customers, particularly those who experience gaps in data matching or attribution where records created later in the day are not being associated correctly.
What problem does this fix solve?
When Full Circle converted a date field to a datetime for comparison purposes, it defaulted to midnight at the start of the day. Any response or activity that occurred later in that same day could fall outside the comparison window, causing missed associations and attribution gaps. Using the end of day ensures the full day's worth of data is always included.
Enablement Instructions
This fix does not require enablement.
Account Based Marketing
Account Merge Handling
Resolved an issue with how the Account Based Marketing (ABM) product handles Salesforce account merges. When two accounts are merged in Salesforce, the ABM product will now correctly recognize and process the merged account, ensuring that account-level engagement data is preserved and attributed accurately after the merge.
Who does it benefit?
Customers using the Full Circle Account Based Marketing product in organizations where Salesforce account merges occur.
What problem does this fix solve?
When accounts were merged in Salesforce, the ABM product was not handling the merge correctly, which could result in lost or misattributed account engagement data.
Enablement Instructions
This fix does not require enablement.
Download Functionality Fix
Resolved an issue where download functions within the Account Based Marketing product were not working correctly under certain conditions.
Who does it benefit?
Customers using download functionality within the Full Circle Account Based Marketing product.
What problem does this fix solve?
Downloads within the ABM product were failing under certain conditions, preventing users from exporting data as expected.
Enablement Instructions
This fix does not require enablement.
Comments
0 comments
Article is closed for comments.