Your Optimize Channel's Rules To Identify are used to identify traffic that is sourced from that channel. Each rule will leverage at least one element of either the Referring URL or the Landing Page URL captured for a referral.
Rules To Identify are a component of an Optimize Channel. They are configured when you create an Optimize Channel and can be updated when you edit an Optimize Channel.
Rules to identify components
This feature is only available with the Optimize add-on. Click here to get the add-on!When creating a Rule To Identify, there will be between 3 and 4 fields you must fill in. Refer to the tabs below to learn more about each field.
"Where" the rule will look to find the Rule Value(s). This is selected from the 1st drop-down menu when creating a Rule To Identify.
See the 1st table in the update Rules To Identify section to view all available Rule Target options.
Example: Landing Page URL
"How" the Rule will attempt to identify traffic. This is selected from the 2nd drop-down menu when creating a RUle to Identify.
See the 2nd table in the Update Rules To Identify section to view all available Rule Logic options.
Example: Exactly Matches
The Rules To Identify works in an AND/OR system: Selecting 
[Add] AND will add conditions to a rule, whereas selecting [Add] OR will add a "separate" rule. When OR is selected, any of the conditions linked by an OR will identify the channel's referral. When AND is selected, all of the conditions linked by an AND are required to identify the channel's referral.
When creating or updating a Rule To Identify, impact.com recommends keeping the logic as simple and readable as possible. This will make ongoing support of your rules more effective and efficient.
Below are the Rule Target descriptions that can be used in a Rule To Identify. Be sure to select Save after making changes. Refer to the Optimize Setup Scenarios article for examples of Rules To Identify.
Note
You cannot configure the Rules To Identify for Direct (where there is no referrer) and Organic Referral (where there is a referrer) channels, also known as the Default Channels. These channels are specifically for cases where traffic does not meet the qualifications for any Rules To Identify to be applied.
Rule Target | Description | Example |
Landing Page URL | The entire URL on which referred traffic lands. |
|
Landing Page Domain | The part of the URL that follows the protocol and precedes the subdirectory/path (if a path is present) or the query string (if a path is not present). |
|
Landing Page Query String | All parameter key-value pairs that follow the question mark ( ? ), which marks the beginning of the query string. |
|
Landing Page Parameter | A specific key-value pair present in the query string. |
|
Referring URL | The entire URL that traffic comes from. |
|
Referring Domain | The part of the URL that follows the protocol and precedes the subdirectory/path (if a path is present) or the query string (if a path is not present). |
|
Referring Query String | Everything after the URLs path (if present) or after the top-level domain (if no path exists). |
|
Referring Parameter | A specific key-value pair present in the query string. |
|
You can also select how a Rule Target (found in the table above) is applied to the Rule Value 2 (what you enter in the final field of a Rule To Identify) by selecting the Rule Logic. See the table below for more information on Rule Logic options.
Rule Logic Option | Description | Example |
Exactly Matches | The exact Rule Value 2 configured must be found in the Rule Target, with no additional characters before or after. | Rule: Landing Page Parameter Example included URL:
|
Contains | The Rule Value 2 must be found in the Rule Target. | Rule: Landing Page Parameter Example included URL:
|
Starts With | The Rule Value 2 configured must be found at the beginning of the Rule Target. | Rule: Landing Page Parameter Example included URL:
|
Ends With | The Rule Value 2 configured must be found at the end of the Rule Target. | Rule: Landing Page Parameter Example included URL:
|
Matches Regex | The Rule Target's value must be a regex match to the Rule Value 2. Learn more about regular expressions. Test a regular expression. | Reach out to your CSM (or create a support ticket) for help with this Rule Logic option. |
Does Not Exactly Match | The exact Rule Value 2 configured must NOT be found in the Rule Target. | Rule: Landing Page Parameter Example excluded URL:
|
Does Not Contain | The Rule Value 2 configured must NOT be found in the Rule Target. | Rule: Landing Page Parameter Example excluded URL:
|
Does Not Match Regex | The Rule Target's value must not be a regex match to the Rule Value 2. Learn more about regular expressions. Test a regular expression. | Reach out to your CSM (or create a support ticket) for help with this Rule Logic option. |
Matches Any | The Rule Value 2 is a comma-separated series of Exactly Matches values (see the Exactly Matches row). Do not use spaces between each entries. | Rule: Landing Page Parameter Example included URLs:
|
Contains Any | The Rule Value 2 is a comma-separated series of Contains values (see the Contains row). Do not use spaces between entries. | Rule: Landing Page Parameter Example included URLs:
|
Is Present | The provided Landing Page Parameter value must be included in the URL. Only available when | Rule: Landing Page Parameter Example included URL:
|
Is Not Present | The provided Landing Page Parameter value must NOT be included in the URL. Only available when | Rule: Landing Page Parameter Example excluded URL:
|