Omeda stores Demographics, Deployment Types, and Products in your database as defined values to keep data clean. When bringing data in, it is important that the incoming data matches these designated values. Thankfully, Zapier has created a data mapping action called, “Formatter by Zapier”, that allows you to take the incoming Demographic, Deployment Type, Product responses from your connected app and map to the designated Omeda value so your data stays consistent and clean.

If you plan on passing Demographics, Products, and/or Deployment Types to the Add Customer Omeda Action and the Omeda values are not already mapped in the Trigger app, you will need to either have the values mapped properly in the Input created by Omeda Support or you can use this Formatter by Zapier action.

To obtain all the Omeda demographic response IDs to use in the Formatter by Zapier action:

1. Log in to Omeda
2. Navigate to My Omeda in the navigation menu
3. Select the Toolbox tab
4. Click on the Export Demographic Dump option. This will send an excel sheet to your email address with all demographic IDs and response IDs which you can use to map in the Formatter by Zapier action.
   Important: When mapping your trigger response values to the omeda response IDs, make sure you’re using the IDs found under the value_id column in the Export Demographic Dump sheet.

For Products and Deployment Types, use “1” for Yes/Opt-in and “0” for No/Opt-out.

To start, you’ll have to first create and test the Trigger. The Formatter by Zapier action should follow the Trigger, before the Omeda Add Customer action.

1. After creating and testing the Trigger, in the Create Action step, search and select the Formatter by Zapier action.
2. In the Event dropdown, select the Utilities option.
   
3. Select the Continue button.
4. In the Transform dropdown, select the Lookup Table option.
   
5. In the Lookup Key search box, search for the Demographic, Product, or Deployment Type coming from the Trigger you wish to map Omeda values to.
   
6. In the Lookup Table, the first column is where you enter the incoming text from the Trigger app. The second column should be where you map the Omeda Values to the incoming text.
   
7. (Optional) Add a Fallback Value if you want to default the field if no response is selected.
8. Test the action. Based on the incoming text from the Trigger, you should see the mapped Omeda Value in the Output.
   
9. To map additional values, follow the same steps starting with Step 1.