# Zapier (/measurement/attribution-data/zapier) ## Overview [#overview] The LettrLabs app in Zapier has a **Send Purchase Event** action. A Zap with this action sends each sale from the apps you use, such as your CRM or your store, to LettrLabs. LettrLabs then compares each sale with the mail you sent. You can use Zapier to: * Send each new sale to LettrLabs, with no file to upload. * Count the sales of an app that has no native integration. * Send the value of the sale, so it counts in ROAS. The action sends each sale to the same conversions API that the [Send by the API](/measurement/attribution-data/api) page describes. The same rules apply to each sale. ## Before you begin [#before-you-begin] * Connect Zapier to LettrLabs, and copy the key. See [Connect Zapier](/integrations/zapier#connect-zapier). * Know the trigger in your app that marks a sale, for example a deal that is closed won, or a new paid order. ## Send each sale with a Zap [#send-each-sale-with-a-zap] In Zapier, start a new Zap. As the trigger, pick the app and the event that marks a sale. As the action, pick the **LettrLabs** app, then **Send Purchase Event**. When Zapier asks you to sign in to LettrLabs, paste your key. Map **total\_amount** to the value of the sale. This field is required. Map one identifier of the customer: the address, the email, the phone number or the discount code. See [What a sale must hold](#what-a-sale-must-hold). Optional: Map **event\_date** to the date of the sale, and the name of the customer. Test the action, then publish the Zap. You're done when the test sale shows in **Attribution Data**. Open the **CSV Upload** tab, then **CSV Uploads**. In **All sources**, select **API**, and find the newest batch. The sale also shows on the **API / Zapier** tab, under **Attribution Records**. ## What a sale must hold [#what-a-sale-must-hold] The action has the fields of the conversions API. The table lists the main fields. | Field | What to map | | ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | **total\_amount** | The value of the sale. Required. | | **full\_address\_primary**, or **address1\_primary**, **city\_primary**, **state\_primary** and **zip\_primary** | The address of the customer. An address in parts needs all four fields. | | **email\_primary**, **phone\_number\_primary** or **coupon\_code** | An identifier, when the sale has no address. | | **event\_date** | The date of the sale. An empty date reads as the time of the Zap run. | | **first\_name**, **last\_name**, **full\_name** or **business\_name** | The name of the customer. | | **order\_id**, **customer\_id**, **store\_id**, **unique\_id**, **crm\_id** | Your own ids, to find the sale later. | Each sale must hold one identifier. An email or a phone number in the wrong format makes LettrLabs refuse the sale. Leave a field empty when you do not have a correct value. ## FAQ [#faq] Open the **CSV Uploads** tab, and select **API** in **All sources**. Open the newest batch, and read **Rejected rows**. A sale with no identifier, or with a bad email, is refused. See [What a sale must hold](#what-a-sale-must-hold). Any active key of your account. Use the key that **Connect Zapier** made, or create one on **Integrations** > **API keys**. See [Send by the API](/measurement/attribution-data/api#create-an-api-key). Use two actions. **Add Recipients to Integration Order** adds people to mail. **Send Purchase Event** sends a sale. See [Zapier](/integrations/zapier) for the mail actions. ## Related [#related]