{"section":"tutorials","requestedLocale":"en","requestedSlug":"bridge-logs-data-pipeline","locale":"en","slug":"bridge-logs-data-pipeline","path":"docs/en/tutorials/beta/vtex-data-pipeline-beta/bridge-logs-data-pipeline.md","branch":"main","content":"The `bridge` dataset includes historical information on Bridge logs. \n\n> ⚠️ Currently, the dataset only provides tracking and canceled order log information.\n\nThis section includes the following information:\n\n- [Bridge data characteristics](#data-characteristics)\n- [Table: order_status_change](#table-order-status-change)\n- [Analyses with bridge data](#analyses-with-bridge)\n- [Correlations with other data](#correlations-with-other-data)\n\n## Data characteristics\n\n| **Characteristic** | **Description** |\n|:---:|:---:|\n| Data source | Obtained from information in the Bridge module. |\n| Availability | VTEX Admin. |\n| History | Data is maintained for two years, starting in 2024 for customers already using the VTEX platform. |\n| Minimum update interval | One hour. |\n\n## Table: order_status_change\n\nThe table fields are described below:\n\n| **Column name** | **Column type** | **Column description** |\n|:---:|:---:|:---:|\n| main_account | character varying(100)\t | The VTEX main account associated with this account. |\n| account_name | character varying(100) | Name of the store or child account responsible for the order. |\n| marketplace | character varying(50) | The name of the marketplace from where this order originated. |\n| bridge_order_id | character varying(300) | Order Identifier sent by the marketplace. |\n| vtex_order_id | character varying(300) | The ID of the order on VTEX's OMS. This is usually the marketplace order ID with an affiliated ID prefix. |\n| marketplace_order_id | character varying(300) | The ID of the order on the external marketplace. |\n| bridge_log_type | character varying(25) | Indicates whether the update is from an order event (order input or approval) or tracking event (invoice, delivery status). |\n| bridge_log_status | character varying(25) | Indicates the status of the log entry. The possible statuses are success, warning or error. |\n| bridge_log_message | character varying(65535) | The message visible to the merchant in the bridge. |\n| update_timestamp | timestamp without time zone | The time when the integration processed the update. |\n| batch_id | character(13) | The ID of each batch of data. Keep in mind that this table has updates in its rows, which causes their batch_id to be bumped at the time of the update. |\n\n## Analyses with Bridge\n\nHere are some of the analyses you can perform using the Bridge table:\n\n- **Analysis of Marketplace Orders:** Understand the logs associated with your orders from external marketplaces.  \n- **Insight into External Marketplace Logs:** Conduct batch analyses on messages from external marketplaces related to order tracking and cancellations.  \n\n## Correlations with other data\n\nBridge data closely ties with order data, providing a comprehensive analysis of purchases and sales. Here are an examples:\n\n- **Comprehensive analysis of orders made through external marketplaces:** Integrating this data model with the orders data provides a complete view of orders sold via Marketplace Out scenarios. Use the order_id to join both tables.\n\n### Discover other Datasets\n\n- [Catalog](/en/docs/tutorials/catalog-data-pipeline)\n- [Inventory](/en/docs/tutorials/inventory-data-pipeline-beta)\n- [Navigation](/en/docs/tutorials/navigation-data-pipeline)\n- [Payments](/en/docs/tutorials/payments)\n- [Orders](/en/docs/tutorials/orders-data-pipeline-beta)\n- [Promotions](/en/docs/tutorials/promotions)\n- [Gift cards](/en/docs/tutorials/gift-card-data-pipeline)"}