Skip to main content

Hi! My business uses Boulevard for client appointment bookings and we just started using Klayvio for email and SMS marketing. We do not have the Boulevard API plan which transfers over all information automatically between the two platforms. I do everything manually 1-2x per week (transferring over client names, emails, phone numbers, and email/sms consent status - they consent to receive messaging from us via Boulevard when booking). 

 

I am going to frame my question as a hypothetical situation to best describe the scenario:

Someone booked an appointment week of January 1st, so in my transfer batch that week, I get their info over to Klayvio. When they initially booked, they did not consent to receive SMS marketing (which reflects in the info I transferred). They then rebook in July, but this time they consented to SMS marketing. Their name, email, phone  number, etc is all the same, only thing that changes was this one piece of info. 

 

Will Klayvio recognize this profile and automatically update their old contact/profile info with the new data transfer? Or will it see that it is essentially a duplicate email and ignore the whole thing? I need to make sure contact info is able to be updated in my data transfers between the platforms. 


Thanks!

@kaylaz unless you are importing the contacts and including an extra external_id column, profiles having the same email address and phone numbers will be merged into one.  Klaviyo essentially treats email and phone number as primary keys.


Like ​@whereisjad said, unless you are importing the contacts and including an extra external_id column, profiles having the same email address and phone numbers will be merged into one.

Klaviyo essentially treats email and phone number as primary keys.

This means in your hypothetical situation, Klaviyo should recognize the profile based on the email and phone number and update the SMS consent status with the new information when you manually transfer it.

While manual transfer works, the best long-term, scalable, and most reliable solution to ensure real-time data accuracy is to use the Klaviyo API in conjunction with the Boulevard API, mediated by a service like Google Tag Manager (GTM) and a server-side tagging solution like Stape or Google Cloud Platform (GCP).

Using the APIs allows for an automated, event-driven integration.

When a client books or rebooks in Boulevard, a webhook could be fired (if available through the Boulevard API) or a query can be set up to regularly pull new/updated data.

This data transfer is then routed through GTM.

GTM, specifically its server-side container, acts as a central hub where the raw data from Boulevard is transformed and mapped precisely to Klaviyo's profile properties and events.

For instance, the rebooking in July could trigger an immediate update to the client's profile in Klaviyo, changing the SMS consent status, and also potentially triggering a custom event like a Booked Appointment or Updated Profile.

Stape or GCP are necessary here to host the server-side GTM container, which is critical for securely handling and processing the sensitive client data before sending it to Klaviyo's API.

This server-side approach minimizes reliance on client-side browser tracking, offering better data accuracy and security.

This setup not only guarantees profile updates, including consent status, but also enables rich segmentation and flow triggering in Klaviyo based on real-time actions and changes in Boulevard, going far beyond just basic contact transfer.

This automation eliminates the risk of human error and ensures your marketing always respects the client's current consent preferences.