Hi Grant,
Sorry for the delay in getting back to you but I was on leave.
Lead Source for us is the Channel which generated the marketing lead. Event, eSeminar, Online Paid, Online Organic etc...
I have built template programs by Channel, product and Region, Each of these are prepopulated with 95% standard data and the Regional teams cloning the programs only have a few items to update. These programs include a standard flow step which is to only update if Blank for both Lead Source - First Touch and Lead Source Detail - First Touch.
The following is an example of some flow steps within our eSeminar Channel > Progession > Registered > Smart Campaign > Flow:
Step 4 - Change Data Value |
Attribute: 'Lead Source - Last Touch' |
|
New Value: 'eSeminar' |
Step 5 - Change Data Value |
Attribute: 'Source Campaign' |
|
New Value: '{{my.ProgramName}}' |
Step 6 - Change Data Value |
Attribute: 'Lead Source Detail - Last Touch' |
|
New Value: 'Registered' |
Step 7 - Change Data Value |
Choice 1: If 'Lead Source - First Touch' is empty then: |
|
Attribute: 'Lead Source - First Touch' |
|
New Value: '{{lead.Lead Source - Last Touch}}' |
|
Default Choice: |
|
-- Do Nothing -- |
Step 8 - Change Data Value |
Choice 1: If 'Lead Source Detail - First Touch' is empty then: |
|
Attribute: 'Lead Source Detail - First Touch' |
|
New Value: '{{lead.Lead Source Detail - Last Touch}}' |
|
Default Choice: |
|
-- Do Nothing -- |
Step 9 - Interesting Moment |
Type: 'eSeminar' |
|
Description: 'Registered to {{my.ProgramName}}' |
We don't formally 'block' these fields as we find the templates work to control the data process.
We 'could' use the first touch information, along with Acquaisition information along with RCA - but have not quite goe there yet.
I hope this helps...
Victoria