Endpoint
Parameters
Guest attribution with custid
When DialogShift sends a guest into the booking flow, it appends a custid parameter to the URL (e.g. …?…&custid=c8f2a1). Read this value from the requested URL, keep it throughout the entire booking flow and return it as custid in the pixel call. DialogShift then attributes the booking exactly to this guest.
Without custid, attribution relies on fingerprinting and is much less accurate.
Implementation
Option A: Tracking pixel in the browser
Add a hidden image to the confirmation page. Insert the values from your booking:Option B: Call the endpoint directly
Call the same URL server-side viaGET as soon as the booking is confirmed:
With a server-side call, DialogShift receives your server’s IP, not the guest’s. Therefore always include
custid – otherwise DialogShift cannot attribute the booking.
