Connect Northbeam to Rig

    Bring Northbeam's spend, revenue and attribution into your warehouse, including both its blended view and the platform-reported numbers. Once they sit beside your raw platform spend and your actual orders, you can interrogate the attribution rather than take it on trust.

    Requirements
    Access to Settings → API keys in Northbeam
    Time required
    5 mins

    Create an API key

    1. Log into Northbeam.
    2. Go to Settings, the gear icon at the bottom left, then API keys.
    3. Click Create new API key.
    4. Copy both the API key and the Client ID.

    Connect it in Rig

    1. In Rig, open Connections and go to Sources & actions.
    2. Search for Northbeam and open the card.
    3. API key: paste the key you generated.
    4. Client ID: paste the Client ID shown next to it.
    5. Click Test, then Sync.

    What Rig pulls in

    • Spend and revenue by channel, with ROAS derived from them
    • Channel performance across your paid mix
    • Customer journeys, the touchpoint paths that lead to a conversion
    • Both blended and platform-reported metrics, kept separately rather than reconciled into one number

    Reading attribution correctly

    Rig keeps Northbeam's blended attribution and the platform-reported numbers side by side, deliberately. They will not agree, and collapsing them into a single figure is how double-counted revenue gets into a board deck.

    • Do not sum platform-reported revenue across channels. Each platform claims credit for conversions the others also claim, so the total will exceed your actual revenue. That divergence is the thing worth measuring: which channels are most over-credited relative to Northbeam's view.
    • Recent days are provisional. Conversions attribute after the click and platforms restate spend, so the last few days of any attribution dataset move after the fact. Treat yesterday's ROAS as an early read rather than a number to act on.

    Troubleshooting

    • Authentication fails: the Client ID is missing or belongs to a different key. Both values come from the same Create new API key action, so a key from one generation paired with a Client ID from another will not authenticate.
    • Numbers disagree with the Northbeam dashboard: check which attribution basis the dashboard view is set to before treating it as a sync problem. Rig holds several, and comparing a blended figure against a platform-reported one will always show a gap.
    • Recent days keep changing between syncs: expected. Late-attributing conversions and restated platform spend both land after the day closes.

    Was this guide helpful?