Advanced Response Configuration
Enable New Campaign Attribution System
This option enables the new (version 1.18) Campaign Attribution system. Deselecting this option will activate the old system. For most existing users, and for any new installation of Response Management, this should always remain checked.
Contact Status Field Name
If your company currently has a compatible status field for tracking contact status, enter the API name of that field here. Otherwise, leave this blank to use the default managed package field that comes with Response Management (FCR_Status__c field). Note that changing this option does not migrate any existing data, so it should only be set during configuration of a new org and should not be changed or updated after that.
Enable Async Responses
This option causes campaign member status updates by the repeat response user to be considered new responses even during future calls. Normally updates during future (async) calls are considered regular updates, not new responses.
Block Archive Updates
Selecting this option prevents updates to existing campaign member archives on opportunity objects due to synchronization events (such as contact updates) and will reduce the number of opportunity object updates. However, campaign members restored during a merge operation may not have the latest data. We recommend leaving this unchecked in most cases.
Background: On the opportunity object there is a Full Circle custom field (API name FCRM__FCR_Admin_CMArchive__c). This field is where the application will save a backup of the data from the campaign member on which the funnel is being tracked for this opportunity.
The data is saved so if the campaign member is deleted through a merge, the application will try to reinsert the campaign member into the campaign. If it can’t be added back to that campaign it will be added to the System Recovery campaign.
Sometimes Response Management will try to update this field with changes and it will be unable to save the opportunity record because a validation rule prevents it, and this failure will appear in the event logs.
Best practice is to use the admin update counter method to bypass the validation rule, however you can also use this setting to disable the backups and thus not receive the errors. If you do that, the data in the archive field won’t be updated and the most current funnel information from the campaign member may not be recovered.
Block Originating Response Deletion
The Originating Response is the campaign member with the active funnel that sourced the opportunity. This option prevents deletion of campaign member objects that are the originating response on an opportunity.
We would recommend this be checked, as the originating response is generally valuable information for funnel and influence reporting.
If a campaign member that is the originating response needs to be deleted, we provide tools for you to swap the opportunity association to use a different originating response, and then deleting the unwanted campaign member will be possible.
Block Deletion of Campaigns with Originating Responses
This option prevents deletion of Campaign records when any of their associated campaign member objects are the originating response on an opportunity. This option only takes effect if the Block Originating Response Deletion option is also selected.
If you really need to delete this campaign for some reason our recommendation is to swap use the opportunity association tools to change the associations from the opportunity to a relevant member of a different campaign, then delete the campaign.
Increment admin update counter on selected non-DML changes
Normally the Admin Update Counter field on an object is only incremented during database operations initiated by the Response Management application. When this option is checked, the counter will also be incremented during selected field changes by Response Management during triggers resulting from database operations initiated manually or from other applications.
The use case for this is generally either to use the counter in validation rules so that the application is allowed to save records where a person user would be blocked by a validation rule, or by developers.
Please note that the following 3 settings apply only to previous (1.21 and older) versions of Response Management. RM 1.22 and later will have been configured with the custom funnels feature, and for those orgs, these settings are not relevant.
Disable MQL Setting
This option disables automatic setting of the MQL and MQL Date fields. By default these are always set when a campaign member becomes an active response, and we recommend not checking this box. However in some cases the funnel may be designed to use a different set of fields to track the active response, or use different criteria.
Disable MQL on Progression
Applies only when Disable MQL Setting is on. If the MQL and MQL fields are blank, this option will prevent setting those fields to the date the funnel progresses (To SAL, SQL or to Won). When not selected these fields will be set with stage progression.
Disable SQL Setting
Click this box to disable the automatic setting of the SQL and SQL Date fields. You may want to do this if your SQL definition does not map to the Full Circle Insights definition of SQL and you wish to set the SQL stage and date manually or through custom code.
Disable First Owner Setting
Click this box to disable the automatic setting of the First Owner Assigned, Worked, and Type fields on the Campaign Member.
Normally this is disabled only after Funnels are enabled below. If you are a customer who has had Response Management for many years and have not upgraded to the new custom funnels, this configuration will stop the application from setting the owner fields listed. However, if you are using the new custom funnels, this does not apply to you. When using custom funnels feature, the owner tracking is set within the custom funnel settings and is completely customizable.
Please note that this setting MUST be disabled in order to use the Default Active Status Overrides (on Status Mapping configuration page, you can override the default active status set on the lead or contact when a response becomes active, based on the campaign sourced by value on the campaign.)
Enable Funnels?/ Disable Funnels
Please contact Full Circle Insights Customer Success prior to making any changes to this setting. Enabling this feature could result in unrecoverable data loss.
This setting is used when upgrading to the new custom funnel system, but should not be used without help from the CS team.
Lead Conversion Handling
Apply Field Defaults After Conversion
This option uses field initialization data to initialize blank fields after conversion. This may be required in orgs with validation rules on campaign member, Contact or Opportunity objects where a lead conversion creates objects that do not comply with the validation rules.
Default values will need to be created for the required fields if using this configuration.
Lead Conversion Test Control
Set this value to specify individual lead conversion diagnostic tests to run on the additional diagnostics page. Leave blank or set to zero to perform all tests. Specify a number from 1 to 6 to perform individual tests. This is used to avoid a known SFDC bug on older orgs that can occur when running multiple lead conversion tests in a single test class.
Active Mode Conversion Override
When enabled, an active user may convert a lead without an active response in cases where they are not creating an opportunity and the configured contact status is not an active status. Make sure they have a clear choice in conversion status values in order to select a contact status that indicates no further action.
For example, the user could convert a lead to a contact with a status of “Existing Opportunity” if the lead/contact is associated with an account that already has an active opportunity. Alternatively they could be added as “Nurturing” or “Recycle” to continue drip marketing if the account is not being actively pursued.
Async System Version
This option allows selection of the asynchronous processing system. This setting defaults to the newer 2015 on new installs (and using this default setting is strongly recommended). Contact Full Circle support for additional options. Warning - switching from the 2015 to an earlier version may require manual data adjustment to avoid data loss!
Maximum Queueable Chains
This configuration only applies to the newer 2015 async system. This setting specifies the maximum number of async jobs that will be chained. The default is “-1” and this represents no limits. Recommendation: -1 for production and 4 for developer orgs. Choose 0 for better performance at the cost of higher batch/future usage.
Scheduler Reset Window
(Only applies to Email service based async system) - Specifies the scheduler reset window on the new async system. This represents the target maximum time between an asynchronous request and the asynchronous operation (the actual time may be 30-60 seconds longer). Allowed range is 120 to 600.
Disable Fast Async
(Only applies to Email service based async system) - Disables the fast async feature on the new async system. Normally, the system will attempt to perform an immediate future call if certain criteria are met. Disable this feature only if instructed to do so by Full Circle Insights technical support.
Disable Scheduler For Update
Temporarily disables the asynchronous scheduler to allow package updates. Use this feature if instructed to by Full Circle technical support. Also displays current scheduler status, which will be normal unless clicked.
User-Based Async Scoring
This feature should only be used when there is a dedicated Marketing Automation User account in Salesforce. For more detail on how and why to use this, please see our Release Notes
Async User is the user processing the batches of incoming leads from the Marketing Automation system. Select the Salesforce Marketing Automation user.
Delay defines how long of an async delay, in minutes. The range is 2-20 and the default is 20.
Threshold defines the batch size of inserts that will apply to async scoring. For example, if the threshold is 3 then batches of 1, 2 and 3 records will apply, but batches of 4 records or more will not. The range is 1-5 and the default is 1.
Note that only Campaign Members inserted by the defined user that meet the batch size threshold criteria will be considered a candidate for User-Based Async Scoring. Campaign Members inserted via the Response Prompt UI do not apply.
Org specific custom feature control. Only enter values here when instructed to by Full Circle Insights technical support.
First & Last Touch Delay
Normally the opportunity first and last touch fields are set in a future context. This global setting allows you to specify the number of minutes to wait before these fields are set. Use this setting when you know your users immediately edit newly created opportunities and set this value to the time they would need to complete typical edits. This will prevent code update conflicts. Note: Only applies if the 2015 Async System is Enabled.
Taxonomy files are a legacy item that are no longer used. Please ignore this setting.
Disable Deal Explorer Visualization Tab
This option hides the Visualization tab on the Deal Explorer. We recommend this remain checked so the visualization tab remains hidden as it is a legacy feature that no longer offers a useful user experience.
Enable Response Summary Database
When enabled, the rebuild updates information displayed in charts in the Response Intelligence tab. We do not recommend users have visibility to this tab therefore this should remain disabled.
Bulk Test Control
Bulk Test Number
Bulk test classes contain multiple tests which are designed to run one at a time. This option specifies the test number to run. A blank or zero value causes no tests to run. Generally you would only run bulk tests to verify application limits under worst-case conditions. These tests can be run using Apex Test Execution.
Bulk enabled test classes that use these settings include:
Bulk Test Batch Size
This option specifies the size of the batch to use with the bulk test specified above. Valid values are 1 to 200.
Warning: Use of the extensibility API can interfere with the correct operation of the Response Management application. It may also void your Full Circle Insights warranty and result in additional support charges. This functionality is intended for advanced APEX developers only and should not be used without first consulting with Full Circle Insights.
This option enables the application extensibility model API. Refer to the Full Circle Insights Extensibility API documentation for further information. This is for use by your deployment team at the time RM is installed, or by your development team as required.
LIST OF PLUGIN CLASSES - any plugin classes that have been added will be displayed here.
Enter name of new class, then click Addin Plugin Class to add.
Class must implement an FCR_ExtensibilityAPI interface.
Changes to plugin classes take effect immediately.
Your Customer Success person will input classes during deployment or later support if needed, however this is rarely used as most plug in functionality has been migrated to the application.