Native connection and data coverage
We inspect the Shopify app connection, its permissions and synchronization settings. The scope identifies the customer and order information needed in Klaviyo and checks representative records against the store.

Connect Shopify and Klaviyo with verified customer profiles, store events and subscription settings. We review the native connection and any existing tracking, then check the data your marketing team will rely on before new flows are activated.
We agree on the records, fields and operating rules before connecting Shopify and Klaviyo. The scope below defines the work to review together.
We inspect the Shopify app connection, its permissions and synchronization settings. The scope identifies the customer and order information needed in Klaviyo and checks representative records against the store.
Theme code, app embeds and older marketing integrations can overlap. We review the active tracking routes and verify the events available under the store’s consent setup instead of assuming every visit is identifiable.
Customer import, email subscription and SMS permission are different concerns. We review historical synchronization, selected lists and any return-sync options, including their effect on existing profiles and live flows.
Provide the Shopify store, Klaviyo account and existing integration inventory. We verify the permissions and current connection options before changing a working app or removing older code.
Identify active campaigns and flows, their triggers and the list used for new subscribers. The release plan controls whether newly synchronized or historical activity can enter those flows.
Confirm checkout opt-in behavior, sign-up forms and the system responsible for each profile field. The connection does not provide a blanket consent determination or promise higher revenue or deliverability.
Compare Shopify customer and order samples with Klaviyo records. Identify missing data, duplicate events and older integrations before choosing the changes.
Apply the agreed native settings and check profiles, supported events and subscription states. Test opted-in and non-subscribed customers with approved test data.
Review historical data and flow exposure, then verify current activity after release. Hand over tested events, field ownership, consent settings and checks for future theme or app changes.