1

Hello,

I have a page that displays a list of records.

I pass a paragraph and the user’s email to this page.

It works normally, it only fails when I need to capture this parameter to pass it as a link to share on social networks, Facebook for example.

Search for the table first item field

Constrant:
Field= Get fro page url
Parameter name

It doesn’t bring anything from the record.

Thanks

Dirceu M. Azevedo

1 Like
2

Hey Dirceu,

It seems like a small issue with passing parameters in the URL. Make sure the field you’re trying to capture is actually present in the URL when creating the link for social media sharing. Sometimes, sharing tools (like Facebook) don’t always pick up the parameters in the URL correctly. Try adding a small delay or check if the parameter is properly passed in the URL before sharing.

Hope this helps! :blush:

Good luck,
Hans

3

Good point, @hpelenga ! Sometimes social media platforms don’t handle URL parameters the same way, so checking how the link is being generated and shared is important. Also, @dirceuazevedo , you might want to use debug mode in Bubble to see if the parameter is actually being received. Hope it helps!

1 Like
4

Hello, If I simply read a record from the database without passing any parameters, Facebook accepts it. But when I compare it with the email that comes as a parameter, it doesn’t bring anything. Even if I pass the email statically, nothing happens. Get from page url dirceuazevedo@gmail.com for example

5

Facebook might be stripping or blocking certain url parameters when sharing the link, which could be why the email parameter isn’t being recognized. Since reading directly from the database works without parameters, the issue is likely with how facebook handles the url when shared.

One workaround is to encode the email before passing it in the url. You can try using :formatted as text in bubble to Base64 encode the email before adding it as a parameter. Then, on the receiving page, decode it before using it in a search.

Another option is to store the email in the database when the user first lands on the page and then reference that stored value instead of relying on the url parameter. So, even if facebook alters the url, the app can still retrieve the correct user data.

If facebook is blocking emails in the url for privacy reasons, you might need to pass a unique id instead of the email, then use that id to find the corresponding record in the database.

6

Thank you for your reply.

Problem solved.

Just check the following in the consultation:

  • Ignore empty restrictions

This way it works perfectly.

Thank you,
Dirceu Martins de Azevedo

1 Like