June 2026

---

Connector updates

Pinterest Ads: OUTBOUND_CLICK metrics and country-targeting reports

The Pinterest Ads connector adds two new OUTBOUND_CLICK metrics (OUTBOUND_CLICK_1, OUTBOUND_CLICK_2) to ad, ad_group, campaign and ad_account report schemas, and introduces country-level targeting report streams for ad accounts, ad groups and campaigns. Targeting reports expose TARGETING_TYPE and TARGETING_VALUE (e.g. COUNTRY) so you can sync country-level targeting metrics into your warehouse.

Meta: Graph API v25 Metric Deprecations (Facebook Pages & Instagram)

On June 15, 2026, Meta is retiring a set of legacy reach / impressions / 3-second-viewer metrics across all Graph API versions and replacing them with new Media Views / Media Viewers metrics. We've updated the Facebook Pages connector to stop requesting the retired metrics (so syncs don't fail) and to start collecting the new replacements. Separately, three Instagram Business reach columns are now nullable. Facebook Ads is unaffected.

Facebook Pages

The Facebook Pages insights tables store one row per metric — a name column holds the metric name and a value column holds its value. No columns are added or removed; instead, the set of metric names that appear changes.

New replacement metrics (Media Views / Media Viewers). These appear as new name rows in the same tables, replacing the retired reach / impressions / 3-second-viewer concepts.

Instagram Business

The following columns on the user_insights table changed from non-nullable integer to nullable integer, keeping syncs resilient when Meta returns no reach value for a period. This is a backward-compatible (widening) schema change — no primary-key or table changes were made.

Klaviyo: SMS Metrics on Campaign & Flow Reports

The Klaviyo connector now offers four additional SMS / text-message statistics when you build a Campaign Values or Flow Values custom report. These let you analyze text-message performance and ROI alongside your existing email metrics.

The new statistics simply become selectable when configuring a Campaign Values or Flow Values report in your Klaviyo source settings.

HubSpot: Property History for Custom Objects

The HubSpot connector now exposes a property history stream for custom objects. Previously, property history was only available for built-in objects (contacts, companies, deals, tickets, products). Now every custom object type gets its own history stream.

For a custom object named my_object, a new my_object_property_history source stream becomes available. Each row captures a single change to a single property — letting you track how any property value evolved over time, rather than only the current state of the record.

Schema — the property history table contains: <object>_id (the object's HubSpot ID), property, value, timestamp, and source_type. The primary key is <object>_id + timestamp + property + source_type.

Gorgias: Custom Reports

The Gorgias connector now supports custom reports powered by the Gorgias Reporting Statistics API. In your Gorgias source settings, a new "Reports" section lets you build any number of report tables by picking a scope, measures, dimensions, a time dimension and a granularity. Each report you configure becomes its own report_<snake_case_name> source stream.

This makes it possible to pull the same numbers that drive the Gorgias native dashboards — including metrics that aren't derivable from the raw ticket table — straight into your warehouse. Supported scopes include ticket-handle-time, first-response-time, resolution-time, tickets-created, tickets-closed, satisfaction-surveys, messages-sent, messages-received, AI Agent metrics, AI Sales Agent metrics, and more.

How it works

• The primary key of each report table is the selected dimensions plus the time bucket, so re-pulls merge deterministically.
• Granularity options: hour, day, week, month.
• Initial sync backfills 365 days; subsequent runs re-pull a rolling 90-day lookback once per day to capture late-arriving aggregations (e.g. tickets that get reopened and re-closed).

Gorgias: Per-Event-Type Tables

The Gorgias connector now supports syncing individual event types as separate, append-only tables. In your Gorgias source settings, a new "Include event tables for specific event types" multi-select lets you pick the event types you care about (e.g. ticket-closed, ticket-reopened, ticket-created). Each selection adds a new event_<event_type> stream — for example, selecting ticket-closed creates an event_ticket_closed table.

This solves a key limitation of the existing ticket table, which only reflects current ticket state. Because fields like closed_at are overwritten on each state change, historical close events are lost — making resolution-time metrics drift from the Gorgias native dashboard. The new event tables preserve the full append-only history, so you can accurately compute "first closed at" or per-period close counts that match what Gorgias reports natively.

Schema — all event_<event_type> tables share the same shape: id, created_datetime, type, object_type, object_id, account_id, user_id, and data (full event payload as stringified JSON).

Stripe: Inactive Prices Stream

Stripe now has a dedicated price_inactive stream for syncing archived (inactive) prices — prices where active is set to false.

Previously, the price stream only fetched active prices. The behavior of the existing stream is unchanged:

• price — continues to sync only active prices (no change)
• price_inactive (new) — syncs only inactive/archived prices

The new stream supports both full and incremental sync, and includes a price_inactive_tier sub-stream for tiered pricing data, mirroring the existing price_tier sub-stream on the active prices stream.

YouTube Analytics: Report Version Migration

YouTube Analytics bulk reports have been updated to new versions. All updated reports now include the new engaged_views metric and use YouTube's latest view-counting methodology. See the YouTube Reporting API revision history for the full upstream changelog.

New metric

The engaged_views column is now available on all updated bulk reports. It reflects the previous view-counting methodology, making it useful for maintaining historical comparisons now that YouTube has changed how views are counted.

New Reach reports

Two new Reach reports are now available:

Reports updated to a new version

The following reports were bumped to new versions. They include engaged_views and use the updated view-counting methodology. See the official channel reports reference and content owner reports reference for the full field definitions.

Reports removed

YouTube deprecated the previous channel and playlist report versions on June 24, 2025, and fully removed them on June 3, 2026 — as documented in the revision history. These reports have been removed from Weld as well. If you were syncing any of these, switch to the corresponding new version listed above.

Reports kept as deprecated

The following report versions were announced as deprecated by YouTube but have not yet been removed. They remain available in Weld so existing syncs continue to work, but are now marked as deprecated. We recommend migrating to the latest versions when convenient: