Campaign Process Technical Details & List of Execution Program
List of Tables Involved:
- Contact_list
- Contact_list_party
- Campaign_contact_list_party
- Marketing_campaign_contact_list (Final list will be generated here)
- Notify_email_data
Note:
- The notify_email_data table refers to SendGrid. You can see all the information in this table.
- This table acts as the staging table for sending marketing campaign emails and needs to be populated after the campaign is published.
Use the following fields:
- reference_type = CAMPAIGN
- reference_id = campaign_id
Other Notes:
- OAuth helps in authentication as well as identification of the tenant.
- The initial payload is called the parent log. It is stored in WEBHOOK_EVENT_LOG.
- The initial payload is processed by a scheduled job which creates child entries in WEBHOOK_EVENT_LOG. Each child entry refers to its parent entry via the PARENT_LOG_ID column
- If the event is a delivery event, then WEBHOOK_DELIVERY is populated.
- If the event is an engagement event, then WEBHOOK_ENGAGEMENT is populated.
- At the end of each parent log processing.
Contact List Management:
Sub Process 1: File Path Configuration:
The File path will be configured on the SYSTEM_PROPERTY table
Columns & Details:
SYSTEM_RESOURCE_ID=’ campaignlist’
SYSTEM_PROPERTY_ID =’ filepath’
SYSTEM_PROPERTY_VALUE = /home/centos/ICRM-Lead/hot-deploy/campaign/smartlist/
If the Path is not configured, then while uploading the file will get the error.
It is very important to configure the file
Sub Process 2: Configure Incoming and Outgoing Folders for the List Upload Process:
The SFTP is configured on the below SFTP_CONFIGURATION table
Its differs from client to client
Sample Seed:
insert into `sftp_configuration` (`SEQ_ID`, `USER_NAME`, `PASSWORD`, `PORT`, `HOST`, `LAST_UPDATED_STAMP`, `LAST_UPDATED_TX_STAMP`, `CREATED_STAMP`, `CREATED_TX_STAMP`, `ENABLE`, `MODEL_NAME`, `LOCATION`) values(‘contactListUpload’,’leacontactlist’,’LeadF!0jhtRE’,’22’,’10.0.0.46′,’2024-04-26 05:03:45′,’2024-04-26 05:03:45′,’2018-07-03 15:40:07′,’2018-07-03 15:40:07′,’Y’,’UPLOADLIST’,’/home/leacontactlist/’);
List of Tables & Jar supporting for upload Process: JAR Name – icrm_external_app.jar (Used for list Extraction Process)
Shell Script: contactlistupload shell script (Scheduled Every 15 minutes once per day)
List of Store Procedures:
contact_list_account
contact_list_lead
contact_list_contact_new
contact_list_customer
List of Staging Table
contact_list_staging
contact_list_temp
Integration of Supporting Programs and Jar Files:
Sub Process 1: Configuration of Jar Program for Contact List Upload Process:
JAR Name – icrm_external_app.jar (Used for list Extraction Process)
Shell Script: contactlistupload shell script (Scheduled Every 15 minutes once per day)
Sub Process 2: Configuration of Jar Program for Contact List Execution:
contact_list_account
contact_list_lead
contact_list_contact_new
contact_list_customer
Sub Process 3: Configuration of Jar Program for Campaign Contact List Execution:
No Jar
Sub Process 4: Configuration of Jar Program for Campaign Publish:
JAR Name : notify-data-processing-0.1.0.jar
Process
emailCampaignExtraction
dripCampaignExtraction
notifyEmailExtraction
webhookExtraction

