Data format should be in CSV format.

The file should contain all the customer transactions that occurred between a time period and should have below fields for one transaction (one row).

<aside> 📌 Sample file can be reached here for store sales feed

</aside>

Data Format

Make sure column header naming matches with fields mentioned here.

Each row includes information related to the customer transactions you want to upload, such as email address, phone number, and name.

Some customer transaction information needs to be hashed using the SHA-256 algorithm, which includes:

• Customer email addresses
• Customer phone numbers
• Customer first and last name
• Customer gender

Other customer transaction data, such as the country of residence, zip codes, and attribute data, doesn’t need to be hashed.

Below are the column headers you can add to the header row for customer transaction information along with the formatting guidelines

• Remove any spaces in between the email address.
• All lowercase letters
• Can provide up to 3 email addresses per customer, which is separated into 3 “Email” columns | Strongly recommended | Y | > Examples before hashing
• [email protected]
• [email protected] | | First Name | - All lowercase letters
• Accents are allowed.
• Remove any unnecessary spaces before, after, and in between the names. | Optional | Y | > Examples before hashing
• şükran
• çağın
• mehmet ali
• renée
• marie-astrid | | Last Name | - All lowercase letters
• Accents are allowed
• Remove any unnecessary spaces before, after, and in between the names. | Optional | Y | > Examples before hashing
• yılmaz
• şahin yıldız
• o'calloway
• cox-cohen | | Gender | Gender in the form of an initial in lowercase
• “f” for female
• “m” for male | Optional | Y | > Examples before hashing
• f
• m | | City | - All lowercase letters
• Accents are allowed. | Optional | N | - istanbul
• new york city
• paris
• munich | | State | - All lowercase letters (Exception: 2-letter abbreviated state names for the US)
• May stand for district (ilçe) for Turkey | Optional | N | > Türkiye
• şişli
• çankaya

Others

• CA
• california
• new york
• maharastra | | Zip | > US zip codes and international postal codes are allowed.

For all countries other than US:

• Don’t include postal code extensions.

For the US:

• 5-digit zip codes are allowed.
• 5 digits followed by 4-digit extension are also allowed and can improve your match rate. | Optional | N | > Türkiye
• 06420
• 34387

Other country examples

• 94109
• 94109-1234
• W1J 0BH | | Country | - Use ISO two-letter country codes.
• Include the country code even if all of your customer data is from the same country | Required | N | - TR
• US
• DE
• JP | | Phone Number | - Phone numbers should be formatted according to the E.164 standard and include the "+" prefix, followed by the country code and the subscriber number. This can include a national destination code or an area code.
• Can provide up to 3 phone numbers per customer, which is separated into 3 “Phone Number” columns | Strongly recommended | Y | > Examples before hashing
• +905551112233
• +12038271234
• +442071838750 | | Conversion Name | - The name of the conversion action that you’d like to import
• Should be “Store Sales” | Required | N | - Store Sales
• SS_customer_purchases | | Conversion Time | Valid date string in form of yyyy-MM-dd HH:mm:ss+z yyyy-MM-ddTHH:mm:ss[±hhmm]
• Replace “+z” with the GMT offset by indicating “+” or “-” and then the 4-digit time difference. | Required | N | > yyyy-MM-dd HH:mm:ss+z "2023-08-14 13:00:00+0500”

yyyy-MM-ddTHH:mm:ss+z "2023-08-14T13:00:00-0100” | | Conversion Value | - A number representing the value that you place on the conversion (Value of the order or items sold.)

• Only positive numbers are accepted (integer or decimal)

• Should not contain any currency symbols, special characters, letters, or commas | Required | N | - 100

• 99.90

• 1250.00 | | Conversion Currency | - The currency in which your conversion value is provided

• Use this column if you report conversion values in more than one currency, or you have multiple customer accounts that are billed in different currencies

• Use 3-character ISO 4217 currency codes | Required | N | - TRY

• USD

• EUR | | Order Id | - Unique identifier for each transaction or order in an offline event set. For example, for retail this can be a receipt ID. | Optional | N | - ATN10001

• 123456 | | Store Code | - Store code (ERP) of the location that the conversion is occurred | Optional | N | - A1234

• Shop77 | | Contents | Relevant products in an event (transaction or order) with product information. See below | Optional | N | | | Contents_ID_# | Unique ID of the product that can be matched with GMC product feed or Meta Commerce product feed | Conditionally Required | N | - product123

• 3PRDCT900123 | | Contents_Quantity_# | The quantity of the item sold | Conditionally Required | N | - 1

• 10 | | Contents_Price_# | The price of the item sold

• It specifies the price for a single item - For example, if you have two same items sold for ten dollars each, the price parameter would be 10.00 and the quantity parameter would be 2 | Conditionally Required | N | - 100

• 99.90 | | Contents_Category_# | Category of the product item | Optional | N | | | Contents_Brand_# | Brand name of the product item | Optional | N | |

<aside> 📌 Sample CSV files for store sales feed can be reached below 👇🏻

</aside>

<aside> 💡 A non-hashed form is included for debugging purposes, which is not the one we ask for. Hashed form is the required version for submission.

</aside>

single-non-hashed.csv

single-hashed.csv

<aside> 💡 Below are the formats with optional order fields such as product sold and store code, user gender fields. Notice the number changes in column names such as Contents_Quantity_1, Contents_Quantity_2

</aside>

non-hashed-all-fields.csv

hashed-all-fields.csv