How to Integrate Klaviyo with Reaktion Using API Key for Full Event Tracking

Modified on Wed, 4 Jun at 2:32 PM

If you have already integrated Klaviyo, but Reaktion Klaviyo tracking is not working, please check step #9 of this guide.

If Klaviyo has not yet been integrated, please start by


1. Going to Data sources in Reaktion and Add new Data Source


https://advertiser.reaktion.com/data-sources/select



2. Click Connect on the Klaviyo logo. 





3. Make sure to select the correct API permissions in Klaviyo.  

Read-Only access to everything and Full (Read/Write) Access to Events



 




4. Here is a Klaviyo guide on how to generate the API key in Klaviyo:


LINK: https://help.klaviyo.com/hc/en-us/articles/7423954176283



5. Copy the API key generated in Klaviyo.



6. Go back to Reaktion and paste your private Klaviyo API key in Reaktion:




7.    Click Install. We are now connecting to your Klaviyo account.


8.    We now start to pull all your Klaviyo data into Reaktion. This can take up to several hours.



9. If you have previously generated an API key in Reaktion, but without Full access to Events, please generate a new API key with correct permissions and update the Klaviyo data source settings in Reaktion: 


- Go to https://advertiser.reaktion.com/data-sources/overview

- Click Manage next to the existing Klaviyo data source, and then Settings

- Open Klaviyo and generate a new API key with Full access to Events


- Delete the existing API key and replace is with the newly generated key and click Save

- Reaktion Klaviyo tracking data will be available moving forward 


Please note that we currently support only mapping one Klaviyo account to one webshop. If you would like to add a second Klaviyo account and map it to other webshop(s) in a multi-store setup, you would need to add an additional Klaviyo data source and repeat the above steps with a new account. 

 





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article