Square Booking flow loses URL parameters (e.g., gclid) on redirect, making reliable cross-domain conversion attribution impossible

[dylan]

Hi Bryan, thanks for the response.

I understand that I can build a custom booking site with Square APIs (which I already did), but I’m now facing another issue:

When I create a booking via the Bookings API, the confirmation email is only sent to the customer, not to the business owner. And I think someone else have this issue too

"Booked By'/creator_details field in API bookings

Hi there, I’m having some trouble with my booking implementation with Square’s API. Through my web app, when I create a booking with bookings.create({bookingRequest}), the creator_details field (Read-Only) sets the details to be such that the person who booked the appointment is the Owner of the Square account, rather than something like having the creator_type be “CUSTOMER”, or even the Team Member that it is booked with. The reason this is an issue for me, is because normally when a service…

On Square’s first-party booking site, the owner normally receives a “new booking” notification. However, for API-created bookings, this doesn’t seem to happen.

This is important for us operationally, since we need to be notified immediately when a new appointment is created.

Thanks!