I want to enroll contacts in a workflow based on the ‘Website URL’ of the ads.
There are native enrollment triggers based on ad names and ad IDs. But there’s apparently no filter based on ‘Website URL’ in those ads.
Context:
There are about 1800 ads in our HS. And about 100 of them have a download link for a specific PDF - these are in the ‘Website URL’ field in those ads.
Rather than going through each of the 1800 ads individually to figure out ad names or IDs of the 100 that have that ‘Website URL’, I was wondering if there’s any quick way to filter contacts based on an enrollment criterion like “‘Website URL’ of the ad contains that specific PDF”.
Any suggestions or workarounds are welcome. Because I really do not want to go through each of the 1800 ads individually.
You have a “page viewed” filter in HubSpot, but that ignores any UTM parameters so you wouldn’t be able to distinguish between someone who arrived on this page from a LinkedIn ad or via any other means.
What’s the ultimate goal of the workflow?
How are the ads setup - I see the ad, click, arrive at the PDF?
The ads are exactly as you mentioned - see ad, click download, get PDF.
The page viewed properties are not really usable, because HubSpot only houses first and last seen pages. And these ads are from a year back, so they may not always be the first or last seen pages.
My last resort is going to be to manually look up and add the ad IDs of each of the 100 ads. But it would have been a lot easier if I could use the ‘Website URL’ as an ad interaction property instead of ad IDs.
I mean, with ad IDs, I’m going to have to add 100 values as workflow enrollment criteria - ad ID is any of the 100.
But if I could have used ‘Website URL’, I would have had to use just one value - ‘Website URL’ contains the PDF link.
In a list we would use the following filter to create contacts based on specific page view or URL which contain a certain path, i.e. www.companyA.com/productB.
The problem, if your process is “see ad, click download, get PDF”, is that the PDF doesn’t count as a page view, it’s simply a file that is being viewed. If there is an inbetween step, such as “see ad, click download, visit landing page, get PDF” we would be able to register the landing page view/visit.
