UTM tracking | Community
Skip to main content
A
Anonymous
January 15, 2018
Question

UTM tracking

  • January 15, 2018
  • 2 replies
  • 6618 views

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Dan_Stevens_
Dan_Stevens_
Level 10
January 15, 2018

Need a bit more info here.  Can you include a screenshot of your smart list?

A
Anonymous
January 15, 2018

Attached

keithnyberg
keithnyberg
Level 7
January 15, 2018

Hey Christina,

You're basically using 2 filters to distinguish the same thing. Remove both and add a filter for UTM_Source = Capterra.

Should fix this.

Sincerely,

Keith Nyberg

    keithnyberg
    keithnyberg
    Level 7
    January 15, 2018

    Hey Christina,

    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.

    Sincerely,

    Keith Nyberg

    Chelsea_Kiko
    Chelsea_Kiko
    Level 4
    January 15, 2018

    +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.

    Thanks!

    Terms & ConditionsAccessibility statement

    Loading footer...