---
title: User events sync
slug: configured-commerce/docs/user-events-sync
docTags: 
createdAt: 2026-08-05T19:35:40.000Z
---

After you integrate Optimizely Data Platform (ODP) to enable Commerce Search v3, you must create integration jobs to sync user events and historical orders from ODP to Google Cloud Vertex AI Search for Commerce. The following user events are mapped from ODP and synced to the Vertex AI.

| **ODP event type** | **ODP action**     | **Vertex AI search event type** |
| ------------------ | ------------------ | ------------------------------- |
| product            | add\_to\_cart      | add-to-cart                     |
| product            | remove\_from\_cart | remove-from-cart                |
| product            | detail             | detail-page-view                |
| page\_view         | category           | category-page-view              |
| page\_view         | cart               | shopping-cart-page-view         |
| page\_view         | website            | home-page-view                  |
| navigation         | search             | search                          |
| navigation         | sort               | search                          |
| navigation         | filter             | search                          |
| navigation         | autocomplete       | search                          |
| order              | purchase           | purchase-complete               |

## User events consent

Tracking data collected in ODP is synced to Google Cloud Vertex AI Search for Commerce to feed machine learning models to make search smarter and more personalized. For production environments, ensure your privacy statement reflects this integration and confirms that user event data may be shared with third-party services like Google. You should review internal compliance and legal requirements related to data sharing and update consent language accordingly.

## Historical User Events Sync job

### Create

Create an integration job with **UserEventSync** as the **Post Processor**.

![Historial User Events Sync.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/M9fg4ILNiya-9h9LnTOuq-20260720-144509.png)

Configure any necessary notifications, and create two parameters named **StartDate** and **EndDate **with a **ValueType** of **SpecificDateTime**.

![Historical - Start Date.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/wRPu5PWuuCyAIiRDw1-d6-20260720-144509.png)

![Historical - End Date.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/qHaAr5ViD7RFJRuFGVJ6N-20260720-144509.png)

### Run

Schedule and run a one-time Historical User Events Sync job, setting a start date and end date. Verify that the job runs successfully and the historical events, especially orders, are synced from ODP to Google Cloud Vertex AI Search for Commerce. Depending on the length of the purchase history to sync, the start date and end date can be adjusted. You should sync the last three to five years of orders.

![Schedule job.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/faAKaXjcdzInEGUDitOFp-20260720-144509.png)

## Daily User Events Sync job

### Create

Create an integration job with UserEventSync as the Post Processor. Configure any necessary notifications.

![Daily User Events Sync.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/pJ3ktemYYVp3TxawPBZ8q-20260720-144509.png)

### Run

Schedule the Daily User Events Sync job to run at a specific time each day, preferably during the early morning hours. Monitor the job to ensure it runs successfully at the scheduled time each day. If any jobs fail during a certain period, contact Optimizely for support to determine the root cause. Once the issue is resolved, run a one-time Historical User Events Sync job for that specific period.

![Schedule Daily Sync.png](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/BSGPyvzWhydHzsDV0W9xS-20260720-144509.png)