List Creation
List creation primarily depends on the list criteria and the target region. Once the list type is identified and the list requirements are in place, processing of the list can be done by using the standard scripts of that region.
Scripts are executed to pull contacts from Customer Experience Database (CXD), which collects contact data, social interactions, Oracle.com browsing information and downloads, as well as data from other "non-traditional" data sources.
The List team uses Oracle database in the back end and SQL Developer Tool as front end in processing the SQL scripts. They then generate a preview of emails or final phone or postal list, which can be exported into Excel and provided to the Marketers through GMSS portal for their approval. At times, external sets of additional contacts or accounts are provided by marketers for processing, those files will be saved in excel and loaded into the table for processing.
Note: Single-byte character sets work well for languages with a relatively small number of characters. Eventually, most of us must make a jump to multi-byte encodings for some languages like Japanese and Chinese which has larger character sets. Hence please keep multi-byte characters and Unicode character sets (UTF-8) in mind when working in foreign languages like Japanese, Chinese and Russian etc.
The list creation process involves the following steps:
- Processing the respective regional standard scripts
- Script execution
- QA process
- Approval process
 People
2 |
 Prep time
30 mins |
 Time
10 mins |
 Difficulty
Medium |
STEP 1 - Regional List Classifications
To support the broad spectrum of global marketers, List team implements the business processes that best suit the need in a specific region. All the regional teams support marketers with contact lists to conduct events, webcasts and webinars to promote Oracle products and services based on their regional restrictions.
Scripts prepared for the requests are executed in the SQL Developer environment with Oracle as database in the back end. Script execution pulls contacts matching the list criteria from the huge Oracle Customer Experience Database (CXD). The contact list is then stored in an Excel format (.xlsx) either as a preview list of emails or contact list of phone or postal contacts according to the list channel selected by the requester in the portal under each list request.
The table below provides region and country details of the Target List.
| Region | Coverage Area |
|---|---|
| North America (NA) | United States and Canada |
| EMEA | 146 countries in Europe, Middle East and Africa, including EE&CIS, MEA, WCE and UK sub-regions. |
| APAC | 56 countries across the Asia Pacific region (excluding EMBARGAROED COUNTRIES) |
| JAPAN | Japan Note : JAPAN is a single-country region and an opt-in country. There are fewer region-specific criteria in JAPAN as compared to other regions. Most list-request targets will be state specific, meaning that the list will be filtered based on specified states for both English and Japanese contacts. |
| Alliances & Channels (A & C) | 43 countries in Latin America, including 9 sub-regions |
| LAD | Global – All Regions Note : Partner Lists are pulled from subscribed Oracle Partner Network contacts. They extract partner data records based on K-Zone Products and Pillar details. |
| Oracle University Team | Global – All Regions Notes : OU provides target-audience lists to promote Oracle University courses, certifications, offers and trainings for corporate organizations through email or phone channel for regions across the world. OU uses student data for segmentation and analysis from various sources, such as: Oracle Training Administrator (OTA), course evaluations (training data), certifications and exams, E-kits (course kits downloaded by students), Workforce Development Program (training purchased by institutes), streams (trial learning subscriptions) and orders (any orders made in the Oracle University account), along with customer data from Customer Experience Database (CXD). |
STEP 2 - Quality Assurance Process
Review process is to have a check on the executed script and the generated list to see whether it is matching the given criteria.
Review panel members are experienced team members who check the criteria of list requests and its applications in the SQL script generated along with output and give the green light to provide the count and preview details to the requester. Review panel members complete the quality assurance (QA) and peer rating updates in GMSS portal once the review process is completed as shown below.
Pre - Approval Process
The ready-to-go lists - preview lists (in case of email) or contact lists (in case of phone or postal contacts) - will be uploaded in the portal under the respective list request for requester's approval.
Post - Approval Process
Final list for each campaign type is different. Final postal contacts are directly uploaded in portal or in Oradocs workspace created depending on the list size.
Internal Phone Lists are provided to the marketers either for Sales Team to upload as leads to Oracle Sales Cloud for sales campaigns or for the external tele sales / tele marketing vendors through Oradocs workspace with folders created.
In case of internal email lists, requester verifies the preview list generated and approves to proceed with the email lists for final list launch in Eloqua (Oracle's marketing automation tool) by changing the request status to Approved. Final lists for emails are created using the Shared List Application Tool or in standard Excel format and uploaded in Eloqua for launch. The list details of the final list along with its campaign and segment details are sent to the Demand Marketing team copying the mail to all stakeholders of the request.
After each list request's approval and final list upload, the list requests are closed by changing the request status to Closed which ends the list life cycle.
Related Topics
Nailed it?
If yes, click below to confirm completion of this topic.
Yes, I have understood this topic well
