Custom Ecommerce Integration
T-Shirt Printing Business
Systems Involved
Deco Network
E-commerce platform
Purpose-built for decorated apparel and promotional products. It handles product configuration, artwork, and order management for a t-shirt printing business, but it sits outside the mainstream e-commerce ecosystem, so it ships with no native connectors to marketing platforms.
Klaviyo
Email & SMS marketing
Klaviyo's value depends entirely on the behavioral data flowing into it: profiles, purchase history, and on-site events are what trigger automated flows. Without that data it's just a list-blasting tool.
The gap
No supported integration path existed in either direction. Klaviyo had no record of who was browsing, what was left in carts, or what had actually been purchased, which meant no abandoned-cart, browse-abandonment, or post-purchase automation.
Technical Stack & Tools
- Client-side event tracking
- Custom JavaScript deployed into the Deco Network storefront templates, firing on product-view and add-to-cart events. Each event pushes the product identifier, name, price, and image to Klaviyo along with the visitor's identity so the event lands on the right profile.
- Server-side order & customer sync
- A scheduled Make.com scenario running hourly. It authenticates against the Deco Network API, pulls orders created or updated since the last run, transforms the payload into Klaviyo's expected shape, and writes both profile records and purchase events. Make.com was chosen over a hosted script for maintainability: the client can see the run history, inspect failures, and adjust the schedule without a developer.
Protocols & Specs
- Transport
- HTTPS REST with JSON payloads in both directions.
- Deco Network API
- REST/JSON, HTTP Basic authentication with credentials stored in Make.com's encrypted connection store rather than inline in the scenario. The orders endpoint is paginated, so retrieval runs as an iterator in Make.com that requests successive pages until the response returns an empty or short page, then passes the accumulated orders downstream for transformation.
- Klaviyo API
- JSON:API-formatted request bodies with a dated revision header for version pinning. Client-side events authenticate with the public site key; server-side profile and event writes use a private API key held in Make.com's credential store, never exposed to the browser.
- Identity resolution
- Email address as the primary key joining anonymous on-site behavior to known customer records, so client-side events and server-side order data land on the same Klaviyo profile.
- Sync model
- Incremental hourly pull rather than webhook push, since Deco Network exposes no outbound webhooks.