Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

We currently have a Zapier App (screenshot attached). The issue lies in when a user clicks on the blue “Click here to learn more“ link in the New Participant Reward event.

The issue: The webpage is naively appending a ?from_url URL parameter to the click, but hashes aren’t factored in. This ends up with a malformed URL, and the user isn’t directed to the appropriate anchor upon landing on the webpage.
 


This is the original URL that we want users to go to:
https://site.com#hash

But this is what Zapier is turning the URL into:
https://site.com#hash?from_url=ANYTHING

 

This is what we would expect Zapier to turn the URL into:
https://site.com?from_url=ANYTHING#hash


Unfortunately, this is an issue that I haven’t been able to make any sort of workarounds whatsoever (DNS, server-side, and third-party tool).

 

Any thoughts, Zapier Dev team? Does this look like a bug?

 

Thank you

@kevinsy that is frustrating and indeed is an unintended consequence. I’ve escalated this to Zapier’s support team. Hopefully, they’ll chime in here quickly

Hi @kevinsy!

That definitely seems like a bug, and an unfortunate one since I can’t think of a way for you to get around it behaving that way. I’m going to file a bug report for this and add you as an affected user. You’ll be notified when that’s been resolved!

In the meantime, the way you’ve done it, specifying which section to check, is about the best workaround I can think of.

Thank you both! @nicksimard @PaulKortman 

Terms & Conditions