> For the complete documentation index, see [llms.txt](https://docs.heypoplar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heypoplar.com/platform-basics/transactional-data/csv-upload.md). # CSV Upload Measuring the impact of your direct mail campaigns can easily be done from inside the platform. We recommend waiting 30-90 days after your campaign's in-home date to see the full scope of success accurately reflected in the numbers.

A CSV record of your order data can be uploaded to the [Transactions](https://app.heypoplar.com/transaction) page of your account. Records can be uploaded more than once, without having duplicates - the platform will ignore duplicates and update any changes to existing orders by **order\_id.** The maximum file size is 20MB so if your uploading large amounts of order data, we recommend splitting the CSV and uploading separately. ## **Required Data** To run attribution reports the platform requires (at minimum) **order\_id, order\_date, shipping address OR billing address and order\_amount** to calculate revenue related metrics. For campaigns that mailed using emails for Address Enrichment, we accept **email OR hashed\_email** to match against as well.

Column Header	Required	Description
order_id	Y	A unique identifier for each order
order_date	Y	YYYY-MM-DD Must be an ISO8601 formatted date representing the date and/or time of purchase
order_amount	Y/N	Required to calculate Revenue and related metrics (CPO, ROAS, etc.), must represent the total order value in decimal form Optional for use cases that don't require revenue tracking (site sign-ups, app downloads, etc.)
customer_id	N	A unique identifier for the transacting customer in your e-commerce system
billing_name billing_address_1 billing_address_2 billing_city billing_state billing_postal_code	Y/N	Required if Shipping Address data is not provided Optional to include with Shipping Address data
shipping_name shipping_address_1 shipping_address_2 shipping_city shipping_state shipping_postal_code	Y/N	Required if Billing Address data is not provided Optional to include with Billing Address data
email	N	Can be used to match against campaigns that mailed using emails for Address Enrichment This data is not stored by Poplar, it is used to compute a hash and then discarded
hashed_email	N	The SHA256 has of the customer's email address as a 64 character string Please convert the value of the email address to lowercase prior to hashing
metadata	N	Additional order details such as items purchased or New Buyer tags
currency_code	N	Three character ISO country-code - if not provided will default to USD

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.heypoplar.com/platform-basics/transactional-data/csv-upload.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.