⚠️ We are currently working to expand and improve the Knowledge Base. If you can't find the article you are looking for in the list, try the search function ⚠️

Smartly.io template asset fetching and our source IP addresses

  • Last update:

What should I do if Smartly.io cannot fetch assets used in a template? 

If Smartly.io is having issues fetching your images or videos from your company's server, or other video storage (dropbox, google drive) you should verify that Smartly.io is not being blocked or limited temporarily. Additionally, you should check that the assets are publicly accessible for Smartly if using cloud storage (such as dropbox, google drive). You may need to ask your IT team to allow Smartly.io unlimited access from our source IP addresses.

Note: If your server implements filtering based on an HTTP-request header, the User-Agent request header containing "Smartly.io" should be allowed. 

Our source IP address ranges for allow listing

  • 116.202.65.160/27
  • 116.202.68.32/27

Note: The above addresses are what are known as Classless Inter-Domain Routing (CIDR) blocks and are not simply two IPv4 addresses. Most systems should be able to accommodate CIDR notation. However, if you have a system that doesn't, you can visualize the ranges here.

What are source IP addresses?

The operation of various parts of our automation platform requires Smartly.io to fetch images, videos and feeds using links supplied by our customers.

For some customers, handling our requests for assets represents a substantial proportion of their internet traffic. For example, we might fetch 500,000 product catalog images from customer links. We share source IP addresses with our customers so that they can distinguish between traffic from Smartly.io and traffic from customers, search engines, partners, and potentially bad actors. Customers should also note that Smartly fetches assets from Germany in Europe.

Meta requests can cause high levels of requests to customer assets

We try to fetch assets as quickly as our partners request them from us to maximize advertising performance. Some of our customers with large numbers of assets wish to spread out requests over time. We suggest customers rate limit our requests and respond with HTTP response code 429. Rate limited requests will fail to render and that will be visible to the partner fetching your template with that asset. Our partners retry these requests multiple times so only substantial and long-running rate limits would impact advertising performance.


 

 

 

Related articles