New product, new amount of stock or change in price… Have the modifications of my source feed been taken into account by the broadcasters? To help you, Lengow has put an indexing history at your disposal. You will find it in feed management, under “Indexing history”. Here are a few tips for you.
1. The updating process of your catalogue
The updating of your product catalogue with the broadcaster is done in two stages:
Stage 1: Updating on Lengow
Our indexation robot questions your source feed to retrieve the values and update them within the solution. The indexing history will allow you to know:
- When the last indexation of your source feed took place;
- How many new products have been detected;
- The amount of errors that were found.
Stage 2: Updating with the broadcaster
Once you have transferred the URL of your optimized feed to the broadcaster, the latter will question it daily to update your catalogue. You will then be able to see on what date the URL of the feed was questioned.
For marketplaces using an API, your catalogue will be sent out daily. The mailing frequency depends on the marketplace. You can consult the frequency in either indexing history or in our broadcasting guides.
2.1 Manual setting up of indexing frequency
Once you will have determined the average frequency at which the broadcaster retrieves the optimized feed, you will be able to change the indexing time and frequency of your feed source from the indexing history page. The aim is to be able to plan the updating of your feed before the broadcaster comes to retrieve the optimized feed. We suggest you plan the indexing of your feed source at least an hour before.
Note: It is possible to select different hours. To do so, keep the Ctrl key of your keyboard pressed (cmd key for MAC), while clicking on the hours you choose with the left click on your mouse.
2.2 Programmed setting up of indexing frequency
You can use our automatic calibrating tool. This tool will look at the last indexing made on your optimized feed and will automatically indicate an indexing of the feed source 30 minutes before that hour for the next time the indexer comes by.
You can define the IPs you want to exclude, such as your own personal IP. This way, when you make calls to open the optimized feed, our system will not take your call into account for the automatic calibration.
Caution: This tool takes into account all the calls to open the optimized feed (not only the calls from the broadcaster). We advise you to manually define the feed indexing frequency, according to calls from the broadcaster. If you want to choose the automatic calibration, you have to exclude your own personal IP.
2.3 Setting up when using a CRON
Our indexers have three minutes to retrieve your feed source, beyond those three minutes, the indexing stops. If your feed source takes more than three minutes to generate, you will need to use a CRON so that the data is not retrieved from your databases, but pre-exported and available in hosted files on our server.
If a CRON has been put in place on our server to generate a file that we will then retrieve, you will need to have given the frequency of generation of that file. You will also need to know the time at which the file is generated on your side, to be able to then indicate to our indexers, the time at which they will be able to retrieve it. If your file is generated once a day, you will not need to define indexing every hour, since we will retrieve the same information each time.
3. Lengow is no longer indexing my source feed
Below is a list of errors you may encounter when Lengow indexing is underway:
- "Error 404" : Your source feed was not available when the indexer scanned it (404 Error)
Solution: Try to download your source feed by loading the URL available in your “Source Feed” tab. If the feed does not load, contact your service provider/webmaster.
- "Failed": Your source feed took longer than three minutes to load. Our indexers have three minutes to pick up your source feed. Once these three minutes have elapsed, indexing stops.
Solution: To reduce the time it takes for your source feed to load, you can either:
- contact your service provider/webmaster to improve the time it takes for your source feed to generate
- or export your source feed into its own file and mark it as a cron job.
- "100% Error" / "Feed unavailable": Your source feed was not available when the indexer scanned it.
Solution 1: Try to download your source feed by loading the URL available in your “Source Feed” tab. If the feed does not load, contact your service provider/webmaster.
Solution 2: Check the compatibility of the source feed.
Solution 3: Check that access to our servers’ IP addresses is authorised (184.108.40.206 ; 220.127.116.11 ; 18.104.22.168 ; 22.214.171.124 ; 126.96.36.199 ; 188.8.131.52 ; 184.108.40.206 ; 220.127.116.11 ; 18.104.22.168 ; 22.214.171.124)
If none of these solutions solves the problem, contact our customer support team.
- "Error matching": the header of one of the following fields has been changed in your source feed: "category", "id", "title" and/or "price".
Solution: You must either:
- replace the header in the modified field with the original header.
- contact our customer support team so they can update your data.
- "Duplicate column": there are at least two duplicate headers in your source feed.
Solution: Download your source feed by loading the URL available in your “Source Feed” tab and check that there are no duplicate entries in the field headers. If there are, change at least one of the two headers directly in your back office.
If there are no duplicate entries, check in the “Source Feed” tab that the virtual field names are not duplicate with the headers in your source feed. If they are, change the name of the virtual field.
If neither of these cases applies, contact our customer support team.
"Alert Ratio": Our system has detected a significant reduction in the number of products in your source feed and the "Alert in case of product de-indexation" option has been activated in the “Options” tab.
Solution: If the reduction in the number of products is deliberate, temporarily deactivate the "Alert in case of product de-indexation" option.
If the reduction in the number of products is not deliberate, check that your source feed is properly configured to export and request manual indexation from our customer support team once the situation is back to normal.
- "Empty source feed": our system has detected an empty source feed when the indexer scanned it.
Solution: Try to download your source feed by loading the URL available in your “Source feed” tab:
- If the feed does not load, contact your service provider.
- If the flux does load, contact our customer support team.
- "Carriage Return and/or Line Feed": You may receive the following message in an email:
"Your data feed xxx (idFlux : xxx) has been updated but your data feed contains incorrect product lines that prevent our system from indexing these lines properly. Most common issues are:
- Carriage Return and/or Line Feed > in this case, the product data start on one line and continue on the next line.
- Column shift > your products must contain as many columns as specified in the file\'s header row."
Solution: Use the feedtester available in the “Source Feed” tab to find and fix the error in your source feed.
- "Product with same ID": You may receive the following message in an email:
"We have detected some products with the same ID in your source feed.
- 70_13609 (2x)
- 70_5899 (2x)
- 50_16479 (2x)
Therefore, only one of these products was indexed in Lengow. (Please note that a product ID can only be used once in your source feed.)."
Solution: Delete the duplicate product IDs directly in your source feed. If you do not find any duplicate entries in your source feed, contact our customer support team.
4. The broadcaster is not updating my feed
In this case, you will need to contact him to ensure that he has taken the URL of your optimized feed into account that Lengow has made available.