Today the options are workarounds
- Theme code pushes metafields only when a customer logs in. Guests, imports, and lapsed customers never sync.
- Shopify Flow + HTTP works until it quietly stops. Nothing tells you.
- Klaviyo Custom Actions need a 400k-profile account.
- Zapier / Make bills per task and adds one more credential to babysit.
If you have more than a couple of custom customer metafields, this is for you. Whatever wrote the metafield (loyalty apps, quizzes, Flow, Matrixify, B2B, custom apps), it can land in Klaviyo.
Map any customer metafield
Point each field at a Klaviyo custom property. Types carry over: dates stay dates, lists stay lists.
Backfill, then stay in sync
Existing customers sync on first connect. Ongoing changes keep profiles current.
Dry run first
See exactly what will change before anything writes to Klaviyo.
Failures are visible
Retries, a failed-sync inbox with the reason, and an email when something breaks.
Safe by default
Never overwrites a filled property or deletes anything unless you say so.
Reusable mappings
Save a mapping once, reuse it on the next store. Built for the person who clicks Install.
How it works
MetaBridge reads your customer metafield definitions.
Name the Klaviyo custom property for each metafield you map.
Backfill existing customers, then stay in sync on every change.
Early access pricing
Founding stores keep this price as long as they stay installed. 14-day free trial at App Store launch.
Shopify customer metafields → Klaviyo custom properties. Mapping + sync health included.
Get early access
Tell us which metafields you need and how you sync them today. That helps us prioritize the right pilots.
I reply personally within two business days. MetaBridge reads only the metafields you map, uses email only to match Klaviyo profiles, and never sells data. Your Klaviyo private API key stays under your control for the sync you authorize; we do not sell data or run ads. Privacy policy.
Prefer email? Write hello@getmetabridge.com with the same details.
FAQ
Do you support HubSpot?
Klaviyo is first. HubSpot contact/company properties are planned for Phase 2.
How do you handle credentials?
Your Klaviyo private API key is used only to write the properties you map. It is not sold, not used for ads, and stays scoped to the sync you authorize. Shopify tokens follow the same rule.
Is this only for agencies?
No. Pricing and install flow are built for a single merchant. Agencies can reuse mappings across stores when that helps.