> ## Documentation Index
> Fetch the complete documentation index at: https://docs.northbeam.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tatari Setup

> Set up Tatari user tracking and AWS data sharing so Northbeam can attribute your Tatari TV orders.

When you're done, Northbeam shows your Tatari clicks, matchbacks, and attributed orders under the **Clicks & Matchbacks** attribution model.

<Info>
  **Before you start**, make sure you have:

  * A login to your [Tatari Dashboard](https://www.tatari.tv/) with access to **Account Settings → Integrations**
  * **Shopify stores:** permission to install apps from the Shopify App Store
  * **Custom platforms:** access to your site's `<head>` code and the token Tatari gives you
  * Access to [Connections](https://dashboard.northbeam.io/settings/connections) in Northbeam
</Info>

<span id="important-notice" style={{ display: "block", scrollMarginTop: "7rem" }} />

<Note>
  This integration supports only **Streaming** inventory by default. **Linear** inventory isn't turned on automatically. If you need Linear, [contact Northbeam Support](https://www.northbeam.io/submit-a-support-ticket) to turn it on for your account.
</Note>

<span id="setup-steps" style={{ display: "block", scrollMarginTop: "7rem" }} />

<CardGroup cols={4}>
  <Card title="1. Set up user tracking" icon="user-check" href="#set-up-user-tracking-in-tatari">
    Add Tatari's tracking to your site.
  </Card>

  <Card title="2. Connect the account" icon="plug" href="#connect-your-tatari-account">
    Turn on AWS Data Sharing and enter your Tatari ID.
  </Card>

  <Card title="3. Add AWS credentials" icon="key" href="#add-the-aws-credentials-in-tatari">
    After 24 hours, paste Northbeam's AWS credentials into Tatari.
  </Card>

  <Card title="4. Confirm tracking" icon="circle-check" href="#confirm-tracking">
    Check that Tatari data is arriving.
  </Card>
</CardGroup>

<Steps titleSize="h2">
  <Step title="Set up user tracking in Tatari">
    <span id="step-1-enable-user-tracking" style={{ display: "block", scrollMarginTop: "7rem" }} />

    Northbeam needs Tatari user tracking to attribute Tatari-driven orders correctly. The setup depends on your store platform. For more detail, see Tatari's [User Tracking Guide](https://drive.google.com/file/d/1U-ETZyVeEMclKiCY63falhOSN4EtbIAq/view?usp=sharing).

    <span id="-for-shopify" style={{ display: "block", scrollMarginTop: "7rem" }} />

    **Shopify**

    1. Open the [Tatari Tag Manager](https://apps.shopify.com/tatari-tv) app on the Shopify App Store.
    2. Click **Add app** and follow the prompts.

    Once it's installed, the app manages the pixels that track funnel events from your TV campaigns.

    <span id="-for-non-shopify-custom-platform" style={{ display: "block", scrollMarginTop: "7rem" }} />

    **Non-Shopify (custom platform)**

    1. Add this script to your site's `<head>`. Replace `YOUR_TOKEN` (in two places) with the token Tatari gives you.
    2. When a user logs in, call `tatari.identify({user_id})`, replacing `{user_id}` with your internal user ID.

    ```html theme={null}
     <script>
         !function(){try{!function(t,i){if(!i.version){window.tatari=i,i
         .init=function(t,n){var e=function(t,n){i[n]=function(){t.push([
         n].concat(Array.prototype.slice.call(arguments,0)))}};"track
         pageview identify".split(" ")
         .forEach(function(t){e(i,t)}),i._i=t,i.config=n,i.pageview()}
         ,i.version="1.2.1"; var
         n=t.createElement("script");n.type="text/javascript",n.async=!0
         ,n.src="https://d2hrivdxn8ekm8.cloudfront.net/tag-manager/YOUR_TOKEN-latest.js";var e=t.getElementsByTagName("script")[0];e.parentNode.insertBefore(n,e)}}(document,window.tatari||[])}catch(t){console.log(t)}}();
         tatari.init('YOUR_TOKEN');
     </script>
    ```

    <Warning>
      **Use the same customer IDs in Tatari and Northbeam.** The user IDs you send to `tatari.identify` must match the customer IDs on your Northbeam orders. Custom setups vary, so check that yours lines up with Northbeam's requirements.

      Need help with user tracking? Contact your Tatari representative. Northbeam can't help with this part.
    </Warning>

    **If you skip this step:** Northbeam can't accurately attribute Tatari-driven orders. If customer IDs don't match, you may see clicks and matchbacks but no revenue or transactions.
  </Step>

  <Step title="Connect your Tatari account">
    <span id="step-2-enable-aws-data-sharing" style={{ display: "block", scrollMarginTop: "7rem" }} />

    AWS Data Sharing lets Northbeam access your Tatari-attributed order data.

    1. Log in to your [Tatari Dashboard](https://www.tatari.tv/).
    2. Go to **Account Settings → Integrations** and make sure **AWS Data Sharing** is turned on.

    <span id="step-2-share-your-tatari-id-with-northbeam" style={{ display: "block", scrollMarginTop: "7rem" }} />

    <span id="step-3-insert-tatari-id-and-source-of-truth" style={{ display: "block", scrollMarginTop: "7rem" }} />

    Next, give Northbeam your Tatari ID and pick your source of truth so the two stay in sync:

    1. Find your **Tatari ID** in your Tatari account URL.
    2. In Northbeam, open [Connections](https://dashboard.northbeam.io/settings/connections) and find **Tatari**.
    3. Enter your **Tatari ID**, select your **Orders Source of Truth**, and click **Connect**.

    Northbeam then creates the AWS credentials you'll use in the next step.

    **If you skip this step:** Northbeam can't access your Tatari-attributed order data.
  </Step>

  <Step title="Add the AWS credentials in Tatari">
    <span id="step-4-allow-24-hours-for-the-tatari-connection-to-process" style={{ display: "block", scrollMarginTop: "7rem" }} />

    **Wait 24 hours first.** After you enter your Tatari ID and source of truth, allow up to 24 hours for the connection to finish processing.

    <Warning>
      If you add the AWS credentials too early, Tatari shows **"API Error 400: Invalid ARNs"**. That's expected. Wait until the 24 hours are up and try again.
    </Warning>

    <Frame caption="The error you'll see if you add credentials too early">
      <img src="https://mintcdn.com/northbeam/EpMPeQ8Ec2Yrg9EI/images/readme/46aed383-image_117.png?fit=max&auto=format&n=EpMPeQ8Ec2Yrg9EI&q=85&s=a25aa3db465f7e596eb09c33fd675dbe" alt="Tatari error message reading API Error 400: Invalid ARNs" style={{ maxWidth: "560px", maxHeight: "440px", width: "auto", height: "auto", margin: "0 auto" }} width="2952" height="586" data-path="images/readme/46aed383-image_117.png" />
    </Frame>

    <span id="step-4-insert-aws-credentials" style={{ display: "block", scrollMarginTop: "7rem" }} />

    <span id="step-5-insert-aws-credentials-in-tatari" style={{ display: "block", scrollMarginTop: "7rem" }} />

    Then add the credentials:

    1. Copy the AWS credentials Northbeam created when you connected your Tatari ID.
    2. In Tatari, go to **Account Settings → Integrations** and select **AWS Data Sharing**.
    3. Enter the AWS credentials from Northbeam and click **Add**.

    **If you skip this step:** the integration isn't complete, so Tatari data doesn't reach Northbeam.
  </Step>

  <Step title="Confirm tracking">
    **Quick check:** your Tatari data shows up under the **Clicks & Matchbacks** attribution model. "Matchbacks" are the attributed orders Tatari reports. On a new integration, it can take up to **7 days** for all your data to fill in, oldest first.

    For a full check:

    * **Connection syncing:** follow [Checking platform connections](/docs/checking-api-connections) to confirm the account shows as connected and data is arriving.

    If a check fails, see [Troubleshooting Northbeam data](/docs/troubleshooting-tracking-issues).
  </Step>
</Steps>

## Need help?

<CardGroup cols={2}>
  <Card title="Tatari FAQ" icon="circle-question" href="/docs/channels/tatari/faq">
    Where Tatari data shows up, how often it updates, and missing revenue.
  </Card>

  <Card title="Troubleshooting Northbeam data" icon="wrench" href="/docs/troubleshooting-tracking-issues">
    Start here if a check above fails.
  </Card>
</CardGroup>
