BMS Documentation
  • 👋Welcome to BMS
  • Overview
    • ✨Our Features
  • Solutions
    • Creating a Branding Campaign
    • Creating a Retargeting Campaign
  • Product documentation
    • Accounts
      • Account Billing
    • Ad Server
      • Creatives
      • Creative Groups
      • Ads
        • Ad Exchange Review
          • Google Authorized Buyers
          • Xandr
      • Creative Builder
        • Blueprints
        • Builds
      • Ad Server Metrics
      • Ad Server Billing
      • Page Load Tracking Tag
    • Demand Side Platform (DSP)
      • Overview
      • Managing Campaigns
      • Managing Budgets
      • Managing Targets
      • Managing Ads
      • Real Time Tab
      • DSP Metrics
      • Campaign Billing
      • Check URL Classification
    • Data Management Platform (DMP)
      • Cookie Pools
      • Trackers
        • Install Instructions
      • Identifier Pools
      • DMP Metrics
      • DMP Billing
    • Catalog Storage Service (CS2)
      • Catalogs
      • Products
      • Import Channels
      • Recommendation Models
      • CS2 Metrics
      • CS2 Billing
    • Identity Access Management (IAM)
      • Users
      • Groups
      • API Keys
    • Media
      • Media Metrics
      • Media Billing
    • Metrics
    • Monitoring
      • Looker Studio
      • Event Stores
      • Event Pipes
      • Monitoring Metrics
      • Monitoring Billing
    • Billing
    • Tag Container
      • Tag Container Metrics
  • Third-Party Integrations
    • Webhook Tool (Zapier)
    • Google Tag Manager
    • Voluum
    • External Data Lake Sync (AWS)
Powered by GitBook
On this page
  • Creating an Event Pipe
  • Filters
  • Targets tab
  • Enabling your Event Pipe
  • Editing your Event Pipe
  • Bulk Actions
  • Archiving and Unarchiving your Event Pipe
  • Deleting your Event Pipe
  • Metrics Tab

Was this helpful?

Edit on GitHub
Export as PDF
  1. Product documentation
  2. Monitoring

Event Pipes

Last updated 2 months ago

Was this helpful?

Our Event Pipes are used to collect data from all products on our platform. You can use this feature to keep track of everything that can cause an event at BMS, from campaigns to organization creation, allowing you to organize the provided data as you wish.

All event pipes created will be sent to either an Event Store, or you can use a webhook to send this data directly to your data management tool. We provide templates for every event that we can track so you can pick which you want to collect data.

We have a solution that may help you understand how a webhook works, check this article .

Creating an Event Pipe

To create an event store, click on , and an event pipe creation screen will pop up.

  • Name - Set a name for your Event Store.

  • Tags - Create tags to better identify each event pipe.

Filters

To start configuring your event pipe, pick a template of your choice in our Filters tab according to your needs.

  • Sample Event Template - In this dropdown menu, you will be provided with all templates related to the events that we can track.

In this example, we will be creating an event pipe for ADS - Delivered. This event tracks every Ad that is currently running in a campaign and is delivering impressions. Once we create this event pipe, all data will be sent to an Event Store or a Webhook.

Once we have the template selected, you can check which data will be collected when creating the corresponding Event Pipe.

  • Path - Specific tag in which you can identify the event. Ex: id, type, source, data.accountId.

  • Operator - Rule that will be used on this filter.

  • Value - The specific value the tag must contain.

In this case, we will be collecting data from ad-delivered events, so this is how the configuration would look.

We specified the Path using the tag "Type", chose the Operator option to "Contains" and added the Value "Ad-delivered". Note that these fields are case sensitive, so the fulfilled fields must match the template.

In this case, our filter failed due to verification in our Value field. These fields are case-sensitive and must match the corresponding information.

Targets tab

Here you will decide where to send the data: whether it will be sent to one or multiple event stores, a webhook, or a Google Sheet.

Event Store

If you decide to send your data to an event store, simply name your target and choose your already created event store.

It is possible to send your data to a webhook, provided by your data management tool, this is an option if you already have a data management tool of preference.

  • Name your target.

  • Select "Send to Event Store".

  • Select the event store you are willing to use.

Call Webhook

It is possible to send your data to a webhook provided by your data management tool, select this option to use the data management tool of preference, and then fill out the details.

  • Name your target.

  • Select "Call Webhook".

  • Insert your data management tool's webhook URL.

  • Payload - Information that will be sent to your webhook.

  • Result - Status returned and the latency.

  • Request - Request used by BMS to send you the information for this test.

  • Response - Received response from your webhook.

Google Sheets

You can also send your data to Google Sheets, select this option, and fill out the details.

  • Name your target.

  • Select "Google Sheets".

  • Connect with your Google Account, and you can access the sheet.

Enabling your Event Pipe

Editing your Event Pipe

Bulk Actions

When selecting two or more event pipes, the Bulk Actions will be enabled, allowing you to make actions in bulk.

You will be capable of Archiving and Deleting events in bulk.

Archiving and Unarchiving your Event Pipe

Deleting your Event Pipe

We advise users to archive instead of deleting, only delete if you are sure of it, the action cannot be undone.

Metrics Tab

Select an event pipe to access its metrics, selecting more than one will show you a comparison between the selected ones, the metrics are populated once you have created event pipes and they are enabled and collecting data.

These are all the metrics for event pipes:

Here you will decide where to send the data: whether it will be sent to one or multiple event stores or a webhook.

Event Store

You must create an event store before using it as a target for your event pipes.

  • Name your target.

  • Select "Send to Event Store".

  • Select the event store you are willing to use.

Call Webhook

It is possible to send your data to a webhook provided by your data management tool, select this option to use the data management tool of preference, and then fill out the details.

  • Name your target.

  • Select "Call Webhook".

  • Insert your data management tool's webhook URL.

  • Payload - Information that will be sent to your webhook.

  • Result - Status returned and the latency.

  • Request - Request used by BMS to send you the information for this test.

  • Response - Received response from your webhook.

To collect the data, we must insert a filter, by clicking on .

Once you have fulfilled all fields with the corresponding information based on your event pipe, the test filter must have a check confirming that it is working properly . If it is not working properly due to missing information or a typo, it will be presented with a warning sign .

Once you have added your filters, click on to save your event pipe.

To configure a target, click on and fill out the details according to the chosen target option:

You must create an event store before using it as a target for your event pipes. Learn more about .

After making all necessary changes, click on to create your target.

Once everything is configured, click on and your event pipe will be listed.

Click on to save your target.

Once you have configured your webhook URL, use our Test Webhook tab to confirm the usability of your webhook tool. Select one of the sample event templates and click on .

If your webhook test is successful, your icon will be presented as and the tabs for your test will be fulfilled.

After finishing all configuration and tests, click on to save your target.

Click on to save your target.

To enable an event pipe simply flip the toggle and your event store will be enabled.

To edit your event store, click on and an editing screen will pop up, make the necessary changes and then click on .

To archive your event pipe, click on and it will be sent to the archived list. In order to unarchive your event pipe, switch your view to archived events by flipping the toggle . You will then be presented with the list of archived events. Click on to unarchive an event pipe.

To delete an event, click on and a confirmation will be required.

After clicking on , your event pipe will be deleted.

To configure a target, click on and fill out the details according to the chosen target option:

Learn more about .

Click on to save your target.

Once you have configured your webhook URL, use our Test Webhook tab to confirm the usability of your webhook tool. Select one of the sample event templates and click on .

If your webhook test is successful, your icon will be presented as and the tabs for your test will be fulfilled.

After finishing all configuration and tests, click on to save your target.

Event Stores
Event Stores
here
Matched Events Count
Target Execution Call Count
Target Execution Failure Rate
Event Pipe Creation
ADS - Ad Delivered Event Pipe
Adding Filters
Event Pipe Filter Settings
Test Filter Warning
Event Pipe's Targets Tab
Event Store Target
Call Webhook Target
Call Webhook Target
Google Sheet Target
Event Pipe Enabled
Event Pipe's Edit Screen
Event Pipe's Bulk Actions
Event Pipe Deletion
Event Pipe's Targets Tab
Event Store Target
Call Webhook Target