Menu
Feedback
Start here
Tutorials
Developer portal

Known Issues
Support Rules
Troubleshooting

Frequently Asked Questions
Announcements
Tutorials
Tutorials
Explore in-depth tutorials for operating your VTEX store.
Tutorials
Beta
VTEX Data Pipeline Beta
Bridge Logs Data Pipeline
Bridge Logs Data Pipeline

The bridge dataset includes historical information on Bridge logs.

Currently, the dataset only provides tracking and canceled order log information.

This section includes the following information:

Data characteristics

CharacteristicDescription
Data sourceObtained from information in the Bridge module.
AvailabilityVTEX Admin.
HistoryData is maintained for two years, starting in 2024 for customers already using the VTEX platform.
Minimum update intervalOne hour.

Table: order_status_change

The table fields are described below:

Column nameColumn typeColumn description
main_accountcharacter varying(100)The VTEX main account associated with this account.
account_namecharacter varying(100)Name of the store or child account responsible for the order.
marketplacecharacter varying(50)The name of the marketplace from where this order originated.
bridge_order_idcharacter varying(300)Order Identifier sent by the marketplace.
vtex_order_idcharacter varying(300)The ID of the order on VTEX's OMS. This is usually the marketplace order ID with an affiliated ID prefix.
marketplace_order_idcharacter varying(300)The ID of the order on the external marketplace.
bridge_log_typecharacter varying(25)Indicates whether the update is from an order event (order input or approval) or tracking event (invoice, delivery status).
bridge_log_statuscharacter varying(25)Indicates the status of the log entry. The possible statuses are success, warning or error.
bridge_log_messagecharacter varying(65535)The message visible to the merchant in the bridge.
update_timestamptimestamp without time zoneThe time when the integration processed the update.
batch_idcharacter(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.

Analyses with Bridge

Here are some of the analyses you can perform using the Bridge table:

  • Analysis of Marketplace Orders: Understand the logs associated with your orders from external marketplaces.
  • Insight into External Marketplace Logs: Conduct batch analyses on messages from external marketplaces related to order tracking and cancellations.

Correlations with other data

Bridge data closely ties with order data, providing a comprehensive analysis of purchases and sales. Here are an examples:

  • 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.

Discover other Datasets

Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
Was this helpful?
Yes
No
Suggest Edits (GitHub)
Contributors
2
Photo of the contributor
Photo of the contributor
+ 2 contributors
On this page
Still got questions?
Ask the community
Find solutions and share ideas in the VTEX community.
Join our community
Request support from VTEX
For personalized assistance, contact our experts.
Open a support ticket
GithubDeveloper portalCommunityFeedback