When you import a dataset to the InfoSum Platform, you will be provided a range of tools to normalise the data and map it into our global schema.
As best practice InfoSum recommends that data is prepared on the premise of one row per person and any associated attributes in individual columns tied to that row. Similar to the table below.
Having descriptive column names - in particular for any customer identifiers - will make this a smoother process.
The table below outlines the identifiers commonly used in the Platform. During the normalisation process, these identifiers are converted into keys, which are used to match rows in a query. Keys can be both deterministically (e.g. Email) and probabilistically (e.g. Full name and DOB) matched during a query.
Using these column names below will help the Platform to understand the meaning of your identifiers.
|Data type||Column name||Guidelines||Examples|
|Email Address||Most international email address formats can be firstname.lastname@example.org
Mobile Phone Number
Home Phone Number
|Both mobile and home phone numbers can be imported in separate columns.||07812345678
+44 1397 123456
|Name can either be formatted in separate or a single column. Forename and Surname should be separated into individual columns||Duncan
|Age||Date of Birth
|Age can be formatted as a DOB or a numerical value - or both. In the case of DOB, each data point should be split into individual columns. i.e 1 Column for YYYY, 1 Column for MM, 1 Column for DD||YYYY-MM-DD
|A range of address columns can be imported, ideally including UDPRN. Each datapoint should also be split into individual columns. I.e. Street in one column, Town in another Column, etc||1 The Street,
|Mobile Advertising ID||Mobile Advertising ID (e.g. AAID, IDFA)||Both Android's Advertising ID (AAID) and Apple's Advertising Identifier (IDFA) can be used.||
|Social Media||Social Media: Twitter Handle
Social Media: Facebook ID
|Identifiers from most social media platforms can be used.||@therecanbeonlyone