Connecting Squarespace Commerce to Roku Ads

Architecture

How Squarespace and Roku actually connect

Two systems that know nothing about each other. Everything below exists to give them one shared reference.

1. Step 1

   Squarespace Commerce holds the truth

   Squarespace holds the order cleanly. The constraint is access — code injection is limited and checkout customisation more so, which caps what a browser-side approach can achieve.

2. Step 2

   Roku Ads needs a click to match

   A pixel or server event on your side that Roku can match against, plus the hashed customer information the match depends on. Without that, the channel is measurable only by holdout.

3. Step 3

   The identifier is the bridge

   Household-level identity, not a click, captured at the visit and carried into the Squarespace order. Without it there is nothing to join on and no tool fixes that.

4. Step 4

   The event source decides reliability

   Send from the webhook rather than the confirmation page, which has restricted script access and may not run what you expect.

5. Step 5

   Deduplication at the destination

   The deduplication problem is across platforms, not within this one. A household exposed to a TV ad and later reached by search and social produces a conversion all three will claim.

Diagnose it honestly

Working vs. broken, side by side

Both states look identical from the Roku dashboard, which is why this runs for months before anyone notices.

Diagnostic sequence

Diagnostic order

Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.

1. 1

   Count orders carrying household-level identity, not a click

   The ceiling on everything else. Do this before debugging anything downstream.

2. 2

   Follow one real conversion end to end

   From the ad click through Squarespace and into Roku.

3. 3

   Test what actually reaches the order record

   One real purchase tells you more than the documentation about what this platform preserves.

4. 4

   Ask whether a geo or audience holdout exists

   If it does not, the reported figure is exposure correlated with purchase, which is not the same as a campaign that caused one.

5. 5

   Read the match rate, not the success message

   Roku reports matched conversions and match rates. The match rate tells you how much of your audience it could resolve at all — and a geo holdout tells you whether the campaign moved anything.

Source-of-truth validation

How it gets proven

Against Squarespace Commerce's own records, not against either platform's dashboard.

• Household-level identity, not a click confirmed present on a live order.
• A real conversion followed from click through Squarespace to Roku.
• Incremental lift measured against a holdout, with platform-reported conversions shown alongside rather than instead.
• A test purchase with the identifier confirmed retrievable from the Squarespace order.
• Reconciled over a fully closed window, matched per record rather than on totals.
• Re-checked 30 days later.

Straight talk

When you don't need this

Worth reading before paying anyone, including us.

• If Roku already reports conversions that reconcile against Squarespace Commerce's records within a few percent, this join is working and there is nothing to buy.
• Measure identifier coverage yourself first — pull your last hundred orders and count how many carry household-level identity, not a click. Ten minutes, free, and it tells you whether any of this is worth doing.
• For a small Squarespace store, the native integrations plus honest reporting may be the right answer — the platform's ceiling is real.
• If you cannot run a holdout, keep CTV budget small and report it as unproven. That is a more useful position than a matched number nobody can check.