Normalizing custom keys for BENELUX
Table of contents:
General formatting prior to upload
Normalisation on InfoSum platform
General formatting prior to upload
Value rules
- No upper cases allowed in the file. All data must be in lower case
- Spaces may be used only for last names
- Accented letters are allowed for first / last names: é/ è / ö / ù
- Special characters are to be removed such as “&”, “/”
- All empty data or column with missing values should have an empty cell (no data may be entered since e.g. using “blank” or “n.a.” or “-1”, might create a match)
Column name rules
Column names must be respected for the keys to be considered as common between databases:
- fullname_birthdate
- fullname_zipcode
- mobile
- bpost_address
Core keys - formatting guide
Key name |
Format |
Example |
fullname_birthdate: firstname_lastname_birthdate |
Keys must be separated with “_” in between values Birthdate must be written with 2 digits for days and months and 4 digits for years separated by “-“ If one of the values is missing, the cell must be left empty |
ellie_smith_01-02-2022 |
fullname_zipcode: firstname_lastname_zipcode |
Keys must be separated with “_” in between values Zipcode is always 4 digits If one of the values is missing, the cell must be left empty |
ellie_smith_3320 |
mobile: Mobile phone number |
mobile phone number in full numbers, without prefix or number separators |
0476024123 |
|
E-mail address without spaces and with @ |
ellie.smith@example.com |
bpost_address : zipcode_cityname_streetname_housenumber |
Keys must be separated with “_” in between values All address components must be normalized via bpost (we use an API connexion, but bpost can do a free one-shot normalization of your database) Note: Still an issue on box numbers which are difficult to normalize and when not used create false matches on apartment buildings using box numbers. |
2000_aalst_atominm_1 |
DPG BE formatting
DPG Media uses the following composite match keys for Belgium:
- firstname_lastname_birthdate = first name + last name + birth day + birth month + birth year
- firstname_lastname_zip = first name + last name + zipcode
- Address = zipcode of the ‘hoofdgemeente’ + street name + house number
These three keys result from concatenating the respective fields defined above, with each field separated by an underscore ('_'). All fields will be converted to lowercase for consistency. All fields must contain a non-null value to generate a valid composite key.
--------------------
Note 1: Birthdays and birth months are always formatted with two digits. Birth years are formatted with four digits. For example, 01-02-2022.
Note 2: Belgium's municipalities are divided into “hoofdgemeenten” (main municipalities) and “deelgemeenten” (sub-municipalities). For this purpose, we use the zip code of the “hoofdgemeente.” The following mapping table shows the difference between “deelgemeenten” and “hoofdgemeenten.”
We make one exception on this table for “Antwerpen”, for which we convert all zip codes with the municipality name “Antwerpen” to “2000”.
Note 3: Belgian street names are normalised using the Bpost Address Validation API, see Web services > Validatie.
Note 4: House number additions (e.g., letters or apartment numbers) are included in the house number field (e.g., ‘kerkstraat 4a’)
Keys examples
Firstname_last name_birthdate
First name |
Last Name |
Birth Day |
Birth Month |
Birth Year |
fname_lname_birthdate |
Patrick |
Janssens |
05 |
11 |
1994 |
patrick_janssens_05_11_1994 |
Griet |
De Groot |
01 |
02 |
2001 |
griet_de groot_01_02_2001 |
Elke |
Debast |
null |
null |
1968 |
null |
null |
Goossens |
18 |
12 |
1982 |
null |
Firstname_lastname_zip
First name |
Last Name |
Zipcode |
fname_lname_zipcode |
Patrick |
Janssens |
3000 |
patrick_janssens_3000 |
Griet |
De Groot |
9308 |
griet_de groot_9300 |
Elke |
Debast |
null |
null |
Ine |
null |
2018 |
null |
Address
Note that for the second record, the zipcode "9308" (deelgemeente) is converted to "9300" (hoofdgemeente). Also note that all fields are converted to lowercase, including the house number addition field.
Zip code |
Street name |
House number |
address |
2160 |
Sint-Damiaanstraat |
52A |
2160_sint-damiaanstraat_52a |
9308 |
Kortenhoekstraat |
4 |
9300_kortenhoekstraat_4 |
null |
Bondgenotenlaan |
6B |
null |
3000 |
Bondgenotenlaan |
null |
null |
DPG NL formatting
DPG Media uses the following composite match keys for The Netherlands: ●
- firstname_lastname_birthdate = first name + last name + birth day + birth month + birth year
- firstname_lastname_pc4 = first name + last name + pc4
- Address = pc6 + house number
These three keys result from concatenating the respective fields defined above, with each field separated by an underscore ('_'). All fields will be converted to lowercase for consistency. All fields must contain a non-null value to generate a valid composite key.
--------------------
Note: Birth days and birth months are always formatted to two digits. Birth years are formatted to four digits. E.g., 01-02-2022
Note 2: A PC6 is formatted such that there is no space between the letters and the digits, e.g., 3021AB
Note 3: House number additions (e.g., letters or apartment numbers) are included in the house number field (e.g., ‘kerkstraat 4a’)
Keys examples
Firstname_last name_birthdate
First name |
Last Name |
Birth Day |
Birth Month |
Birth Year |
fname_lname_birthdate |
Patrick |
Janssens |
05 |
11 |
1994 |
patrick_janssens_05_11_199 4 |
Griet |
De Groot |
01 |
02 |
2001 |
griet_de groot_01_02_2001 |
Elke |
Debast |
null |
null |
1968 |
null |
null |
Goossens |
18 |
12 |
1982 |
null |
firstname_lastname_zip
First name |
Last Name |
PC4 |
fname_lname_zipcode |
Patrick |
Janssens |
5012 |
patrick_janssens_5012 |
Griet |
De Groot |
3021 |
griet_de groot_3021 |
Elke |
Debast |
null |
null |
Ine |
null |
6462 |
null |
Address
PC6 |
House number |
address |
5012AB |
52A |
5012ab_52a |
3021DC |
4 |
3021dc_4 |
null |
6B |
null |
6462CJ |
null |
null |
Normalization on InfoSum platform
When normalizing data on the InfoSum platform, please follow our Normalization how-to documentation.
Here's an example of what the above keys will look like on the normalization tool:
Name (case sensitive) |
InfoSum type |
Set-up |
|
Native key |
Lowercase email field |
Mobile Phone Number |
Native key |
Mobile phone |
bpost_address |
Custom key* |
Lowercase fields of house_number + street + city + postal_code |
fullname_birthdate |
Custom key* |
Lowercase fields of first_name + last_name + birth_day + birth_month + birth_year |
fullname_zip |
Custom key* |
Lowercase fields of first_name + last_name + postal_code |
lastname_birthdate_zip
|
Custom key * |
Lowercase fields of last_name + birth_day + birth_month + birth_year + postal_code |