The full setup path from workspace to first attributed number, with honest timing for when data shows up.
nod. attributes revenue to the channels that actually drove it, by combining a first-party pixel, your Shopify orders, and your ad platforms. Setup has a few required stages and a couple of optional ones. This page is the map — each stage links to a deep-dive article with the exact steps.
When you create a workspace, nod. provisions your pixel — a public id in the form px_... that identifies your workspace to the tracking script. Creating a pixel is admin-only and idempotent: if one already exists, nod. returns the same id rather than minting a new one, so the snippet you paste never has to change later.
On Shopify the pixel is an app embed: install nod. from the App Store, then switch nod. pixel on in your theme editor — no code, and nothing left behind if you uninstall. On other storefronts or funnels it's a single script tag in your site template's <head> or your tag manager's custom-HTML head slot. Once it's live it tracks pageviews automatically, including SPA navigation, and never breaks your page even if something goes wrong.
Full steps: Install the nod. pixel on Shopify and, for anything that isn't Shopify, Install the pixel on other storefronts and funnels. For how the script behaves once it's running, see How the nod. pixel works.
Connecting Shopify lets nod. read your orders and turn them into conversions. Install nod. from the Shopify App Store — that is the only path, and it needs no store domain, token or custom app. nod. then registers the order webhooks, backfills up to a year of past orders so the dashboard isn't blank, and captures your store's timezone so daily totals line up with your Shopify admin.
Full steps: Connect your Shopify store.
Connect Meta and Google Ads so nod. can read spend, and Klaviyo for email/SMS campaign performance — all of it joins against the revenue your pixel and Shopify orders produced. Each connector is admin-only to connect or disconnect. GA4, TikTok, and ChatGPT Ads are also available if you use them, but Meta, Google, and Klaviyo are the core three for most stores. ChatGPT Ads connects by pasting an Advertiser API key, and reports spend, impressions, and clicks only — OpenAI exposes no conversion or revenue metrics, so revenue for that channel comes from your pixel and Shopify orders the same way it does for any untracked platform.
Full steps: Connect Meta Ads, Connect Google Ads and GA4, Connect Klaviyo.
This is the step that actually makes attribution work. nod. reads nod_source on your ad URLs to name the channel explicitly, plus an ad-level join key (nod_adid) and nod_adset / nod_campaign to group it, wherever the platform supports click-time macros. Each platform has its own parameter string and its own field to paste it into (Meta's goes in the ad's URL parameters field, not the destination URL — Meta strips query strings appended there directly). Skipping this step is the single most common reason attribution looks thin.
Full steps: Add nod. URL parameters to your ads.
If you sell on Shopify, nod. can forward consented Purchase events to Meta through the Conversions API. This improves Meta's delivery, optimization and platform reporting. It does not power nod. attribution, which already uses the nod. Pixel and Shopify orders. Pick a dataset, then use the master switch to pause or resume forwarding. Unknown or denied consent always skips the send; there is no consent-bypass toggle.
Full steps: Set up the Meta server-side send-back (CAPI). If you also run your own Meta pixel, read Avoid double counting with your own Meta pixel too.
By default the pixel loads from a shared nod. domain. Pointing a subdomain you own, such as px.yourshop.com, at nod. keeps delivery on your brand domain and can avoid simple third-party hostname blocklists. It does not bypass consent or every blocker. This is optional and can be set up after the required pixel and URL-tagging steps work.
Full steps: Serve the pixel from your own domain (first-party).
Shopify orders show up fast: the order webhook triggers an attribution derive as soon as it arrives. Everything else — pixel-only purchases, leads, and any re-derivation triggered by new data — runs on a cron that ticks every 30 minutes, so allow up to half an hour for those numbers to appear. There's no real-time derive from pixel pageviews alone, and ad-platform performance (Meta, Google Ads, ChatGPT Ads) is synced on its own cycle rather than live: a connected account is polled every 15 minutes, and an account with nothing new backs off to as far apart as four hours.
Once your ad platforms are connected, come back and confirm step 5 is actually done: an unconfigured URL-parameter step is the most common reason a freshly connected account still shows revenue as unattributed.