Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Expose Alternate Tracking ID and Tracking URL

Answered
vishal khode User

Table name:
shipment_shipping_label

Columns to add:

  • alternate_tracking_id
  • tracking_url

API documentation link:
ShippingLabel | ShipHero GraphQL API

Additional details:

We would like to request that the existing alternate_tracking_id and tracking_url fields from the ShipHero ShippingLabel API be exposed in the Fivetran shipment_shipping_label table.

Both fields are already available directly on the ShipHero GraphQL ShippingLabel object. The API documentation identifies alternate_tracking_id as the public API alternate tracking ID associated with the record and tracking_url as the URL for tracking the shipment.

These fields are important for our Monthly Shipping / Shipment Reports:

  • alternate_tracking_id is required because some shipments may have an alternate tracking identifier in addition to the primary carrier tracking number. This allows us to preserve and report the complete shipment tracking information available in ShipHero.
  • tracking_url is required so users can directly access the carrier/shipment tracking page from our reporting without having to manually construct a tracking URL based on the carrier and tracking number.

Having these fields directly available through Fivetran will allow us to reproduce ShipHero's shipping data more accurately and avoid maintaining custom logic in BigQuery to derive tracking information.

Requested change: Please expose the existing alternate_tracking_id and tracking_url fields from the ShipHero ShippingLabel API in the corresponding Fivetran shipment_shipping_label table.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Syead Mujtaba Imam Rizwi Fivetranner

    Hi Vishal,

    Thank you for the request to expose the alternate tracking ID and tracking URL fields on the shipment shipping label table. We have added this to our active backlog and confirmed both fields are available on the source data. Could you share more about how you plan to use the tracking URL, for example whether it needs to link directly from a dashboard? We will keep you updated on this thread as we make progress.

    Best,
    Syead Mujtaba Imam Rizwi

  • vishal khode User

    Hi Syead,

    Thanks for the update.

    Regarding the alternate tracking ID and tracking URL, we need both fields as part of our Monthly Shipping Report.

    The alternate tracking ID is required to capture the shipment's tracking reference and use it for shipment-level identification and reconciliation.

    The tracking URL would be used to provide a direct link to the carrier's tracking page from our downstream reports/dashboard. This allows users to quickly access the shipment tracking information when reviewing a shipment.

    Our expected use is:

    • Alternate Tracking ID → included as a tracking/reference field in the Monthly Shipping Report.
    • Tracking URL → included as a clickable URL in the downstream report/dashboard so users can directly access the shipment tracking page.

    We would therefore need these fields exposed from the Shipment Shipping Label data and associated with the relevant shipment/shipping label.

    Please let us know if you need any additional details or examples from our Monthly Shipping Report.

    Thanks,
    Vishal Khode