We consider image templates to be a crucial feature to ensure your success on ROI Hunter. When you apply an image template using Template Editor, original image links in your catalog will be replaced with ones that ROI Hunter creates for you. This triggers Meta to start fetching them automatically.

The template-enhanced images are generated on demand. This means that we do not store all your product images with the template in advance. When we receive the request for an image from Meta, we download your source image, apply the template, and send the result back to Meta.

When any change affecting your image occurs (e.g.: Changes to Product Price, Product Image etc.), we generate a new image link. This triggers Meta to automatically fetch the new image.

Technically, when the image is supposed to change (new template applied, scheduled change, price update etc.), ROI Hunter needs to re-process your product feed (replace image URLs) and send it to Meta. Meta needs to update all products and start fetching new product images. As all this takes some time, please expect delays when updating the images.

For smaller feeds with up to dozens of thousands of products, the new template should start appearing in up to one hour. For bigger feeds, expect even longer delay.

If you are using Catalog Batch API integration, we start sending updated image URLs to Facebook immediately, so first products with the template start appearing faster. But the more products need to be updated, the longer it takes to have fresh images available. For catalogs with millions of products, please also expect hours of delay.

Important note - for smooth image updates, all the following requirements need to be met.

To ensure that Meta always has images with the most recent product data, you should make sure to meet the following requirements. ROI Hunter currently does not report image processing issues, so potential issues might be hidden. Therefore, the following requirements are critical for seamless image processing.

As mentioned above, please expect higher traffic of image download requests from ROI Hunter. Especially for big catalogs with additional images, the traffic can be huge, especially during the early stages of onboarding into ROI Hunter. The server hosting these images should be able to handle the high traffic load. Also, the internet connection should be stable and fast to avoid time-outs.

To be able to process these images, we need to have access to download your images without any blocking or limitation. Some servers automatically start blocking sources of high traffic to protect themselves from overloading. In these cases, you might not even be aware that our requests are being blocked by your servers.

All our image requests have a user agent in their headers set to “ROI Hunter/Media Downloader; http://www.roihunter.com/”. They come from our proxy servers with the following IP addresses:

You can see our requests coming also from other IP addresses. This happens when the first download request via proxy fails and the retry request is sent directly from the server that is processing the image.

If you want to keep your server protected but want to have your images processed correctly, we request that you or your IT team whitelist both our user agent and the specific IP addresses.

When Meta receives new images, they don’t fetch them all from us immediately. Their system is waiting for an event signal received for the specific product. When your product is visited or added to the cart, the product image will probably be needed for the ad. As a result, Meta ensures that they will have images for the most popular products first.

This process requires proper tracking of the traffic on your website and in your mobile app. If you want to have the image fetched by Meta properly, make sure that the tracking is implemented and that the correct product or group IDs are tracked. More details about the tracking can be found in Meta’s documentation about Dynamic Audiences.

As a result of the process described in this article, there could be a delay between applying a new image template and those changes reflecting on your ad previews. In Meta Commerce Manager, you can see old images even several days after applying the new template - especially for products that are not visited often. From our experience, Facebook Ad Library is not relevant for checking the images at all.

If you believe there is anything wrong with your images or you want to make sure that everything is processed correctly, you can contact our Support team via the chat button or via wehelp@roihunter.com.