1. Why should I migrate to Klaviyo V3?

We upgraded the connector to the latest API revision. Key tables such as profiles and segments_by_profile now run as incremental loads, cutting processing time and warehouse costs. All future table additions and API revisions will ship only in this version.

2. Why is a lookback window needed for attribution events?

Klaviyo informed us that attribution fields such as placed_order can take up to five hours to update. Without a lookback window, Daton may miss these late updates. The window tells Daton how far back to re-fetch data each run. We suggest six hours.

3. How can I add metric-events beyond the standard ones in Daton?

If the standard events do not meet your needs, or if you want all metric-events in one table, choose the events table and select every metric you require in the final step.

4. Can I edit and add more metrics to the events table?

Yes. You can edit the integration and add metrics at any time. But to load historical data for the new metrics, you must reload the table. If you remove the table, Daton clears your metric selections, but your warehouse data stays intact. Adding the table again requires reselecting metrics.

5. How does incremental behaviour work for profiles, segments_by_profile, segments?

We will load the complete historical data first and then start the incremental approach for following tables

• profiles
• segments_by_profile
• lists
• flows

6. How does incremental behavior work for campaigns, campaign_messages?

The following tables fetches only new and updated records starting from a configured historical start date.This ensures faster syncs while keeping data fresh and accurate.:

• campaigns
• campaign_messages

7. What if I need historical data for above tables from before the configured start date?

If you require older data (beyond your configured start date), we can perform a one-time rollback to allow the system to refetch the historical range you need.

To request this, contact us at support@sarasanalytics.com.