Content Comparison

...

1. Primary Look UP

   1. primary_field - This part of the configuration is where you specify what you would like to be the primary lookup field for the Processr job - in this example the primary field is email

   2. primary_field_operater - This part of the configuration is where you state the logic for the lookup

      1. Equal - means it has to be an exact match eg adam@convertr.io - adam@convertr.io

      2. Contain - means it just has to contain the value within any part of the string Convertr - Convertr LTD

      3. Startswith - means that the beginning of the strings have to match EC2A 3EJ  - EC2A 4GH

      4. Endswith - means that the end of the strings have to match EC2A 3EJ  - EC1 3EJ

2. Secondary Lookup (*the user can set multiple lookup fields)

   1. The secondary lookup filed is where you can specify the additional lookup filed in the example it’s Secondary Look up Field

   2. operator - This part of the configuration is where you state the logic for the lookup

      1. Equal - means it has to be an exact match eg adam@convertr.io - adam@convertr.io

      2. Contain - means it just has to contain the value within any part of the string Convertr - Convertr LTD

      3. Startswith - means that the beginning of the strings have to match EC2A 3EJ  - EC2A 4GH

      4. Endswith - means that the end of the strings have to match EC2A 3EJ  - EC1 3EJ

3. Level

   1. The level states what lead data the processor should be looking at for:

      1. Advertiser will look for leads across campaign associated with that advertiser

      2. Campaign will look only for leads on the campaign

      3. Enterprise will look for leads across the whole enterprise regardless of campaign and advertiser.

4. Timeframe

   1. past_x_minutes this is where you determine the time frame of when the lookup should be checking for example if set to 1 this will only look for leads within the past minutes

5. Passed - the logic for this if the lead record matches on primary lookup but the secondary lookup field are different the timeframe and level specified eg the email and Secondary Look up Field have no matches

   1. result_passed

      1. appendn_field - this will add the filed to the lead record eg Did the Job pass?

      2. append_value - this will add the value to the lead record eg Yes

6. Failed - the logic for this is the lead record matches on primary lookup and the secondary lookup field are the same within the timeframe and level specified eg the email and Secondary Look up Field have matches matches

   1. result_failed

      1. appendn_field - this will add the filed to the lead record eg Did the Job fail?

      2. append_value - this will add the value to the lead record eg Yes

7. Primary Lookup Not Found - the logic for this is that if the primary lookup is not found within the timeframe and level specified eg the email does not exist on the level specified or it outside the timeframe stated

   1. result_primary_not_found

      1. appendnappend_field - this will add the filed to the lead record eg Was the Primary Lookup field Not Found?

      2. append_value - this will add the value to the lead record eg Yes

...