Datalist
Datalist is a named identity to capture, store, and map the data against a particular list. Data is ingested into FH CDP in various bases via XLS, CSP, etc., and they connect to different DB sources, as well as there are some pipelines set up to get the data from enterprise warehouse or S3 locations from different sources. When the data ingested into FH CDP all the records are mapped against a particular data list.
How to Ingest Data or a Customer can Come to FH CDP
Whenever customers are ingesting any data into the system, FH tags that data with a tag name as default. Once the data has been tagged, it is stored against a particular user and mapped. There is no limitation to tagging. There are multiple ways FH gets data, batch process and store into particular account. Every client has an account inside FH. They can create some account users & define roles inside that account. They just need to upload the data into FH.
Clients have different data from multiple sources – be it the CRM, third-party, and lot of data residing from different sources, and they have a single platform, where all the data can be ingested. They can see what a customer is doing. FH has created a lot of pipelines to map these data.
For example: If FH is collecting data from the social media. Clients have Facebook business page, once they set up credentials for accessing that Facebook page, FH has batch process to pull the data from social media and store into FH. It is an automated process. FH store stores these data and does the tagging on behalf of the client. For that we have created an application that needs permission from the client side to pull the data from the social media and ingest into FH.
Some of the customers’ data reside in the phases. They need to upload into FTP or S3 location on a daily basis. It also includes the historical data. FH has set up a pipeline to get these data in their format and translate into its own format and ingest the data in FH. The people liked their post, shared, or commented. Using this information, it performs sentimental analysis of that particular post later on as well. Name and image are stored inside FH.
FTP and S3 are not DIY mode, based on client request we do the set up. What are the fields, unique identifier, and data they are going to share with us. We align with the customers to share the historical data, then upload into the system phase wise by adding whatever implemental data they have on a daily basis in multiple formats that includes, text, PSV, CSV, etc., these are the end-points ingested into FH.
After creating the Datalist, FH import these data. Every data inserted has a data list name. Datalist is mapped with the FH schema. Every datalist has a different tag.
How to Store the Data and Where
Every data that is ingested into FH inserted into a particular field or column. For that FH has pre-defined set of fields (around 40 – 70), default for each account such as:
- First name
- Last name
- Location
- Phone no, etc.
Using these fields, you can map and store data inside FH:
Step 1: Create a data list
Step 2: Upload multiple times same data or different data on a daily basis
You see locations tags against a particular data list, like how many times it is uploaded, who are the proper users, and the tags associated to them. Every data that is ingested into FH is the user only. If a customer would like to add any additional information, then FH map the data against the users.
How FH Platform Does This?
When any master data is uploaded, all the transactions mapping is done against a particular user.
Why Datalist is Important
If a client wants to run any marketing campaign or share data with third-party, they can choose from the data list and send the communication. You can upload multiple data with same tag name. For filtering the users, FH is giving customer segmentation tool. Users can come here and do segmentation. For that segment they can send communication. There are two major tables, where data is uploaded.
- User Master
- User Details
For every account, a table is created. We physically create different tables for each account. For one account, User Master Entry is there, it is stored in the particular table only. User Master and User Details is the two main tables to collect all the data inside FH. Apart from that it has a number of tables as well. Any data that which is ingested into FH is stored in the User Master and User Details table.
At the time of creating a user FH define these two identities:
- Channel ID (User-Unique-Id): Define each interaction, from a single channel. One channel ID for one user. The Channel-ID is unique across the User Master. No duplicates. Channel Id is for channels plus users.
- Enterprise ID (Unique Identity): For different Nomenclature it is used. If it is a Facebook, for a particular ID, FH creates one user, this user data gathered from different stages. A single user may like five different posts at the same time. Same user information gathered from different channels or sources ingested into User Master multiple times. To identify a single user, FH using Enterprise ID or FH-ID (128-bit UIB).