Shared ecommerce schema
Define purchase, refund, checkout, and product events once, then keep the same field names across storefronts.
Standardize first-party events across storefronts, preserve brand context, and route each approved signal to the right analytics and advertising accounts.
Storefront and backend events
Collect the same purchase contract across each brand and market.
Brand, market, and consent rules
Preserve ownership and apply the policy attached to each event.
Brand-specific accounts
Route eligible events to the configured analytics, ad, and warehouse targets.
Collection, policy, and delivery rules sit in one event path, so multi-brand ecommerce teams can see what happens before data leaves.
Define purchase, refund, checkout, and product events once, then keep the same field names across storefronts.
Keep brand, storefront, market, currency, and source fields attached through collection and delivery.
Send approved events to the analytics and advertising accounts configured for that brand or market.
Apply consent, PII, transformation, and naming rules before data reaches downstream tools.
Compare brands on a stable event contract while retaining their original currencies and operating context.
Match browser journeys with confirmed orders, refunds, and other source-of-truth events from commerce systems.
Add a storefront without inventing another tracking schema.
Keep each brand's destinations and permissions explicit.
Reconcile marketing events with confirmed commerce records.
Hardal uses encrypted transport and managed access controls. Its security programme includes ISO 27001, ISO 27701, and ISO 9001:2015 certifications. Check the Trust Center for scope and certificate details.
Bring one event schema, one destination map, and one confirmed order flow. We will show where the shared layer starts.