Using a Custom Revenue Amount Field

Last update: 2023-10-20

Topics:
Custom Revenue Amount
View more on this topic

Created for:

By default, Buyer Attribution Touchpoints will pull the Opportunity Amount from one of two fields:

Amount (SFDC Default)
Marketo Measure Opportunity Amount (Custom)

If you are using a custom Amount field on your Opportunities, we will need to configure a workflow in order to calculate the Buyer Touchpoint Revenue. This takes some more advanced knowledge of Salesforce, so it may require assistance from your SFDC Admin.

Starting off, we will need the following information:

API Name of your Amount field

From here, we’ll start creating the workflow.

Create the Workflow in Salesforce Lightning

The following steps are for Salesforce Lightning users. If you still use Salesforce Classic, those steps are listed below.

From Setup, type “Flows” into the Quick Find Box, and select Flows to start Flow Builder. From the right panel click the New Flow button.
Select Record-Triggered Flow and click Create on the bottom right.
In the Configure Start window, select the Opportunity object. From the Configure Trigger section, select A record is created or updated.
In the Set Entry Conditions section, under Condition Requirements, select Custom Condition Logic Is Met.
- From the search field, select your custom Amount field.
- Set the operator as Is Null, and the value as False.
- Set the evaluation criteria to Every time a record is updated and meets the condition requirements.
Under the “Optimize the Flow for” section, select Fast Field Updates. Click Done on the bottom right.
To add the element, click the plus (+) icon and select Update Triggering Record.
In the New Update Records window, enter the following:
- Enter a label—the API name will be generated automatically
- Under “How to Find Records to Update and Set Their Values,” select Use the opportunity record that triggered the flow.
- In the “Set Filter Conditions” section, select Always Update Record as a Condition Requirement to Update Record.
- In “Set Field Values for the Campaign Record,” from field, select the Marketo Measure Opportunity Amount and from value. Then select your custom Amount field.
- Click Done.
Click Save. A pop-up will appear. Type “Flow Label” in the Save the Flow window (the Flow API Name will be generated automatically). Click Save again.
Click the Activate button to activate the flow.

Create the Workflow in Salesforce Classic

The following steps are for Salesforce Classic users. If you have made the switch to Salesforce Lightning, those steps can be found above.

Navigate to Setup > Create > Workflow & Approvals > Workflow Rules.
Select New Rule, set the object as “Opportunity” and click Next.
Configure the workflow. Set the Rule Name as “Update Marketo Measure Opportunity Amount.” Set the Evaluation Criteria to “Created, and every time it’s edited.” For the Rule Criteria, select your custom Amount field and select the Operator as “Not Equal To” and leave the “Value” field blank.
Add a workflow action. Set this picklist to “New Field Update.”
Here you’ll fill out field information. In the “Name” field, we recommend using this naming: “Marketo Measure Opp Amount.” The “Unique Name” will automatically populate based off the “Name” field. In the “Field to Update” picklist select “Marketo Measure Opportunity Amount.” After selecting the field, select the “Re-Evaulate Workflow Rules after Field Change” box. In the “Specify New Field Value,” select “Use a formula to set the new value.” In the empty box, drop the API name of your custom Amount field. Click Save.
You’ll be brought back to a roll-up page for your workflow, be sure to “Activate” and you’ll be good to go. To activate, click Edit next to your new workflow and then click Activate.

Once you’ve completed these steps, the opportunities will need to be updated in order to trigger the workflow to have the new value from the custom opportunity field.

This can be accomplished by running your opportunities through Data Loader within SFDC. Please find details on using Data Loader in this article.