Relevant to:
- Admin Briq.app users
Briq offers the ability to send customers' personal information, such as their name and email address, to tracking partners. Only information from customers who have made a booking will be shared. The merchant must implement this themselves, and this article explains how.
⚠️ To legally send customers' personal information to tracking partners, two conditions must be met:
- The customer has explicitly consented to the forwarding of personal information to tracking partners, for example, by clicking “accept marketing cookies” in the merchant’s cookie banner;
- The data is stored in a hashed (not directly readable) form by the tracking partner.
⚠️ Note: The merchant is responsible for ensuring that customers’ personal information is processed correctly, as required by privacy regulations. Briq will never send personal customer information to tracking partners itself.
Sending customers' personal information to a tracking partner
Communication with tracking partners takes place via the dataLayer. All information in the dataLayer can be retrieved—e.g., via Google Tag Manager—and forwarded to Google Ads. To do this, use a Google Ads Conversion Tag with Enhanced Conversions enabled.
The Briq widget already adds standard information to the dataLayer, such as which deals and products are being viewed. However, the Briq widget does not do this for personal customer information. As a merchant, you can do this yourself by adding the window.onBriqWidgetBookingCreated JavaScript hook. This could work as follows:
<script type="text/javascript">
window.onBriqWidgetBookingCreated = function (customer) {
dataLayer.push({
event: "enhanced_conversion_data",
...customer
});
}
</script>
The enhanced_conversion_data event then contains the following (SHA256-hashed) information:
- firstName (string)
- lastName (string)
- email (string)
- mobile (string)
- newsletter (boolean)
⚠️ Note: If the JavaScript hook exists, Briq will call it after a booking is made. Therefore, ensure this script only exists if the customer has given consent, for example via the cookie consent banner.
⚠️ Note: The JavaScript hook must exist only once. If the hook is defined multiple times, only the last one will be called.
Should you have any questions about this topic, please do not hesitate to contact us at support@briqbookings.com or in the chat in Briq.app.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article