How can we help?

Start here: setting up nod. step by step

The full setup path from workspace to first attributed number, with honest timing for when data shows up.

Install the nod. pixel on Shopify

Switch on the nod. pixel app embed and verify events arrive.

Install the pixel on other storefronts and funnels

Add the nod. snippet to any non-Shopify site and send purchase and lead events manually.

Connect your Shopify store

Install nod. from the Shopify App Store so your orders become attributed revenue.

Connect Meta Ads

Link your Meta ad account so nod. can read campaign performance and attribute revenue back to it.

Connect Google Ads and GA4

Connect Google Ads for spend and campaign data, and GA4 as a read-only analytics mirror.

Connect Google Search Console

Connect a verified property and read aggregate organic search demand without turning Search Console data into conversion credit.

Connect Klaviyo

Add your Klaviyo API key so nod. can read your email and SMS performance.

Add nod. URL parameters to your ads

Append nod_source and the nod_* join parameters to your ad platforms so nod. can match orders back to the exact ad and channel that drove them.

How the nod. pixel works

What the pixel fires, what it stores, and what it never collects.

Consent and cookie banners (CMPs)

Wire your cookie banner to the nod. pixel so it respects your visitors' consent choices.

Serve the pixel from your own domain (first-party)

Point a subdomain at nod., understand who configures what, and know the limits.

The domain allowlist

Control which sites can send events to your pixel, and avoid the silent event drop that comes from a too-narrow list.

Track conversions and intent milestones with the pixel API

Send purchases, leads, and explicit Journey milestones without turning generic form activity into attribution evidence.

How nod. attribution works

The full path from pixel event to a credited dollar in your dashboard.

Attribution models and when to use which

What each model does, and how nod. Mix V3 separates Created, Intent Captured and Final Closed.

Why your numbers differ from Meta, Shopify, and GA4

What nod. counts, excludes, and measures differently from your other reports, and which number to trust.

Coverage: how much of your revenue is attributable

What the coverage numbers mean, what lowers them, and what you can do to raise them.

Reading the attribution dashboard

What each surface shows, how drilling and the model switcher work, and the conventions behind the numbers.

Set up the Meta server-side send-back (CAPI)

Connect a dataset, understand the consent gate, and verify Purchases in Meta's Test Events tab.

Avoid double counting with your own Meta pixel

Stop Meta from counting one order as two purchases when you run your own browser pixel alongside nod.'s server-side send-back.

CAPI delivery, health, and retries

What happens when a send to Meta fails, how retries and backoff work, and how to read the health badge.

The pixel shows no events

Work through the checklist, most likely cause first, to find why events aren't arriving.

Shopify webhook health: states and fixes

What ok, partial, failed, and hmac_failed mean, where to see them, and how to fix each one.

My numbers look wrong: a checklist

Work through six checks, most likely cause first, before assuming nod. is broken.

Frequently asked questions

Straight answers on pixel performance, privacy, Safari, data retention, test orders, and consent banners.