Skip to main content

Optimove IPs to Allow

Natalie Samuels
  • Updated

To ensure seamless communication between Optimove and your environment, it is necessary to allowlist specific IP addresses. This section provides the required IP addresses for different functionalities within Optimove. Please allow these IPs according to your environment configuration.

If you have any questions or require further assistance regarding IP allowlisting or integrating with Optimove, please consult the documentation or reach out to our support team.

ETL Process - Batch Data

For Optimove's ETL (Extract, Transform, Load) process, customers need to whitelist the following IP addresses. These IPs are associated with Optimove's main ETL tool.
US:
  • 34.86.122.69
  • 35.202.1.14
EU:
  • 34.159.11.103
  • 35.233.102.48
Pre-production:
  • 34.150.185.150

Legacy Systems

This section lists IPs for our legacy infrastructure. These IPs are used for 'Non-Optidata ETL' processes and also send some API notifications, webhooks, and legacy engager (channel) communications. 

 
US:
  • 35.245.236.141
  • 34.145.132.59
  • 34.145.232.78
EU:
  • 34.159.94.86
  • 35.242.197.153
  • 34.159.242.247

Optimove Personalize and Data Connections

If you are using Optimove Personalize or setting up an API-based Data Connection and have firewall rules with IP address restrictions, you must allowlist the following IP addresses. This ensures that Optimove can successfully connect to your API endpoints.

  • 108.129.6.43
  • 46.137.111.133
  • 99.81.4.55

Webhooks and Callback URL

Important: The IPs listed below cover our primary webhook services. However, some notifications may still originate from our legacy systems. To ensure complete coverage, please also whitelist the IPs in the “Legacy Systems” section relevant to your region.
 

API, Listeners (Callback URL), Webhook Integrations, Conditional Execution, Promo Integration

Functionalities that communicate over a callback URL—such as API callbacks, webhook integrations, conditional execution, and promo integrations—require whitelisting Optimove’s notification IP addresses to ensure successful delivery of webhook notifications.

Examples of services using these include:

  1. API calls using a callback URL, such as:
    1. AddCustomerAttribute
    2. UpdateCustomerAttributes
  2. Webhook integration (Opti-gration) for campaigns that export data to external buckets and notify via callback URLs.
  3. Conditional execution or promo integrations involving internal systems communicating with Optimove via webhook notifications.
US:
  • 35.199.60.237
  • 35.221.56.26
  • 35.221.33.157
  • 34.86.85.20
  • 35.221.48.107
EU:
  • 35.242.199.57
  • 35.198.188.17
  • 34.107.29.24
  • 35.246.154.200
  • 34.107.86.58

Real-Time Triggers (formerly Track & Trigger)

Using the Real-Time Triggers (formerly Track & Trigger) functionality involves event listeners and third-party integrations with Optihub engagers.

Current IP Addresses

US:

  • 34.70.245.229
  • 34.122.196.101
  • 34.71.252.19

EU:

  • 35.189.243.236
  • 192.158.28.169
  • 35.195.171.164

3rd Party Integrations

3rd party integrations apply to any of the following channels:

  • Klaviyo
  • SFMS-SMS
  • SFMC-SFTP
  • CheetahMail
  • Leanplum
  • Braze - Scheduled Push
  • Braze - Scheduled Email
  • Braze - Realtime Push
  • Braze - Realtime Email
  • Klaviyo Outdoor
  • Klaviyo Audience
  • Airship
  • IDT-SMS
  • IDT-IVR
  • Adobe Campaign
  • DMP
  • Promot-only
  • Google Customer Match

US:

  • 34.70.245.229
  • 34.122.196.101
  • 34.71.252.19

EU:

  • 35.189.243.236
  • 192.158.28.169
  • 35.195.171.164

For any custom channel or integration developed by Optimove per request, please contact our support team.

Related articles