Hi @AJ_Kakrot , you’re not missing anything obvious. This is one of those areas where HubSpot’s Ads tool is still opinionated about where that data lives.
Natively, HubSpot treats Meta campaign, ad set, and ad name as Ads interactions, not first-class contact properties. That’s why you can see them clearly in the timeline but can’t reference them in workflows or reports. The only pieces that HubSpot intentionally promotes to properties are the Original source drill-down fields, and as you noticed, those usually stop at the campaign level for Meta Lead Ads. Ad set and ad name are not persisted anywhere else by default.
As of now, there is no native switch to “promote” Ads interaction metadata into contact properties at creation time. This hasn’t changed in 2025. HubSpot’s own attribution model assumes that deeper ad metadata is for analysis inside the Ads tool and attribution reports, not for operational automation. That’s the product boundary you’re hitting.
The two practical workarounds I’ve seen teams use are:
First, push the metadata in at the form level. For Meta Lead Ads, you can add hidden fields to the lead form and map campaign, ad set, and ad name directly from Meta into HubSpot contact properties. This is the cleanest option if you control the Lead Ad form setup, because the values arrive as normal properties and are usable everywhere. HubSpot documents how Ads and form attribution work here (Connect your Facebook ad account to HubSpot )
Second, if you’re on Operations Hub Pro or Enterprise, use a custom code workflow. You can listen for contacts created from Meta Lead Ads, pull the most recent Ads interaction via the APIs, and write those values into custom contact properties yourself. It’s more work, but it’s the only way to backfill timeline-only data into properties after the fact.
If long-term attribution and routing depends on ad set or ad name, I’d strongly recommend the hidden-field-on-the-lead-form approach. Once the data is only in the timeline, HubSpot doesn’t give you a native way to operationalize it.
Hope this helps clarify the limitation and the realistic paths forward.