Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
In the Products tab, you will be presented with all the products imported through our import channel, you can check the details and metrics from each product.
You can filter your products by Catalog or manually searching for a specific product.
When checking the details for each product, you will see all the information gathered from the Mapping, as well as any errors in the product.
You can select as many products as you wish to compare them in the metrics tab, providing you with important information about each product and how it is performing. If you hover the cursor over the , a detailed description of the metric will be shown.
In the Catalogs tab, you will be able to create a catalog, and then install a pixel to your page so that BMS can collect data from your page based on the following events:
Product Viewed
Product Added to Cart
Product Ordered
By adding those events to your page, we will be able to collect all the data needed to start creating metrics and then use our Recommendation Models to improve your ads.
To create a catalog, click on button.
Choose a name for your catalog, and if you wish, add Tags to better identify your catalog.
Then your catalog will be available on your list.
Attention! We advise you to deactivate the Catalog instead of completely deleting it. When deleting a Catalog, all data and metrics are lost as well.
Once you have created your catalog and installed your pixels, and everything is set up correctly, you should start seeing events appear in your metrics. Check our metrics page to get a broader view of how events occur and their descriptions.
You can select multiple catalogs for comparison and assess their individual performance.
To have a more broader view on each specific metric go to the CS2 Metrics page.
In order to activate our metrics and events, you are required to install a pixel on your website to start collecting data.
Select a Catalog where you want to install your pixels and then move to the Install Instructions tab.
Each event has a correct page to have your pixel installed, check on each event description to know exactly where.
Don't forget to replace the placeholder with your offer ID. Every website has its own way of defining an offer ID variable, so pay attention to how this variable was configured in your website. If the correct variable is not used for your products, the event will not work. Ensure that the offer ID variable on your website returns the same values that were imported as product identifiers (on our platform, they are called Offer IDs) in your catalog.
Example: The Product ordered event should be installed on your order confirmation page.
After filling in the fields, click on .
If you need to Edit a catalog's name or tags, click on , after making the necessary changes, click on .
To archive a catalog, click on , then your archived catalog will be shown in the Archived list, to alter your view flip the toggle .
To unarchive a catalog, toggle your view to the Archived list then click on , and your catalog will return to the active catalogs.
To delete a catalog, click on , a screen will be shown to confirm the deletion.
After clicking on , your catalog will be permanently deleted.
A broad list of Metrics is available and you can group them by Catalog, Import Channel, and Recommendation Model, each presenting its metrics, should you need any detailed information from a specific metric, hover your cursor over the and you will have that metric's description.
Learn more about recomendation models and how to create them.
Use recommendation models to display your products on dynamic banners, which display different products according to who receives the ad, intending to increase your conversions.
Before creating a recommendation model it's necessary to configure catalogs and the DMP services that will act as sources for our recommendation models.
Fill in the details:
Name: Inform a name for your recommendation model.
Tags: Set tags for your organization.
Catalog: Select the catalog containing the products you will use for this recommendation model.
After creating a recommendation model, it's necessary to configure its sources before being able to use it. This can be done at the configuration tab:
Select a recommendation model in the list.
Fill in the details:
Name: Inform a name for your source.
Limit: Set the maximum number of products to be added to the recommendation model by this source.
Type: Select the type of source you want to use:
DMP Tracker: This option will add products to the recommendation model based on the activity data collected on your website.
Tracker: Select the tracker you want to use.
Tracker Event: Select the tracked event that will be considered to add products to the recommendation model.
Field Containing Offer IDs: Inform the customized field containing the offer ID of the products you want on this recommendation model.
Template: Specify a template to produce an offer IDs comma-separated list to track.
CS2 Product Ranking: This option will add products to the recommendation model based on the activity collected by your product catalog.
Rank by: Select a ranked activity between the options available:
Most Added to Cart: This option will add the most added-to-cart products to your recommendation model.
Most Ordered: This option will add the most ordered products to your recommendation model.
Most Recommendation Clicked: This option can only be used after running a campaign with recommendation models, and it will fill your recommendation model with the products that were recommended before and have been clicked by a user.
Most Recommendation Viewed: This option can only be used after running a campaign with recommendation models, and it will fill your recommendation model with the products that were recommended before and have been viewed by a user.
Most Recommended: This option can only be used after running a campaign with recommendation models, and it will fill your recommendation model with the most recommended products.
Most Viewed: This option will add the most viewed products to your recommendation model
In the past hours: Set a number of hours in the past to consider the activity collected during the period for adding products to the recommendation model.
Right after creating your source, a preview of your recommended products will be available. For this preview to be generated, you should have your cookie pools and trackers and/or your catalog events installed on your website, as their data will be used to generate the recommendations.
There are some editing options available for recommendation models and sources.
Sources are how you collect data to power your Recommendation Model. The Recommendation Model needs this data to organize products as intended. You must choose between a DMP Tracker or a CS2 Product Ranking; both methods work well, but each requires additional steps for proper configuration. Once you have configured your source correctly, your Recommendation Model will start collecting data and actively updating itself, providing your ad with the most current information.
Attention! Be careful when deleting recommendation models, this action cannot be undone and all the related data, including previously collected metrics, will also be deleted.
You can learn more about how metrics are handled by visiting the Metrics page.
This metrics tab contains data about how your website's users interact with your products. Without selecting a product, account-wide metrics data for all your products will be displayed on this tab, selecting one product will restrict the displayed metrics data to the selected one and selecting more than one will generate a metrics comparison between the selected products.
This metric shows the number of times the selected products have been added to the cart in the defined time frame.
Example: In a context where you install an event on your website, intending to track products that have been added to the cart by your users. You also configure an action to track the product in the catalog for when this event happens. This metric shows how many times a product has been added to the cart, use this data to understand in which products your website's audience is more interested. This graph's defined time frame was 3 days, divided into 6h periods, represented as dots. You will notice that on June 24th, between 12 PM and 6 PM, there were nearly 400 products added to the cart.
This metric shows the number of times the selected products have been ordered in the defined time frame.
Example: In the case where you install an event on your website, intending to track products that your users have ordered. You also configure an action to track the product in the catalog for when this event happens, this metric shows you how many times the selected products have been ordered, use this data to understand in which products your website's audience is more interested. This graph's defined time frame was 3 days, divided into 6h periods, represented as dots. You will notice that on June 24th, between 12 AM and 06 AM, there were nearly 50 products ordered.
This metric shows the number of times the selected products were included in a recommendation in the defined time frame.
Example: In the context of using a recommendation model for a retargeting campaign, this metric will show you how many times a product was included in a recommendation, use this data to understand which of your products are being recommended on your banners. This graph's defined time frame was 3 days, divided into 6h periods, represented as dots. You will notice that on June 24th, between 12 AM and 6 AM the selected products were included on a recommendation nearly 4000 times.
This metric shows the number of times the selected products were visualized in the defined time frame.
Example: Suppose you have installed on your website a product view event, with an action of track in the catalog, these metrics will show you a count of how many times the selected products were viewed on your website. Use this data to understand in which products your audience is more interested, then create a recommendation model based on this data. This graph's defined time frame was 3 days, divided into 6h periods, represented as dots. You will notice that on June 24th, between 12 AM and 6 AM the selected products were visualized nearly 3000 times.
This metric shows the number of times the selected products' recommendations were clicked in the defined time frame.
Example: In case you have a campaign using a recommendation model, this metric will show you a count of clicks on your recommendations, this data will help you to measure your recommendation model efficiency, which will allow you to test different marketing strategies and observe how your audience is reacting on it. This graph's defined time frame was 3 days, divided into 6h periods, represented as dots. You will notice that on June 24th, between 12 AM and 6 AM, the recommendations were clicked 2 times.
This metric shows the number of times the selected products' recommendations were viewed in the defined time frame.
Example In the context where you have a campaign that is using a recommendation model to generate banners, this metric will show you a count of views on your recommendations, the data this metric provides is useful to understand if your recommendations are being viewed, furthermore, comparing this metric with the Recomendation Click Count metric will allow you to understand if your banner is interesting to your targeted audiences. This graph's defined time frame was 3 days, divided into 6h periods, represented as dots. You will notice that on June 24th, between 12 AM and 6 AM, the recommendations have been viewed nearly 4000 times.
You can learn more about how metrics are handled by visiting the Metrics page.
All features on CS2 have their own metrics tab, containing data about aspects related to each one, including performance and processing data.
The Catalog Metrics tab is a collection of all metrics available on all features of CS2. Initially, without selecting any catalog, a comparison between your catalogs will be displayed on this tab. Selecting more than one catalog will also show a comparison, this time between the selected catalogs. Picking only one catalog will enable the 'Group by' feature.
There are 3 options available on the 'Group by' feature:
Group by Catalog: This will display all the metrics data related to the selected catalog.
Group by Import Channel: This will compare the metrics related to the import channels linked to the selected catalog.
Group by Recommendation Model: This will compare the metrics related to the recommendation models linked to the selected catalog.
The Products Metrics tab contains data about how your website's users interact with your products. To learn more about each metric related to this feature, go to the Products Metrics article.
The Import Channels Metrics tab contains data about your importing jobs, such as data processing, performance, and failure rate. To learn more about each metric related to this feature, go to the Import Channels Metrics article.
The Recommendation Models Metrics tab contains data about how your recommendation models are performing. To learn more about each metric related to this feature, go to the Recommendation Models Metrics article.
You can learn more about how metrics are handled by visiting the Metrics page.
The import channels metrics tab contains data about your importing jobs, such as data processing, performance, and failure rate. The metrics tab will display account-wide data for all import channels if no import channel is selected. Selecting a single import channel will show metrics specific to that import channel while selecting multiple import channels will compare their performance.
This metric shows how many import jobs you have started in the defined time frame.
Example: Use this metric to follow how many import jobs are being started on your account. On this graph, the defined time frame was 1 week divided into daily periods, represented as dots. You will notice that there is 1 import job started each day, which means the catalog is being daily updated.
This metric shows how much time was taken until the import jobs were concluded in the defined time frame.
Example: Use the data obtained on this metric to define the best catalog update option according to your business needs. On this graph, the defined time frame was 1 week divided into daily periods, represented as dots. You will notice that on June 24th the time until the import job was concluded was nearly 1 second.
This metric shows the import job failure rate within the defined time frame, indicating the percentage of import jobs that have failed.
Example: When an import job fails, it means that the platform couldn't retrieve any data from the feed file, this could be an issue with the mapping or the source feed file. On this graph, the defined time frame was 1 week divided into daily periods, represented as dots. You will notice that the import job failure rate was 0%, meaning no job has failed.
This metric shows the number of issues with import jobs within the defined time frame. Some issues may occur due to invalid or missing data in your feed file. The causes of these issues can be analyzed on the jobs tab.
Example: When an import job has been completed, however, some issues occurred on the process, such as a mapping issue or missing data in the feed file. On this graph, the defined time frame is 1 week, divided into daily periods, represented as dots. You will notice that during the first 5 days of the week, there were nearly 10 issues with the import job. Additionally, you will observe that on June 24th and onwards, there were no issues with the import job, indicating that the feed file was fixed
This metric shows the amount of bytes processed during the import jobs in the defined time frame.
Example: You can use this to follow the size of the imported feed file on a time frame. On this graph, the defined time frame was 1 week divided into daily periods, represented as dots. You will notice that on each day, almost 1 MB was processed during import jobs.
This metric shows the amount of records processed during the import jobs in the defined time frame.
Example: You can use this metric to measure how many records are being processed during your import jobs. On this graph, the defined time frame was 1 week divided into daily periods, represented as dots. You will notice that on the first 5 days, the import job was processing almost 100 records, on the last 2 days, it was processing a little more than 100 records, which means the feed file has been modified.
You can learn more about how metrics are handled by visiting the Metrics page.
This metrics tab contains data about the performance of your recommendation models. Without selecting a recommendation model, account-wide metrics for all your recommendation models will be displayed. Selecting one recommendation model will restrict the displayed metrics to that model. Selecting more than one will generate a comparison of metrics between the selected models.
This metric shows the number of times the selected products were included in a recommendation in the defined time frame.
Example: In the context of using a recommendation model for a retargeting campaign, this metric will show you how many times a product was included in a recommendation, use this data to understand which of your products are being recommended on your banners. On this graph, the defined time frame was 1 week divided into 30-minute periods. You will also notice that the product recommendation count was nearly 500 most of the time.
This metric shows the number of times the selected products' recommendation was clicked in the defined time frame.
Example: In case you have a campaign using a recommendation model, this metric will show you a count of clicks on your recommendations, this data will help you to measure your recommendation model efficiency, which will allow you to test different marketing strategies and observe how your audience is reacting on it. On this graph, the defined time frame was 1 week, divided into 6h periods, represented as dots. You will notice that on June 22nd at 12 PM there were 4 clicks on the recommended products.
This metric indicates if the recommendations are being fulfilled with products or if it's missing products in the defined time frame.
Example: Suppose you have a campaign using a recommendation model to generate banners. You will need to set the number of spaces to be filled with recommendations. This metric shows you if your spaces are being fulfilled, use this data to follow if your recommendation models are working properly, which means that the recommendations are being 100% fulfilled, and therefore your banner will not display any empty space. This graph's defined time frame was 1 week, divided into 6h periods, represented as dots. You will notice that on June 24th at 12 AM the recommendation fulfillment rate was nearly 80%, meaning that some spaces on the banner were not filled with products.
This metric shows the number of times a recommendation was requested in the defined time frame.
Example: In case you are using a recommendation model to generate your banners, this metric will show you how many recommendation requests were processed by the platform, this data is useful to follow your consumption of the recommendation models feature. This graph's defined time frame was 1 week, divided into 6h periods, represented as dots. You will notice that on June 23th at 6 PM the recommendation request count was nearly 2000 requests.
This metric shows the number of times the selected product recommendation was viewed in the defined time frame.
Example: In the context where you have a campaign that is using a recommendation model to generate banners, this metric will show you a count of views on your recommendations, the data this metric provides is useful to understand if your recommendations are being viewed, furthermore, comparing this metric with the Recomendation Click Count metric will allow you to understand if your banner is interesting to your targeted audiences. On this graph, the defined time frame was 1 week, divided into 6h periods, represented as dots. You will notice that on June 26th at 12 PM there were nearly 4000 views on your recommendations.
The catalog storage service billing section is available on the billing page. It contains information about every billed item related to CS2 and is divided into 6 sub-sections.
At BMS, it prioritizes transparency by displaying every detail of your bill. Visit our to understand how the bills are structured.
Below is an explanation of each of these sections with their respective details.
This subsection outlines the costs associated with catalog management. Deletions are free of charge, and each service in this section includes a free quota of 1,000 requests, except for the storage, which is billed based on the number of catalogs stored and the duration of their storage.
Example: In this picture, there were consumed nearly 1,039 catalog-hours, which is equivalent to 1 catalog stored for a month with another catalog stored for a few days, resulting in a $1.08 charge. You can also observe that no charges were applied for the other services consumed since the free quota was not exceeded.
This subsection outlines the costs associated with import channel management. Import channels configured are billed based on the number of import channels configured and the duration of their availability on the platform, import jobs are billed according to how much data they have transferred, there is a free quota of 100 requests for the start import job service, after which charges will incur per request, for the other services on the section there is a free quota of 1,000 requests, after which the services will be billed per request.
Example: In this picture you will notice that for most services the free quota was not exceeded and therefore no charges were applied to these services, it is also possible to observe that nearly 325 channel-hours were consumed, which is equivalent to having 1 import channel configured for almost two weeks, resulting on a $0.34 charge, you can see that nearly 5 GB were transferred on this period, resulting on a $0.42 bill, after reaching the quota, the listing import jobs service was charged per request, resulting on a $0.28 charge, therefore this customer will be charged on $1.03 for the services on this subsection.
In this subsection, you will find the cost details for the recommendation models. Deletion actions are free of charge, there is a free quota of 1,000 requests for every service on this section, except for the Models Configured, which is billed based on the number of recommendation models you have configured and the duration of their availability and use.
Example: You will notice that, in this picture, most of the services consumed did not exceed the free quota, and therefore no charges were applied, it is possible to observe that nearly 835 model-hours were consumed, which is equivalent to 1 model configured for almost a whole month, resulting on a $0.87 bill.
This subsection details the costs related to the use of the recommendation engine, there is a free quota of 1,000 requests, after exceeding this quota, the charge is applied per product recommendation request.
Example: In this picture, the free quota was not exceeded, and therefore no charges will incur for the services.
This subsection contains the cost details related to product management. Deletions are free of charge, except for the storage, every service on this section has a free quota of 1,000 requests, after which you will be charged per request, the storage is billed based on the number of products you have stored and the duration of their storage.
Example: You will observe, in this picture, there were no charges for the services that did not exceed the free quota, after exceeding the quota the creating products and the patching products services were billed per request, there were nearly 35 thousand creating products requests, resulting in a $0.52 bill, and nearly 35 million patching products requests, resulting in a $ 513.17 bill, you can also notice that almost 208 million product-hours were consumed, resulting in a $28,85 bill, totalizing a $542.55 bill for the services in the section.
This subsection contains the cost details related to the catalog tracking, every service in this section has a free quota of 1,000 requests, after which you will be charged per request.
Example: In this picture, you will notice that a free quota of 1,000 requests was given to each service, after exceeding this quota, the charges were applied based on the number of requests used, there were nearly 151 thousand requests for tracking product events, resulting in a $1.51 bill, and nearly 31 thousand tracking recommendation event requests, resulting in a $0.31 bill, totalizing $1.82 for the services on the section.
Use import channels to upload your products' catalog's feed to our platform, this feature will also keep your catalog updated according to the feed.
Import Channels can import data from HTTP, FTP or SFTP websites. Google Merchant's XML format is the standard for creating catalogs and the easiest to work with, but the import channel can be configured to use CSV or other XML formats.
Fill in the details on the 3 tabs:
General Tab On this tab, you will find the general details related to your import channel, use the examples to help you fill in all the details.
Name: Set a name for your Import channel.
Tags: Set tags for your organization.
Catalog: Select the catalog you've created to receive the products on the feed.
When to create or update products: Set the period in which your products will be created or updated.
When to remove products:
Never: Products created or updated at the source will be modified or added to the catalog. However, products deleted at the source will not be removed from the catalog.
Before each importation: All products will be deleted from the catalog before each import process. Then, products that exist at the source will be added to the catalog. Beware! The catalog will remain empty until the importation is completed, which might result in empty ad banners during this period. All product metrics will be preserved.
Hours after being imported: Define how long after importation products should remain in the catalog if not re-imported. As long as the import frequency is shorter than the product expiration time, the catalog will not become empty. All product metrics will be preserved.
Source Tab This tab contains the source details related to your import channel, use the examples to help you fill in these details according to your source option.
Protocol: Select the protocol of your source and fill in the details according to your choice.
HTTP:
URL: Inform your feed's URL
SFTP and FTP:
Host: Inform your source's host.
Port: Inform your source's Port.
User: Inform a user to access your source.
Password: Inform the password to validate your user at the source.
Path: Inform the path to your source.
Detected Records: Display your feed's records in table format.
Issues: Display the problems that can affect your import job.
Raw: Display your feed file source code.
Charset: Inform the source's charset, which was previously detected on the source test result.
File Format: The source test result will automatically fill these fields, however, you can change them manually. Select between these options:
CSV: Source feed based on a file with comma-separated values.
Delimiter: insert the character that separates your file values.
XML: Source feed based on an XML file.
Item tag: insert the item tag on your XML file.
Mapping Tab You will find on this tab the mapping details related to your import channel, use the examples to help you to configure your mapping.
Template Format: Select between these two options:
Google Shopping: Select this option if you are using a Google Shopping Feed.
Advanced: For any other kind of feed file, select this option.
Filters Tab In this tab, you will be able to set filters to select the products that you need to import. This can be useful for reducing the costs of import jobs by importing only the products you need.
Path: Inform a path value, such as one of the feed column labels.
Operator: Select one of the operator values, this value will establish the filter.
Value: Inform the value you need to filter from your catalog's feed, such as a brand name, or range of product ids.
After filling out the fields, you will also need to input the same data into the displayed template. You must change only the values you are filtering, otherwise, it will not work properly.
Example 1: In this picture, you will notice that a filter was established using the description column of the feed file as a reference for the path, the chosen operator was 'Contains', and the Value was 'Cerdo', meaning that this import channel will only import products that contain the word 'Cerdo' in their description. You will also notice that on the template, the content of the line 'description' was modified to match the filter value.
Example 2: You will also notice a filter using the 'url' column as a reference for the path; this one was manually added. To manually add new columns to your filters, they must be present in your feed's mapping too. You also need to respect the template semantics: columns are comma-separated, and a colon is used to separate a column label from its value. Column labels and values must be declared between quotation marks.
Click on to start creating a recommendation model.
Click on to save your recommendation model.
Click on to add a source for this model.
Click on to save your source.
You can edit a recommendation model's name and tags, however, the catalog cannot be changed. To make this edition click on at the same row as the recommendation model to be edited.
All source details are editable, select the recommendation model containing the source to be edited. Then, in the configuration tab, on the sources section, click on at the same as the source to be edited, make your changes, then click on to save them. You can also duplicate a source by clicking on . This is useful if you need another source with only a few changes compared to an existing one while keeping the existing one.
You can archive a recommendation model by clicking on at the same row as the recommendation model we need archived. It's also possible to delete a recommendation model, however, this will delete all the metrics related to it, this action cannot be undone, so be careful when performing it. Click on at the same row as the recommendation model to be deleted. Then confirm the action by clicking on . This action cannot be undone.
It's possible to delete a source. However, this will also delete all the metrics related to this source, so be careful when performing this action. In the sources section of the configuration tab, click on at the same row as the source to be deleted. Then confirm the action by clicking on . This action cannot be undone.
These are all the metrics available in the Product feature for analyzing the performance of your products. Additionally, when checking metrics, you can always check our to access additional information about a specific metric.
These are all the metrics available in the Import Channels feature for analyzing the performance of your import channels. Additionally, when checking metrics, you can always check our to access additional information about a specific metric.
These are all the metrics available in the Recommendation Model feature for analyzing the performance of your recommendation models. Additionally, when checking metrics, you can always check our to access additional information about a specific metric.
All products generate metrics once you start using them. These metrics are charged and are crucial for understanding your BMS platform usage and performance. The is responsible for these metrics and will display the related bill. BMS is focused on transparency and will show you the costs for all features within each product.
To start creating an Import Channel, we must first create the catalog which will contain the products imported by the feed, to create a catalog follow the steps in the article, we also will need to have a products feed to use as a source for our import channel.
Click on to start creating your Import Channel.
Test Source: This button, , allows you to test your source and retrieve relevant data for the next fields. There are three tabs for the source test result:
After finishing the test click on to close the source test result window and automatically fill the next fields with your test results.
Detect Template: Click on to detect the best template based on your feed file.
Test Template: Click on to access a preview of how your products will be displayed in your catalog. If there are any failures with the mapping or the feed file, you will notice them on this test.
Click on to proceed.
You can add as many filters as necessary by clicking on , and also remove them by clicking on at the same row as the filter you want to delete.
Once you have finished the steps above, check your settings to ensure everything is correct, then click on to save your Import Channel.
Click on to start a manual job for importing your products:
Click on to start importing your products.
It's also possible to import only a few products to test if everything works fine before starting the full import. We can do this by checking the box 'Testing Mode', filling in the details and then clicking on .
Follow your import at the Jobs tab, at this tab we can see the issues with our import or if they were completed. It's possible to understand the problem by clicking on or on the same row as the failed job.
We can edit our import channels by clicking on at the same row that the import channel you need to edit. All details are available for editing.
We can delete unused import channels by clicking on at the same row that the import channel to be deleted is, however, this will also delete the metrics related to it, so proceed with caution, alternatively we can also archive these import channels by clicking on at the same row that the import channel to be archived, to view archived import channels, turn on the option 'Archived' above the import channels' list.
In our CS2 area, you will be able to import your eCommerce products and then access our Recommendation Models feature. These models provide insights about your catalog's users, allowing for the reanalysis of your catalog's ads to better meet their needs and recommend other products accordingly.
You can learn more about how metrics are handled by visiting the .
The Catalogs' metrics tab presents a compilation of all the metrics available in CS2. In this article, we will discuss only the catalog-specific metrics. You can learn more about the other CS2 metrics in the article dedicated to each of the features: , , and .
This metric displays the total number of products in your catalog within the specified time frame.
Example: When importing your catalog's feed it's possible to experience some issues, like a missing product, for example, this metric shows the number of products that are included in your catalog, and this can help you to notice missing products. In this picture, the defined time frame was 8 days, divided into daily periods, you will notice that there are a little more than 1 million products in this catalog, the number of products has changed each day, showing that this catalog is being updated daily.
This metric shows the number of products added to your catalog in the defined time frame.
Example: You can have your new products added to your catalog anytime you need, this metric will help you to understand how many new products were added to your catalog. In this picture, you can observe that the defined time frame was 8 days, divided into daily periods, on Sep 2, nearly 3 thousand products were added to the catalog, you can also observe that every day, new products were added.
This metric displays the number of products in your catalog that have been updated in the defined time frame.
Example: When updating the catalog, this metric will help you track the number of products that were updated. Use this data to ensure that all the updates made to your feed file were processed by the platform. In this picture, the defined time frame was 8 days divided into daily periods, you will notice that on Sep 2, nearly 3 million products were updated, then, between Sep 3 and Sep 5, almost 4 million products were updated daily, after that we can observe a decreasing number of products updates.
This metric shows the number of products that were removed from your catalog in the defined time frame.
Example: When updating your catalog, this metric will help you track the number of products removed. Use this data to ensure that all the products you removed from the feed file were also removed from your catalog. In this picture, the defined time frame was 9 days divided into daily periods, you will observe that on Sep 9, almost 1 million products were removed from this catalog, and no product was removed between Sep 11 and Sep 15, on Sep 16 a few products were removed from the catalog, and then on Sep 18, we have another huge catalog update, removing almost 1 million products again.
These are all the metrics available in the Catalog feature for analyzing the behavior of your catalog. Additionally, when checking metrics, you can always check our to access additional information about a specific metric.