“current_path” anomaly

  • Resolved jacobw201

    (@jacobw201)


    8 years, 8 months ago

    Hi guys! I’m re-opening this because I was remote for a bit, and the previous ticket (https://ww.wp.xz.cn/support/topic/current_path-anomaly/) got closed.

    I have a {current_path} hidden merge tag field (called “location”) in my signup form on my website. This is to track what page subscribers have signed up from. But somehow I just got a couple subscribers whose location field were set to:

    /?utm_source=13%20Moon%20Calendar%20Essentials&utm_campaign=7c202be7ae-EMAIL_CAMPAIGN_2017_08_31_IMadeABooBoo&utm_medium=email&utm_term=0_a6a82fa01a-7c202be7ae-112393901&mc_cid=7c202be7ae&mc_eid=2abddb8039

    and

    /?utm_source=13%20Moon%20Calendar%20Essentials&utm_campaign=433079cd51-AUTOMATION_Star_Traveler_s_Email_Course_1&utm_medium=email&utm_term=0_a6a82fa01a-433079cd51-112709297

    Seems really weird! These URLs are obviously links that appeared in a couple of my MailChimp campaigns. The first one was a campaign I manually sent to a segment, the second link is within an automation campaign.

    Any ideas as to what could have caused those links to be their “location” merge field, if that form ONLY exists on the MC4WP form on my website??

    Baffledly yours,

    Jacob

    PS: You replied saying that you couldn’t even access the “/” directory of my site. Turns out there was some HTTPS issues going on which are now resolved!

    PPS: On close inspection it seems that perhaps people click a link to my web-page via the newsletter itself, and that ends up as the URL. So when they sign up this populates. In light of this, there may not be a way around it?

    • This topic was modified 8 years, 8 months ago by jacobw201.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Lap

    (@lapzor)

    8 years, 8 months ago

    PPS: On close inspection it seems that perhaps people click a link to my web-page via the newsletter itself, and that ends up as the URL. So when they sign up this populates. In light of this, there may not be a way around it?

    That’s right. Someone visits your site via the campaign, and right when they enter this will be the URL that MailChimp sends them.

    The only way around it I think is some custom code that filters the source field and cuts off everything after the questionsmark. Custom code is out of scope for our free support, but here are some snippets to get a developer started: https://github.com/ibericode/mc4wp-snippets/blob/master/modify-data-before-sending-to-mailchimp.php

    Hope that helps!

    Kind regards,

    Thread Starter jacobw201

    (@jacobw201)

    8 years, 8 months ago

    Thanks, Lap! Curious if you’ve guys have considered a {page_title} hidden field for the MC4WP forms? What’s that?? You’re putting into the next update! AWESOME! 😉 Seriously, you guys rock, and this plug-in is uber useful… ubeful? Thanks again!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘“current_path” anomaly’ is closed to new replies.