Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
You can learn more about how metrics are handled by visiting the Metrics page.
To access the metrics tab select the trackers which you want to visualize data on the trackers' list:
You can select more than one tracker. However, the 'Group by' option is only available when selecting a single tracker. When selecting multiple trackers, the data will be grouped by tracker and this option will not be displayed.
When grouping by tracker all the data collected by the selected tracker will be displayed on these metric cards or in the data table columns:
This metric shows how many actions were executed by your tracker in the configured time frame.
Example: On this graph, you can observe an increase in the number of actions at 6 AM. The graph displays a time frame of 3 hours divided into 5-minute intervals represented as data points. After creating a tracker, you will need to set up events and actions. Each time a tracked event occurs, the configured actions associated with that event will also be executed. For instance, an 'add to cart' event might trigger an action to track the added product in the catalog. This metric indicates when and how often the action is executed within that time frame.
This metric shows when an event has been tracked, however, the action linked to it has failed.
Example: When a user adds a product to their cart on your website and this event is configured to be tracked, with an action to track it in the catalog, the event itself is tracked successfully. However, the action to update the catalog failed, resulting in the product not being tracked. In the graph, you can observe that the action failure rate is typically 0%. However, there are moments where the action failure rate peaks near 40%. The graph covers a time frame of 3 hours, divided into 5-minute intervals represented as data points.
This metric shows the amount of users' expirations that occurred in the defined time frame.
Example: When configuring a tracker, you can set a tracking period after which the user will expire. This metric shows the number of expirations that occurred. On this graph, you can observe that between 4 AM and 5 AM, nearly 50 tracked users expired.
This metric shows the configured maximum number of users to be added to the tracker.
Example: When creating or editing a tracker, you will set the maximum number of users allowed to be added to your tracker. This metric displays that data. In this graph, you can observe that the tracker was configured to accept up to 1 million users
Whenever a user performs a new tracked activity on your website, this will be tracked, this metric will show the number of new activities tracked in a defined time frame.
Example: You have an 'add to cart' event configured on your tracker. Whenever a user adds a product to the cart, it counts as a new activity. On this graph, you will notice that the number of new activities increases after 6 AM. You will also observe that this graph covers a time frame of 3 hours, divided into 5-minute intervals represented as data points.
This metric shows the remaining time a cookie is still available in the pool until expiring in the determined time frame.
Example: When you create your cookie pool you can set the number of days in which a cookie will expire, this metric shows you how much time you have until a cookie expiration. On this graph, the time frame was of 1 week, divided into daily periods, represented as dots, you can observe that on June 20th there was less than 1 day until some of the cookies in the pool expire.
This metric will show how many users were in the tracker in the defined time frame.
Example: After setting up a tracker on your website, your website's users will begin to be tracked. The number of users tracked within a defined time frame is the data shown in this metric. On this graph, you will notice that the number of tracked users between 4 AM and 6 AM was nearly 400 thousand.
When grouping by event, the displayed metrics will be separated according to their respective events. The following metric cards or data table columns are available:
This metric shows the number of actions executed by each tracked event within the configured time frame.
Example: You have a 'product view' event configured on your tracker, linked to a 'track in catalog' action. Every time a product is viewed, the event is tracked, and the associated action is executed. This metric shows this data grouped by event. On this graph, you can observe an increase in actions around 6 AM. The graph covers a time frame of 3 hours, divided into 5-minute intervals represented as data points.
This metric shows instances where an event was tracked but the linked action failed to execute. The data is displayed grouped by event.
Example: When a user on your website adds a product to the cart and this event is configured to be tracked, with an action to track it in the catalog, the event is successfully tracked. However, the action fails to execute, resulting in the product not being tracked in the catalog. On this graph, you can see that the action failure rate is typically 0%, but there are moments where it reaches nearly 40%. The graph covers a time frame of 3 hours, divided into 5-minute intervals represented as data points.
Whenever a user performs a new tracked activity on your website, it will be recorded. This metric shows the number of new activities tracked within a defined time frame, grouped by event.
Example: You have 'add to cart' and 'product view' events configured on your tracker. Every time a user performs any of these tracked activities, it will be counted and displayed in this metric, grouped by event. On this graph, you will notice that the number of new activities increases after 6 AM. The graph covers a time frame of 3 hours, divided into 5-minute intervals represented as data points.
These are all the metrics available in the DMP product for analyzing the performance of your cookie pools and trackers. Additionally, when checking metrics, you can always check our to access for more information about a specific metric.
You can learn more about how metrics are handled by visiting the Metrics page.
All features on DMP have their own metrics tab, containing data about aspects related to each one, including performance and processing data.
The Cookie Pools Metrics tab contains data about how your website's users interact with it. To learn more about each metric related to this feature, go to the Cookie Pools Metrics article.
The Trackers Metrics tab contains data about your websites' tracked activity. To learn more about each metric related to this feature, go to the Trackers Metrics article.
A Cookie Pool is a collection or database of users' cookies. Cookies are tiny pieces of data stored in a user's web browser when they visit a website. These cookies record users' online behavior, preferences, and interactions with websites and services.
In the context of digital advertising and marketing, a cookie pool can serve several purposes:
Audience Segmentation: Segment users into different groups based on their interests, behaviors, demographics, or other criteria. This segmentation allows for more targeted and customized advertising campaigns.
Retargeting: Collect users' data based on events and actions for tracking purposes, this data can be used later to create recommendation models for your retargeting campaigns, improving your conversions. .
Ad Customization: Use the data gathered to display more relevant ads for each user on your target, based on their recent online activity, interests and behavior, customized ads are more engaging and lead the advertiser to get better results.
Analytics and Measurement: Track your campaigns' performance, measuring click-through rates, conversion rates and user engagement, among other metrics.
Frequency Capping: Set frequency caps to limit how often a particular ad is shown to a user within a certain time frame. This prevents displaying the same ad to the same user repeatedly.
A cookie pool must be created shortly before using it for a campaign so that it can be populated. Configure how long your cookies should be available before expiring, set how many cookies you want to store at your pool and select the Ad Exchanges you will use to synchronize your cookies with it.
Fill in the details:
Name: Insert a name for your cookie pool.
Tags: Insert tags for your organization.
Exchanges: Select ad exchanges to synchronize with your cookies, we recommend selecting only the exchanges you'll use to run your ad campaigns to prevent unnecessary charges.
TTL: Set the number of days a cookie will be kept on the pool after syncing.
Max Size: Set the maximum amount of cookies that will be stored. After reaching the limit no more cookies will be added to the pool until the old ones expire, but the collected cookies will still be available to use, it's also possible to increase your Max Size to allow more cookies to be collected.
Attention! Be careful when deleting cookie pools, this action cannot be undone and all the related data, including previously collected metrics, will also be deleted.
After creating a cookie pool you`ll need to install it on your website to start using it, this can be done by following the instructions on the Install Instructions tab of the Cookie Pools page.
Select the cookie pool you will install by marking the checkbox next to its name.
Paste the code as high up as possible inside the page`s <head> tag.
If you want, it`s possible to use a unique user id, this is useful if your users log in on multiple devices, to do this, uncomment the indicated part of the code and insert the unique user id.
You can also use a tag manager, such as Google Tag Manager (GTM), to add this code to your website.
Trackers are small scripts placed on your websites' codes to gather data on your users' activities, then we can use the collected data to build recommendation models for running retargeting campaigns, improving your conversions. Additionally, this data can provide valuable insights into your users' interests, facilitating the creation of more efficient ad campaigns.
Trackers will gather data about your website's activities, so it must be installed and active for a while before their data can be used for a campaign.
Fill in the details:
Name: set a name for your tracker.
Tags: set tags for your organization.
Maximum users: set the maximum number of users that should be tracked, once the limit is reached, no more new users will be added to the tracker, but the users added will still be tracked.
Maximum events per user: set the maximum number of events per user to keep track, once the limit is reached, receiving new events will cause the oldest ones to be expired.
Maximum activity age: set the number of days for the tracked users' data to be stored, after this period this data will be deleted.
Attention! Be careful when deleting trackers, this action cannot be undone and all the related data, including previously collected metrics, will also be deleted.
Configure events to be tracked and actions to be performed by the tracker when the event happens.
Configure events according to the activities performed by user on your website, for example adding products to the cart, viewing products, and others.
Fill in the details:
Name: Set a name for your event.
Event ID: This field can be customized to set a different event ID, however, it is automatically filled with the event's name.
Custom Data Fields: Set data fields to be collected when the event is captured.
Fill in the details:
Name: Set a name for your action.
What to do?:
Track In Catalog: Allows you to track events based on a product catalog.
Catalog: Select the catalog you desire to use.
Track as: Select as this action must be tracked.
Field Containing Offer IDs: Select the custom field that contains the offer ID or use a template.
Template: Insert a specific template that will be used to create a comma-separated list of offer IDs to be tracked.
Available Custom Data: Custom data fields configured on your event will be displayed here to help you build a template.
Edit your events and actions to meet your business needs.
After setting up events and actions for your tracker you have to install the tracker on your website, this can be done by following the instructions on the install instructions tab.
To access the trackers' instructions tab, select the tracker you need to install in the trackers' list, to use this tab you must select only 1 tracker at a time. The tab will contain one section for each event created for the selected tracker.
There are 3 install methods available for this feature: Script, Pixel and Redirect. You can choose from these options after you expand the section of the event you want to install.
Select the Script option.
If you have configured custom data fields, use the indicated placeholder to inform the values.
Install it on your website where you want this event to be captured.
Select the Pixel option.
If you have configured custom data fields, use the indicated placeholder to inform the values.
Install it on your website on the page you want this event to be captured.
Select the Redirect option.
Inform the URL to where you want to redirect the user to after the event is captured.
Use the generated URL just as you would use the URL you provided.
After installing your events' trackers you should start receiving data from them, it's possible to follow this process on the metrics tab.
You can learn more about how metrics are handled by visiting the .
Select a cookie pool from the list to access its metrics. It is also possible to select more than one to compare their results.
This metric displays how many cookies have expired within the configured time frame. Cookies expire based on the TTL, which is the number of days after which a cookie will expire, configured when creating the cookie pool.
Example: You create a cookie pool with a TTL of seven days and install it on your homepage. The cookies generated by your users' access will be available for targeting for seven days. After this period, the cookies will expire. This means that in a retargeting campaign, for example, you will impact users who visited your website in the last seven days. In this graph, you can observe that on June 19th, just under 5 cookies expired, on June 20th no cookies expired, and on June 21st just under 5 cookies expired, and so on.
This metric shows the maximum amount of cookies allowed in the pool as configured.
Example: When creating or editing a cookie pool, you can set the maximum amount of cookies in the pool. This will limit the total number of cookies your pool can contain. In this graph, you can observe that a maximum size of 100,000 cookies was defined for this cookie pool.
This metric shows the actual size of the pool, meaning it will show how many cookies are or were in the pool within the configured time frame.
Example: On this graph, you can observe the size of a cookie pool in the defined time frame. This metric can be used for gathering knowledge about how many cookies are generated within the configured time frame, which will allow you to set a maximum size for the pool that is in the same range as the number of users on your website.
This metric shows the number of cookie synchronizations, meaning it shows when a collected cookie has been synchronized with our platform and later with the exchanges as well, which allows you to target users more precisely.
Example: On this graph, you can observe the number of synchronizations that happened in a defined time frame. When a user accesses your website, a cookie will be requested for him, after receiving this cookie, it will be analyzed if this user already has a cookie or not, if he does the new cookie will be synchronized with the already existing one, updating its data on the platform, if he doesn't a cookie will be created for him on the platform.
This metric shows the median remaining time a cookie is still available in the pool until expiring in the determined time frame.
Example: When you create your cookie pool you can set the number of days in which a cookie will expire, this metric shows you how much time you have until a cookie expiration. On this graph, the time frame was 1 week, divided into daily periods, represented as dots, you can observe that on June 20th there was less than 1 day until some of the cookies in the pool expired.
Click on to create a cookie pool.
Click on to save your Cookie Pool.
After creating a cookie pool, you can edit it by clicking on the editing button . All parameters are editable, for the TTL the changes will apply only to newly added cookies. After making your changes, click on to save them.
It's possible to archive cookie pools for your better organization. Click on to archive the selected cookie pool, visualize your archived cookie pools by turning on the switch "Archived" above the cookie pools list. It is also possible to unarchive a cookie pool by clicking on .
You can delete a cookie pool by clicking on the delete button , a warning that this action cannot be undone will be displayed to you, to proceed with the process click on to confirm you are deleting it and it's done. Be aware that targets based on these cookie pools will stop working.
On the Install Instructions tab, click on to copy the code.
Click on to start creating a tracker.
Click on to save your tracker.
All the trackers' parameters are editable, click on in the same row of the tracker you want to edit, make your changes, then click on to save them.
It's possible to archive trackers for your better organization. Click on to archive the selected tracker, visualize your archived trackers by turning on the switch "Archived" above the trackers' list. It is also possible to unarchive a tracker by clicking on .
We can also delete our trackers by clicking on the delete button in the same row as the tracker you want to delete, then confirming it by clicking on . This action cannot be undone, so please be careful. Additionally, keep in mind that recommendation models based on the deleted tracker might stop working.
On the Configuration tab, click on to start creating an event.
Click on to add an action to your event.
Click on to save your action.
Feel free to add more actions to this event, and when you're done, click on to save your event.
We can edit events by clicking on at the same row of the event to be edited on the Configuration tab, all events' parameters are available to be edited, after finishing your changes, click on to save them.
Actions' parameters are also editable, you can do this by finding the event that contains the action you want to edit on the Configuration tab, clicking on at the same row of the event, and then clicking on at the same row of the action to be edited, make your changes and click on to save your changes, then click on again to save your changes to the event, and you're done.
It's also possible to duplicate events and actions by clicking on at the same row of the event or action you need to duplicate, this feature can be useful if you need to create a new action or event while keeping some parameters of an existing one.
It's possible to delete events and actions by clicking on at the same row of the event or action that you need to delete, then confirm the action by clicking on . This action cannot be undone, so be careful when doing it. Alternatively, it's also possible to disable events and actions by changing the switch position from on to off in the same row of the event or action you want to disable.
Use the copy button to copy the script displayed.
Use the copy button to copy the image tag displayed.
Use the copy button to copy the displayed URL.
These are all the metrics available in the Cookie Pool feature for analyzing the performance of your cookie pools. Additionally, when checking metrics, you can always check our to access for more information about a specific metric.
The data management platform billing section details the costs related to this service, divided into up to 6 subsections, depending on the services you have consumed.
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.
In this subsection, you can find information about the costs associated with the cookie pool management service. Deleting items does not incur charges, and for any service within this section, other than stored and configured cookie pools, there is a free quota of 1,000 requests. Once this quota is exceeded, a charge per request will apply. As for stored and configured cookies, charges will be based on the quantity of cookies stored and configured, as well as the duration of storage.
Example: In this picture, you can see that nearly 9,000 cookie-hours were consumed. The charge is not shown as it is less than $0.01. Additionally, almost 825 cookie-pool-hours were consumed, resulting in a $0.86 bill. The free quota on the get cookie pool service was exceeded in 7,120 requests, resulting in a $0.07 bill. Since the other services did not exceed the free quota, no charge was applied to them, totaling a $0.93 bill.
This subsection provides details on the cost of the cookie synchronization service. This service is used whenever a cookie in your pool is synchronized with a cookie on the ad exchanges. There is no charge for deletions, and each service includes a free quota of 1,000 requests. Once the free quota is exceeded, a charge per request will be applied.
Example: As observed in this image, none of the listed services have exceeded the free quota, so no charges will be applied.
In this subsection, you will find the cost details for the interest group management service. Deletions are not charged, and there is a free quota of 1,000 requests for each service in this section, except for storage, which will incur charges based on the number of interest groups configured and the duration of storage.
Example: As observed in this image, none of the listed services have exceeded the free quota, so no charges will be applied.
In this subsection, you will find the cost details related to the tracker activity query service. This service is used whenever you request data about your tracker's recent activities. There is a free quota of 1,000 requests for this service; after that, you will be charged per request.
Example: As you can see in this picture, the free quota was not exceeded, and therefore no charges will be applied.
This subsection details the costs related to the tracker activity recorder service. This service monitors and records your tracker activity. There is a free quota of 1,000 requests for this service; after that, you will be billed per request.
Example: In this picture, you can notice that after surpassing the free quota of 1,000 requests, there were nearly 208,000 requests made, resulting in a $2.08 bill.
This subsection provides information about the costs associated with the tracker management service. Except for storing configured trackers, all other services in this section come with a free quota of 1,000 requests. Once this quota is exceeded, a charge per request will apply. Deletions do not incur any charges.
Example: In this picture, you will notice that no charge was applied to the services that didn't exceed the free quota, also nearly 1,700 tracker-hours were consumed, resulting in a $0.23 bill.
Use DMP to collect and manage large volumes of data about your audience's online behavior, then use this data to track your audience and define targets for customized ad campaigns.
A Cookie Pool is a collection or database of users' cookies. Cookies are tiny pieces of data stored in a user's web browser when they visit a website. These cookies record users' online behavior, preferences, and interactions with websites and services. .
Use trackers to gather data about your website's audience's online behavior and configure events and actions to create recommendation models based on this data, allowing you to run retargeting campaigns. .
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.
