Skip to main content

Hi, we want to start using klaviyo with a mobile App. Our first task is to use the API to synchronize the changes of the users of our server to a contact list in klaviyo.

Our plan is to use it from the server (with PHP) so as not to depend on publishing the App with each change.

Specifically we intend to use the API to maintain an updated contact list in Klaviyo with create / update customer profiles every hour.

Can our marketing department still use klaviyo with these updated lists without using real-time user action events?

Do we lose a lot of important klaviyo functionality if we discard using real-time event tracking?.

Our idea is not to load the server too much and to make the implementation of the klaviyo service easier.

Our users can buy a subscription and later cancel it or continue renewing and contact lists in klaviyo would be updated with dates of renewal or cancellation or registration of a new user in the App from time to time but not in real time. 

Do you consider this to be a misuse of klaviyo? Would this list be filled in more unusable by our marketing department when configuring campaigns and flow in klaviyo or would klaviyo still be a useful tool for marketing and mailing without using the tracking profile activity in real time of the users of the App?

We do not want to do the work and then this other level of synchronization is needed, we must consider it for the budget if it is really a must be.

Thank you, best regards

Hello @I3NET,

Thank you for sharing this with the Klaviyo Community.

Although real-time actions (events) are an important part of Klaviyo, you can still use Klaviyo effectively without using real-time action events. For example, you will still be able to dispatch campaigns (which do not require real-time events to work) and most types of flows, including list and segment-triggered flows. Editing and designing email templates, product feeds and recommendations and many other product areas will still be useable and effective without real-time event tracking. As long as your emails for renewal/subscription/cancellation are not time sensitive, you do not need to worry about real-time event tracking. However, if those emails or any other emails are time-sensitive, I recommend using the Track API to send emails via an event-triggered flow to track user renewal/cancellation/ registration in real time. This will be important to ensure those users get those emails at an appropriate time. Additionally, you can look into using date-triggered flows for date-related events. For information on updating profiles, see our Identify API documentation.

Overall, Klaviyo will still be a great tool for marketing and emailing users without real-time event tracking, but you need to keep in mind if you have time-sensitive emails that need to be dispatch when someone takes an action (what we call metric-triggered flows), you’ll likely want to use real-time event tracking in these circumstances.

I recommend browsing our help center for more information on our product areas.

Thanks for being a member of our community.


Reply