Syncing Customer Data Via File

CitrusAd currently only support TSV format for Customer data. The table below describes the names of columns in a TSV file and their descriptions. For customer data, only “customer_id” is a required column.

Column names and descriptions for customer data in TSV files

Column name

Required?

Datatype

Description

customer_id

Required

Text

This is the identify of the customer in the system of retailer.

year_of_birth

Optional

Number

This is the year of the birthday of the customer. This must be a number.

gender

Optional

Text

This is the gender of the customer. If the value is provided, it must be one of the values {“UNDEFINED”, “FEMALE”, “MALE”, “OTHER”}.

The value is case-insensitive.

postcode

Optional

Number

This is the postcode of the contact address of the customer

suburb

Optional

Text

This is the suburb of the contact address of the customer

target_data

Optional

Json array

If the value is provided, it must be a json array.

For example:

[“customer_type:corporate”, “customer_country:Australia”]

customer_targeting:KEY

Optional

Text

If this type of column is used, retailers must provide a value for KEY.

For example: The column name could be “customer_targeting:customer_type” and the value of a cell in the column can be “corporate”, “smb” or “retailer”.

There could be several columns with this syntax in a TSV file.

An example of a TSV file for customers can be seen in the table below. We note that the raw data is a text file but it is represented in a table so that we can read easily.

An example with a heading row and three data rows in a TSV file for customers

customer_id

year_of_birth

gender

postcode

suburb

customer_targeting:customer_type

0937832

1990

MALE

3000

Melbourne

0347293

1993

FEMALE

4000

Brisbane

0293423

OTHER

4064

Milton

Corporate