Connect Meta Ads

Connecting Meta Ads lets nod. read your campaign, ad set, and ad performance and match it against pixel-based attribution. This is a read connection — it does not change anything in your Meta account and it is separate from the optional server-side send-back described in Set up the Meta server-side send-back (CAPI).

tl;dr

• Connect from Settings → Data sources (the card reads "Meta · Facebook & Instagram").
• Connecting requires the Admin role. Members can see the status but not connect or disconnect.
• After OAuth, pick the Meta ad account nod. should read.
• Campaign data refreshes once a day, not in real time.
• nod. only reads ad performance here. Sending conversions back to Meta is a separate, optional setup (CAPI).

1. Open the integrations page

Go to Settings → Data sources. Meta is the first card in the grid. Each card shows one of five states: Connected, Needs setup, Reconnect, Not connected, or Soon.

If you're not a workspace admin, you'll see the current state but no Connect action — only admins can connect or disconnect data sources.

2. Start the OAuth flow

Click Connect on the Meta card. You're sent through Meta's OAuth login, the same authorization nod.'s Approval app uses. Authorize access and you're returned to nod.

3. Pick the ad account

Once authorized, choose the Meta ad account nod. should read. If your business has more than one ad account, you can change the selected account later from the same card — this is also the account the Meta pixel/dataset picker in CAPI setup reads from by default.

What nod. reads

Once connected, two daily jobs keep Meta data current:

• Campaign, ad set, and ad performance (spend, impressions, clicks, and related metrics) syncs once a day, along with lifetime insights on published ads.
• The full account hierarchy — campaigns down to ads — syncs once a day with trailing 30-day performance.

This is a snapshot, not a live feed: there is no real-time sync for Meta ad performance. Expect the numbers on your dashboard to reflect the most recent daily sync, not the current minute.

What nod. does not do here

This connection is read-only. nod. does not create, edit, pause, or publish anything in your Meta account through it.

Sending consented Shopify Purchases back to Meta through the Conversions API is a separate, optional feature configured on the Tracking page. It improves Meta delivery, optimization and platform reporting; nod. attribution works without it. It uses the Meta ad account and pixel/dataset you select there, not this connection's ad-account choice by itself. See Set up the Meta server-side send-back (CAPI) to turn it on.

Reconnecting

Meta access tokens can expire. When that happens, the card's status changes to Reconnect, and any dependent feature (like CAPI) will flag it too — for example, the CAPI status line shows "Meta token expired — reconnect." Click Reconnect on the Meta card and repeat the OAuth flow; nod. resumes reading from where it left off.

What happens next

After you connect and pick an account, existing performance data isn't backfilled instantly through this flow — the daily sync jobs pick it up on their next run. Give it until the next day's sync (or check back after 24 hours) before assuming something is missing.

Common pitfalls

• Only admins can connect or disconnect. If the Connect button is missing, you're signed in as a member, not an admin.
• A stale connection shows as Reconnect, not Not connected. If Meta was working before and suddenly numbers stop updating, check for a Reconnect pill before assuming a tracking problem.
• Ad-account performance and CAPI dataset are different choices. Selecting an ad account here does not automatically configure CAPI's Purchase send-back — that's a separate setup on the Tracking page.