Align.ly Attribution uses a Date/Time field on the Campaign Member record in order to calculate attribution. In the product, we call this "Engagement Date".

Within the Align.ly Attribution managed package, we include a field called Engagement Date (API Name: algnatt__Engagement_Date__c) that is the default field. When you first run Align.ly Attribution, Engagement Date will be set to the Created Date of your existing Campaign Member records. Going forward, the default value of the Engagement Date field is a formula field set to NOW(). If the Date/Time needs to be changed, you can easily edit the field to overwrite the value.

You also have the option to create your own custom Data/Time field on Campaign Member. If you do so, we recommend you also configure the default value to be a formula set to NOW().

Based on the Date/Time field you choose to use, you'll want to update the "Engagement Date" field in Align.ly Attribution Settings. To do so, follow these steps:

• Click on Setup -> Develop -> Custom Settings
• Click "Manage" next to Align.ly Attribution Settings
• Update the "Engagement Date" field with the API Name of the custom field you are using:
• The default value: algnatt__Engagement_Date__c
• If using your own Date/Time field, it will likely look something like this: Attribution_Date__c (be sure to include __c)

Align.ly Attribution calculates a field called Attribution Type. Attribution Type can be Sourced or Accelerated. Part of the calculation is looking at the Opportunity Start and Opportunity End Dates.

Where is this configured?

In Lightning: Go to Setup -> Custom Code -> Custom Settings then click "Manage" next to "Align.ly Attribution Settings".

In Classic: Go to Setup -> Develop -> Custom Settings then click "Manage" next to "Align.ly Attribution Settings".

You will see the following fields:

• Opportunity Start Date/Time Field (AB)
• Opportunity End Date Field (AB)
• Opportunity Start Date/Time Field (OB)
• Opportunity End Date Field (OB)

Default Settings

When installing Align.ly Attribution for the first time, the default values will be the following:

• Opportunity Start Date/Time Field (AB)
• Field: Opportunity Created Date
• API Name: CreatedDate

• Opportunity End Date Field (AB)
• Field: Opportunity Close Date
• API Name: CloseDate

• Opportunity Start Date/Time Field (OB)
• Field: Opportunity Created Date
• API Name: CloseDate

• Opportunity End Date Field (OB)
• Field: Opportunity Created Date
• API Name: CloseDate

When would I need to use a different field?

The most common use case we see is for using a custom field for Opportunity Start Date. For example, your business might consider an Opportunity owned by marketing until to progresses to Stage 2. In this case, you'd create a custom date/time field on Opportunity and timestamp it with a value when the Opportunity moves from Stage 1 to Stage 2.

How to Use a Custom Field

If you'd like to use a different field for either Opportunity Start Date or Opportunity End Date, you need to create a custom field on the Opportunity object and then enter the API Name of the field into the custom setting.

A few important notes:

• If you use a custom field, make sure it always has a value and is never blank.
• Opportunity Start uses a Date/Time field while Opportunity End uses a Date field.
• When updating the API Name in the custom settings, be sure to include "__c" on the field name if it is a custom field that you created.

Align.ly Attribution's account-based attribution model has the ability to incorporate Campaigns attached to Leads. The only requirement is that the Leads are related to an Account via an Account Lookup field on Lead.

The Account Lookup field on Lead can be a custom field created by you in your Salesforce environment, the "Matched Account" (algnlta__Matched_Account__c) field from Align.ly Lead-to-Account, or an Account Lookup field from another third-party lead-to-account matching solution.

Enabling Matched Leads in Account-Based Attribution Models

To enable the use of matched Leads in account-based attribution models, follow these simple steps:

• Go to Setup -> Custom Code -> Custom Settings
• Click "Manage" next to Align.ly Attribution Settings
• In the "Account Lookup Field on Lead" setting, enter in the API Name of your Account Lookup field
• If using Align.ly Lead-to-Account, enter "algnlta__Matched_Account__c"
• If using your own custom field or another third-party lead-to-account matching solution, you can find the API Name of the Account Lookup field on Lead by following these steps:
• Go to Setup -> Object Manager -> Lead
• Click on "Fields & Relationships"
• Look for the field with a Data Type of "Lookup(Account)" and copy the value of the "Field Name"
• The "Field Name" is what you will want to enter into the "Account Lookup Field on Lead" setting in Align.ly Attribution Settings
• Click "Save"
• That's it! That's all the configuration required to now incorporate Campaigns of Matched Leads into your account-based attribution models.

The "Sourced Attribution Duration (in days)" setting is the number of days BEFORE the Opportunity Create Date (or custom field setting) that a Campaign Member record will be eligible for attribution and be considered "sourced".

The "Engagement Date" (or custom field setting) is the date field used to determine if the Campaign Member record is within the time period.

Configuring batch scope sizes is an advanced feature that is typically used to help troubleshoot issues. If you are unfamiliar with Salesforce batch jobs, they are used to process large numbers of records in Salesforce. To process records more efficiently, Salesforce breaks up a batch job into smaller, more manageable chunks of records. The batch job scope size refers to the number of Salesforce records processed in a single "chunk" within the overall batch job.

In Align.ly Attribution, there are three configurable options in Custom Settings:

• Batch Scope Size Associate Opps
• Batch Scope Size Update Type
• Batch Scope Size Calculate Models

The default value for all three configurable settings is "200", which means 200 records will be processed in each batch "chunk".

In some cases, it might be necessary to reduce the batch scope size for a specific batch job. For example, if you get an error, reducing the batch scope size to "1" might help isolate and identify the error.

Configuration

In Lightning: Go to Setup -> Custom Code -> Custom Settings then click "Manage" next to "Align.ly Attribution Settings".

In Classic: Go to Setup -> Develop -> Custom Settings then click "Manage" next to "Align.ly Attribution Settings".

On the Campaign Member object in Salesforce you will see two fields that were added as part of the Align.ly Attribution managed package:

• [AB] Lock Campaign Member
• If checked, the Campaign Member will be excluded from account-based attribution calculations.

• [OB] Lock Campaign member
• If checked, the Campaign Member will be excluded from opportunity-based attribution calculations.

How is this field typically used?

Most likely you will not need to use this field or leverage this functionality. However, if you do find yourself needing the ability to selectively exclude a specific Campaign Member record from attribution, you can do so by checking off the respective field based on if you're running account-based and/or opportunity-based attribution.

On the Opportunity object in Salesforce you will see two fields that were added as part of the Align.ly Attribution managed package:

• [AB] Lock Opportunity
• If checked, the Opportunity will be excluded from account-based attribution calculations.

• [OB] Lock Opportunity
• If checked, the Opportunity will be excluded from opportunity-based attribution calculations.

How is this field typically used?

Most organizations will typically have Opportunity Types for new business, cross sells, up sells, and/or renewals. While it's common for marketing attribution to be associated to new business, cross-sells, and up-sells, you may want to exclude renewal opportunities. In this case, you would automatically update the Lock Opportunity field when the Opportunity is a renewal using a Salesforce Workflow or Process Builder.

This feature is the "WHERE" portion of a SOQL query to further narrow down the Campaign Member records which are processed for the Opportunity-based attribution model.

How is this feature typically used?

The feature is pretty flexible and we see a wide range of uses from our customers. Some of the most common are if there is a specific type of Campaign that should be filtered out or the number of records processed each time Align.ly Attribution runs needs to be limited. Here are examples:

• Campaign.Type != 'Sales Prospecting Lists'
• algnatt__Engagement_Date__c = Last_N_Days:366

This feature is the "WHERE" portion of a SOQL query to further narrow down the Opportunity Contact Role and Opportunity records which are processed for the Opportunity-based attribution model.

How is this feature typically used?

The most common use cases is to filter out renewal opportunities from your attribution models or filter out a specific Contact Role like "Partner". Here are examples of how this can be done:

• Opportunity.Type != 'Renewal'
• Role != 'Partner'

This feature is the "WHERE" portion of a SOQL query to further narrow down the Campaign Member records which are processed for the Account-based attribution model.

How is this feature typically used?

The feature is pretty flexible and we see a wide range of uses from our customers. Some of the most common are if there is a specific type of campaign that should be filtered out or the number of records processed each time Align.ly Attribution runs needs to be limited. Here are examples:

• Campaign.Type != 'Sales Prospecting Lists'
• algnatt__Engagement_Date__c = Last_N_Days:366

This feature is the "WHERE" portion of a SOQL query to further narrow down the Opportunity records which are processed for the Opportunity-based attribution model.

How is this feature typically used?

The most common use case is to filter out renewal opportunities from your attribution models. To do this, you would enter the following assuming you have an Opportunity Type of "Renewal":

• Type != 'Renewal'