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.