Retailers will need to configure their network access settings to allow Connexity related domains and IP addresses for our integrations to function. In most cases where retailers installed pixels that are not firing, it’s likely that your system is actively blocking our domains and IP addresses for security reasons. Below you will find what function is enabled for each access list and the domains and IPs required. Please add these before launching your campaigns with Connexity.
*Note* For each use case, include all domains and IP addresses; Dynamic Product Ads IP addresses are required if you are planning to run Dynamic Product Ads.
For the Ecommerce Tracking Pixel
If your site implements a Content Security Policy (CSP), you will need to ensure the following domains are defined in your “Content-Security-Policy” meta tag:
- js.cnnx.link - Used to download Connexity Event API JavaScript
- www.bizrate.com - Used for Connexity conversion event tracking
- rr.bizrate.com - Used for Connexity conversion event tracking
- cdn.taboola.com - Used to download Taboola Event Tracking API JavaScript
- trc-events.taboola.com - Used for Taboola event tracking
- trc.taboola.com - Used for Taboola event tracking
For Images, Feeds, and Source-of-Truth Reports
The below IPs need to be allowed in order for our CDN to cache merchant product images, to fetch feeds, and sales reports.
- 104.197.177.57/32
- 34.28.60.226/32
- 34.170.10.182/32
- 34.76.225.210/32
- 192.138.218.0/23
- 64.19.224.0/20
- 2001:550:a07::/48
For Dynamic Product Ads
The below IPs need to be allowed to run Dynamic Product Ads/DPA campaigns.
- 185.106.32.0/24
- 185.106.33.0/24
- 185.106.34.0/24
- 185.106.35.0/24
- 141.226.226.0/24