# Results
If you're sharing transactional data with the platform, the Results page will show a detailed attribution analysis divided by each creative mailed. See our [Transactions](/platform-basics/transactional-data.md) documentation on how to share Order data with the platform and read your attribution reports.
If the campaign has been in-home for the 30-90 day attribution window, this section breaks down campaign's success and is especially useful if comparing against a holdout group or A/B testing different creatives.
Visible attribution metrics can be adjusted using the columns filter to the right. Descriptions of each metric appear when hovering your mouse over the information circle. Use the **Matchback View** to adjust the dashboard to **First Time Orders.**
{% hint style="info" %}
Metrics for First Time Orders can only be calculated if you're passing "new\_buyer" as true/false under your order "metadata." If you have the [Poplar Shopify App](/integrations/supported-platforms/shopify.md) installed, this data is passed automatically.
{% endhint %}
## **Download Raw Matches**
A record of raw matches can be downloaded can be downloaded on a campaign and account-wide level. Poplar reporting follows a last-touch attribution model across campaigns, so it could be that the mail piece was not the last one that the specific customer received. Use the **order\_id** column to trace an attribution back to a specific order.
### **Data Key**
Below is a guide to the columns you will receive in your CSV download:
| **match\_id** | ID unique to that match |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **campaign\_id** | ID of the campaign |
| **campaign\_name** | Name of campaign |
| **campaign\_type** | Type of Campaign (Poplar, Shared, Solo, etc.) |
| **creative\_id** | Unique ID for the creative that matched |
| **mh\_id** | Unique ID of the mailing/holdout record that matched |
| **external\_order\_id** | External order ID for the match |
| **customer\_id** | External Customer ID for the match/order |
| **order\_date** | Date the order was placed |
| **order\_total** | Total amount of the order |
| **cost\_per\_piece** | Cost of the individual mailer |
| **status** | Mailed or holdout |
| **send\_date** | Date the mailer was launched |
| **attribution\_start\_date** | Date the first mailing was delivered, used as the in-home date for attribution |
| **envelope\_type** | Type of envelope, applicable to shared mail campaigns only |
| **test\_cell** | Grouping of mailings, only used in certain cases |
| **customer\_first\_order\_within\_campaign** | True/False based on if it is this customer IDs first order attributed to this campaign |
| **is\_first\_time\_order** | True/False based on if this order is considered a New Buyer |
| **id\_match** | True/False based on if this order matched on Customer ID between mailing list and transaction file |
| **email\_match** | True/False based on if this order matched on email between mailing list and transaction file |
| **bill\_match** | True/False based on if this order matched on billing address between mailing list and transaction file |
| **ship\_match** | True/False based on if this order matched on shipping address between mailing list and transaction file |
| **manual\_send\_id** | ID of the manual send in Poplar |
| **manual\_send\_name** | Name of the manual send in Poplar |
| **metadata** | Any metadata from that order |
---
# Agent Instructions: 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:
```
GET https://docs.heypoplar.com/getting-started/campaign-setup/results.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.