Skip to main content

Integrate Klaviyo to my custom coded website on Bluehost

  • January 1, 2023
  • 1 reply
  • 138 views

Forum|alt.badge.img+2

I have a web developer that’s building my custom coded website on Bluehost, no Wordpress. He said when he attempted to integrate Klaviyo, that he received a message saying that my account needs to be verified to continue. I attached that message below that he sent me. At that pint he was listed as a manager in klaviyo but I did change his role to content creator. Since my website isn’t launched yet, I hadn’t upgraded but after this message I upgrade to a $15 a month plan as well in the process of trying to hurry up and get my account verified and integrated. I reached out to klaviyo yesterday and haven’t got any help yet but this is very urgent and needed to launch my website. Looking for urgent help, thank you. 

 

Did this topic or the replies in the thread help you find an answer to your question?

1 reply

Brian Turcotte
Forum|alt.badge.img+37

Hi @TayD and welcome to the Community!

 

May I ask what specific action your developer was using when the error occurred?

 

I’ve seen this issue before when trying to send emails with the Template API. This action has been disabled for security purposes until further notice, but the same use case can be accomplished using the Track API to send a custom metric that triggers a flow:

  1. Use the Track API to pass an event into your Klaviyo account. This event can have properties of its own as well as customer (recipient) properties. The data for these API calls must be encoded in base64 format - or you could make use one of our SDKs in Python/Ruby/PHP and NodeJS. All documentation about the track API as well as the SDKs can be found here: klaviyo.com/docs
     
  2. Create a metric triggered flow using this new custom event that got added to your account
     
  3. Use the template editor to add the custom fields data to your email
     
  4. Finish up setting the flow by using filters/conditional logic if necessary or just by setting the email to live or manual mode.

 

If this error is being seen in a different context, then would you be willing to provide some more context for myself and other Community members?

 

Thanks for using the Community!

-Brian