Connect WooCommerce store activity to Klaviyo with checked customer records, shopping events and consent settings. We review the existing extension and tracking setup, then verify which information reaches Klaviyo and where gaps or duplicate events need repair.
We agree on the records, fields and operating rules before connecting WooCommerce and Klaviyo. The scope below defines the work to review together.
We inspect the supported WooCommerce connection and identify the events your marketing team needs. A test order is traced against the events actually available, including the distinction between server-side store activity and browser tracking.
Product identifiers, variants and customer matching are reviewed together. Guest purchases and existing profiles need explicit checks so a purchase event is useful alongside the correct customer and product context.
We review initial synchronization and existing scripts before turning on another source of events. Subscriber settings are checked independently of customer import, and historical orders are kept distinct from new activity when evaluating flow behavior.
Share the website, installed extension version and the Klaviyo account. We confirm compatibility, account permissions and any hosting restrictions that could prevent the connection working.
Provide your checkout opt-in wording, current lists and consent setup. Importing a customer profile does not by itself establish permission to send marketing, and email and SMS settings need separate treatment.
Campaign writing, sending and revenue targets are outside a connection-only scope. Existing live flows must be reviewed before synchronization changes so imported activity does not trigger unintended messages.
List active plugins, tracking scripts and Klaviyo integrations. Compare a representative WooCommerce order and profile with their Klaviyo counterparts.
Apply the agreed connection settings, then test supported shopping activity, an opted-in customer and a customer without marketing permission. Compare identifiers and event values.
Check synchronization status, missing records and duplicate events. Document the tested event inventory, limits, consent settings and the owner responsible for ongoing checks.