I have this URL built www.mineraltree.com/products/ap-automation-demo?utm_source=capterra and I have a campaign that says if any form is filled out and web page querystring contains Capterra OR referrer contains Capterra. Then add to campaign and sync to SF campaign.
It is not working. Any ideas? I cant add it at the form level since our forms are embedded on Wordpress pages so the utm has to be in the unique url.
You're basically using 2 filters to distinguish the same thing. Remove both and add a filter for UTM_Source = Capterra.
Should fix this.
You might be over-thinking this a bit. Why not just use a single trigger with the querystring and referrer constraints? NOTE: the "referrer" when used with this trigger, refers to the page that submitted the form.
The "Visited Web Page" filter can take significantly longer for Marketo to log this activity - so I tend to avoid this sort of approach. Meaning, someone who's never visited the page and submits the form will never proceed through this campaign - since the filter won't qualify the lead.
Do it the way Dan says. You can't filter on something that may not have been logged yet, so you must not attempt to use the VWP for the same page the form was on.
Maybe remove the constraint on your fills our form trigger and simply add a filter for UTM_Source = Capterra, then proceed to the flow step. This will trigger on any form fill, then look to ensure the UTM_Source is capterra before proceeding to the flow steps. Not as ideal as the process you outlined as that wont get triggered everytime, but only when appropriate. (could be a cool idea to add a custom field constraint to the fills out form trigger like UTM values)
Important to verify that your UTM parameters are being captured in Marketo on form submit as if not done correctly, could be the problem. Double check by submitting a test record and verifying the UTM source = Capterra. If that doesn't work and the field is not populated, double check how you are pulling UTM parameters into your form (via URL parameter, cookie, etc) and then correct.
My gut is that the query string constraint may not be as bulletproof as just using a filter for your utm value. So you could always submit a ticket to support and get their take on why that functionality isnt behaving as expected.
+1 to what Keith said. I was going to tell you the same thing, we always add the utm_source= filter as it closely examines that certain piece of data. Adding a query string 'catch' in my opinion won't always work the way you want it and you want to pay attention to the utm_source= filter anyway for reporting. If it isn't working properly, you'd want to know for reporting purposes.