Here's an example and real case scenario:

www.example.com/s/somepage?query=12345 (The page I want people to land on)

The front-end setup is using community pages


www.example.com/somepage redirects to www.example.com/s/somepage?query=12345

www.example.com/s/somepage redirects to www.example.com/s/somepage?query=12345

www.example.com/somepage?fbclid=facebooksannoyingtrackingid does not redirect to the correct page and hits a force.com "page not found" error

What is the best way to mitigate against facebook tracking params / any tracking params..

| improve this question | | | | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.