Integration · Shopify
Integrate Shopify with Slugy: track revenue, not just clicks
The best URL shortener for tracking revenue on Shopify — tie every order back to the short link, influencer, or QR code that drove it.
How it works
Traditional click tracking tells you a link got 1,000 clicks. Slugy tells you those clicks turned into 42 orders worth $2,180 — broken down by link, campaign, and channel. The bridge is a click id (slugy_click_id) captured at landing and replayed at checkout. For the API background, read how to track link conversions.
- 1
Tag outbound links with UTMs and short links
Create a branded short link in Slugy for every campaign — product launches, influencer codes, email drops, QR on packaging. Append UTM source/medium/campaign (use the free UTM builder) so GA4 and Slugy agree on attribution. Share the short link everywhere instead of the raw myshopify URL.
- 2
Capture slugy_click_id on your storefront
When a visitor lands via a Slugy link, Slugy sets a first-party slugy_click_id in the URL and cookie. Add a Shopify web pixel (Settings → Customer events → Add custom pixel) that reads the id from the URL or cookie and persists it through to checkout — localStorage or a checkout attribute both work. Without this id, orders cannot be attributed.
- 3
Post the order to Slugy at checkout
On order creation, POST to /api/integrations/shopify/order with a Leads-write API key (Settings → API Keys) or your shared HMAC secret. Include clickId, orderId, customerEmail, saleAmount and saleCurrency. Growth workspaces record a sale event against the original link; Pro/Free get a 403 for revenue fields and a 404 for unknown clicks.
- 4
Analyze revenue per link
Open the analytics dashboard: clicks, leads, conversion rate, and revenue per slug. Compare influencer A vs influencer B on actual dollars, not clicks. Route sale.created to Slack for instant sale alerts or to Zapier to update your CRM, Sheets, or email flows.
Example order payload
POST /api/integrations/shopify/order
Authorization: Bearer <leads-write API key>
Content-Type: application/json
{
"clickId": "clk_abc123",
"orderId": "gid://shopify/Order/123",
"customerEmail": "buyer@example.com",
"saleAmount": 49,
"saleCurrency": "USD"
}- Authentication: shared HMAC secret or a workspace API key with leads-write scope (binds the sale to that workspace).
- Unknown click ids return 404 — log and continue; the order still exists in Shopify.
- Non-Growth workspaces get 403 for revenue fields — upgrade to Growth to unlock sales analytics.
FAQ
Do I need a Shopify app install?
No. Slugy uses a lightweight web pixel plus a server-side order POST — no app review, no theme edits. Paste the pixel once, then forward orders with an API key.
Which plan do I need for revenue tracking?
Lead events (lead.created) need Pro. Revenue events (sale.created with saleAmount/saleCurrency) need Growth. Click analytics work on every plan including free.
What if a buyer comes back later without the link?
Persist the click id in a first-party cookie or localStorage with a 30–90 day TTL, then attach it at checkout. Last-click attribution wins, matching how most e-commerce teams report influencer and ad spend.
Does this work with Shopify Flow?
Yes. Trigger a Flow workflow on order creation, read the stored click id, and POST it to Slugy. The same payload shape works from pixels, Flow, or your own server.
Bottom line: one web pixel plus one order POST turns every Shopify checkout into revenue attributed to the short link behind it.