Using ZAP Events in Ometria

There are three primary uses for ZAP POST events in Ometria. 1. Segmentation - You can use ZAP POST events and their respective properties to filter customers for segmentation. This could be Customers who who scanned a QR code in the last 30 days could be included in an 'Engaged Customers' segment. 2. Reporting - You can use ZAP POST events and their respective properties to filter customers or actions in a report, for example orders from customers who have received a ZAP in the last 3 months. 3. Automated Campaigns - You can use automated campaigns to target customers who have been rejected or returned from a send in the last 3 months so you can target them via an email campaign.

In order to have access to the ZAP POST events in your Ometria account you'll need to ask your Ometria account manager to enable the "ZAP~POST Custom Events Models".

Customer Segmentation

Here you can see we're filtering for customers who have ever had a ZAP Sent event fire.

You can then save this as a static or dynamic segment for further use in Ometria campaigns and reports.

Reporting

Using the normal data filters available for customer segmentation in Ometria, users can configure static or dynamic segments based on the ZAP POST events available in the platform. In this example we'll create a report to see orders from anyone who has scanned a QR Code on a ZAP in the last 6 weeks. 1. Start by selecting the Orders report option in the report creation screen.

Scroll down to the custom filters controls

If you're using an existing segment then select the segment in the available dropdownlist.

If you're building a new segment from scratch select the customer filters and then custom events in the condition options to find the appropriate event for your use case.