Segment / RudderStack — track merch events alongside product events
PO created, shipped, delivered events stream to your CDP — attribute swag spend by campaign and segment in Italy.
Event schema — server-side track()
Standard events: po.created, po.approved, po.shipped, po.delivered, recipient.received. Each event carries PO ID, value, currency, recipient (anonymised ID), department, campaign, country.
Identity stitching
Recipients are identified by email hash + campaign — joins with your existing user identity. For B2B, account-level identification via domain.
Destinations — anywhere Segment goes
Once in Segment/RudderStack, route to your warehouse (Snowflake, BigQuery, Redshift), product analytics (Amplitude, Mixpanel, Heap), CRM (HubSpot, Salesforce), ad platforms.
Italy — local privacy and SdI (Sistema di Interscambio)
GDPR consent handled per recipient. Where consent absent, only aggregated/anonymised events flow. IVA 22% cost data is added server-side, never PII. SdI (Sistema di Interscambio) invoice IDs cross-reference for finance reconciliation from Milano.
FAQ
RudderStack open-source?
Yes — works with both managed and self-hosted RudderStack. Mtu-friendly.
PII in events?
Hashed only — never raw email/phone. Full PII flows only with consent and via secure channel separate from events.
Customer.io / Klaviyo support?
Yes — through Segment destinations or directly via webhook.
Replay events?
Yes — last 30 days available on request, useful for re-attribution.
Cost?
Events count against your Segment MTU. We minimize event volume — one per state transition, not per heartbeat.