Sync user events and historical orders

  • Updated

This feature is currently in beta. Contact your Customer Success Manager or sign up for the beta on Optimizely.com.

After you integrate Optimizely Data Platform (ODP) to enable Commerce Search v3, you must create integration jobs to sync user events and historical orders to Google Retail Search.

Historical User Events Sync job

Create

Create an integration job with UserEventSync as the Post Processor.

Historial User Events Sync.png

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

Historical - Start Date.png

Historical - End Date.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

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

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 Historical User Events Sync job for that specific period.

Schedule Daily Sync.png

User events consent

Tracking data is stored in ODP and synced to Google Retail Search. Consider it for your production environments.