---
url: /guides/api/agnostic/api-source.md
---
# API Source

Connect your non-Shopify website to Elevar and get the scripts for tracking.

## Overview

Follow this guide to learn how to configure the API Source in Elevar. The API
Source allows you to connect a non-Shopify website to Elevar so events can be
captured, enriched, and forwarded to your configured destinations.

Before starting, you must contact your Elevar representative or support team to
enable the API Source for your account.

Setting up the API Source includes:

* Configuring your general settings
* Setting up browser scripts for client-side tracking
* Optionally configuring server-to-server tracking
* Setting up consent integration

::: tip

If someone from your team already completed the API Source setup, you can skip
directly to the [Browser Setup](#browser-setup) section to retrieve the scripts
needed for your website pages.

:::

## General Settings

After your Elevar account is ready, navigate to **My Tracking** and click **Set
Up Now** on the API Source card to begin the setup process:

![API Source](/img/api-source.webp)

Click **Get Started** in the API Source overview, then in **General Settings**:

1. Answer whether you have multiple subdomains (e.g., `blog.website.com` and
   `shop.website.com`)
2. If you select **Yes**, enter your overarching domain (e.g., `website.com`)

::: warning

Use your root domain (e.g., `example.com`), not a subdomain. This ensures proper
cross-domain tracking and attribution. For more details, see
[Overarching Domain](/guides/api/additional-resources/overarching-domain).

:::

### Configure Client-Side Tracking

Under **Advanced Options**, decide whether to **Allow Google Tag Manager for
client-side tracking**:

![Client-Side Tracking Method](/img/agnostic-client-side-tracking.webp)

* **Using Elevar** (Recommended): Leave unchecked and Elevar will manage
  client-side tracking automatically during destination setup
* **Using Google Tag Manager**: Check the box if you want to use your own GTM
  container for client-side tracking

Click **Save & Continue** to proceed.

## Browser Setup

Copy the browser script provided in this section, you'll need it for the
[Install Scripts](/guides/api/browser-setup/install-scripts) guide.

![Browser Setup](/img/browser-setup.webp)

If you send events from the browser, click **Generate Signing Key** under
**Browser Key**. This allows our servers to verify and process your browser
events (events sent without this won't reach us).

**Browser Key** is marked as optional because it is only needed for browser
events. If you only use the browser script to collect attribution data and send
your events server-to-server, you can skip it.

Click **Mark as Complete** to proceed.

## Server Setup

Select whether you'll send server-to-server events in addition to browser
events.

![Server Setup](/img/server-setup.webp)

* Select **Yes** if you plan to send events from your server for improved
  tracking accuracy
* Select **No** if you're only implementing browser-to-server events

::: tip

For detailed implementation instructions on server-to-server tracking, see the
[Server Setup](/guides/api/agnostic/server-setup) guide.

:::

Click **Save & Continue** to proceed.

## Consent

Configure how Elevar handles user consent:

1. Choose whether to enable Consent integration
2. If enabled, select consent fallback behavior when consent choices aren't
   received

::: info

The source where Elevar reads consent signals depends on your client-side
tracking method:

* **Using Elevar**: You need to manually integrate your CMP with Elevar's
  Consent API
* **Using Google Tag Manager**: Reads from Google Consent Mode

:::

Click **Save & Continue** to finish the API Source setup.
