Name: Klaviyo Reshape — flat feed to Google Merchant, products that match
Brand: CRM Sync
SKU: klaviyo-merchant-reshape
Price: 49.00 USD
Availability: InStock

Klaviyo Reshape for Nested GraphQL Data Layer Feed for Google Merchant API

The mirror is free and read-only: every Klaviyo list and segment you have, and the key each one becomes — produced before you change anything.

What you get

✓Your mirror first — one read-only call, four counts, and two deliberate zeroes: no members read, no permissions read.
✓The catalog reshaped — rebuilt in the shape Google Merchant reads: every variant tied to the product it belongs to, identifiers as a list, price as an amount and a currency, shipping per country.
✓Two tables in your own Xano — lists and segments kept apart, because a subscription and a live query are not the same object and must not share a status column.
✓Per-channel permission with a record behind it — which basis, which version, granted when, under what wording. The thing an agent needs before it can act for a customer.

Klaviyo keeps products flat, and its own documentation says so: there is currently no way to set up related or variant items in Klaviyo in a traditional parent-child model. Every size and colour arrives as its own row, and the product they belong to survives only as text someone typed into an ID — nothing checks it, so when it is wrong the rows attach to the wrong product and nothing tells you.

Permission flattens the same way. Klaviyo records channel subscription — email and SMS opt-in, with a timestamp. What it does not record is purpose-scoped advertising consent: ad_user_data and ad_personalization, with the jurisdiction that decided. “You may email me” is not “you may share my identifiers with Google for ad personalisation” — different purposes, different fields, and the second cannot be inferred from the first.

So the identifier stays trapped in the email channel. It never becomes addressable to Google, because the consent that would admit it was never collected and cannot be back-derived from a newsletter opt-in.

Access you have and access you do not look identical from the outside — so the honest way to show it is to let the server verify it in front of you. Open the panel, press the button, and read what it actually says. What happens depends on who you are, and the panel tells you which before you press rather than promising an outcome it cannot know.

Nothing here is asserted at you: the record is served live, its hash chain is verified on read, and the row you just created appears in it. Accounts are redacted in this public view. An anonymous press writes nothing — a ledger a stranger can append to from a public page would prove nothing.