Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

CRM Sync gap fill: Shopify / Google → Xano

CRM Sync captures consent at the edge, before any tag loads, and writes it to a ledger in Xano, the system of record. Shopify and Google each hold part of the picture; neither holds all of it, and ECC holds none. For each consent gap:

GapShopifyGoogleCRM SyncXano
Consent per purpose (analytics, ads, sale / share, email, SMS)emailMarketingConsent and smsMarketingConsent on the customer (per channel); Customer Privacy API analytics / marketing / preferences / sale_of_data (per visitor).Consent Mode v2: analytics_storage, ad_storage, ad_user_data, ad_personalization.The banner writes one ledger row per purpose, never one combined flag.purpose
granted
Who decided, how and with which bannermarketingOptInLevel (single / confirmed opt-in); consentCollectedFrom on SMS consent.The Consent Mode update that was sent, as evidence.Every row carries source, banner_version, actor and a hash of the raw signal.source
banner_version
actor
evidence_sha256
An exact, comparable timeconsentUpdatedAt (ISO 8601, UTC).-recorded_at in UTC at the edge, plus seq.recorded_at
seq
Where consent was given, and under which regimeCustomer Privacy API region for the visitor.Consent Mode defaults set per region.Region from the edge request and the Sec-GPC header, resolved to a regime before the banner shows.region
regime
gpc
Consent before there is a customerCustomer Privacy API consent for an anonymous visitor.Consent Mode state per browser.visitor_id on every row; an identity link to the Shopify customer and KUNNR on first order or sign-in.subject_type
visitor_id
identity_link
Consent for one-time customersThe customer created or matched from the checkout email.-Subject keyed by email hash and Shopify customer ID; never by a one-time KUNNR.email_sha256
shopify_customer_id
Consent for B2B contact personsB2B company contacts are customers in their own right.-subject_type contact, with the company as context.subject_type
contact_id
A withdrawal that sticksCustomer marketing-consent update webhooks.A Consent Mode update to denied on the page.Appends a row, then publishes the withdrawal event; nothing overwrites a row.idempotency_key
recorded_at
seq
Data subject requests: access, deletion, opt-out of salecustomers/data_request, customers/redact and shop/redact webhooks; dataSaleOptOut on the customer.Remove the person from Customer Match lists.Fans the request out (Shopify, Google, ECC, Xano) and collects a receipt from each.dsr_request
dsr_receipt
Age or minor status--An age gate where required; unknown stays unknown.minor
Retention per purpose--Sets expires_at from the regime’s rule when it writes the row.expires_at
Permission to use a person for ads and audiencesmarketing and sale_of_data from the Customer Privacy API.Customer Match uploads carry consent (adUserData, adPersonalization: GRANTED / DENIED) per person.Exports only subjects whose newest ad_user_data and ad_personalization rows are granted; Merchant Center products carry no personal data.entitlement

Append-only: rows are added, never updated. The newest row per subject and purpose (by recorded_at, then seq) is the current decision.

FieldTypeNote
idintRow ID.
idempotency_keytext, uniqueOne per decision; a replay writes nothing.
subject_typeenum customer / visitor / contact
visitor_idtextSet before there is a customer.
kunnrtextKNA1-KUNNR when known; never a one-time account.
shopify_customer_idtextgid://shopify/Customer/…
email_sha256textNormalised e-mail, hashed: a key, not contact data.
contact_idtextB2B contact person.
purposeenum analytics / ads / ad_user_data / ad_personalization / sale_share / email / sms
grantedbool
sourceenum banner / shopify / dsr / gpc / importimport rows never grant ads purposes.
banner_versiontext
actortextWho or what wrote it: shopper, agent, support user, job.
regiontextISO 3166-2 at decision time.
regimeenum us_optout / eu_optin / kr_pipa / …
gpcboolSec-GPC seen.
minorbool, nullable
recorded_attimestamp (UTC)
seqintOrders events in the same second.
expires_attimestamp, nullable
evidence_sha256textHash of the raw signal (banner payload, webhook body).

Alongside it: identity_link (visitor → Shopify customer → KUNNR), dsr_request and dsr_receipt (one receipt per system a request fans out to), and an entitlement view computed from the newest rows: what a person may be sent, shown or exported to. Entitlements are derived, never uploaded or edited by hand.

Who writes what

WriterMay writeMay not
CRM Sync banner (edge)Ledger rows (source banner, gpc)Anything in ECC
Shopify webhooksLedger rows (source shopify), DSR requestsAds purposes from an e-mail opt-in
DSR handlerLedger rows (source dsr), DSR receiptsDelete ledger rows (they are the proof)
One-time import (CSV)Ledger rows (source import)Ads purposes, or anything newer than an existing row
ECC / middleware batchNothing: reads the entitlement viewConsent fields, in ECC or Xano
Merchant / Google exportNothing: reads entitlements and productsPersonal data into Merchant Center