Revenue tracking

HTML

Use this method if you or your developer can edit your website's files.

You paste one line of code into the header that all your pages share. The header is the hidden part of a page between <head> and </head>. Do it once and every page is covered.

This step tracks visits only: which pages people open and which ad or site brought them. Sales are not tracked yet. If you sell on your site, there is one more step at the end.

1. In AdRiseLab, open Revenue → Setup, select the HTML tab and copy the snippet.
2. Open the file that holds your shared header. It is often called index.html, header.html, header.php, base.html or layout.html.
3. Paste the snippet on a new line just before </head>. If each page has its own header, do this on every page.
4. Save and publish your site the way you normally do.
5. Reload your website. It will look the same; that is expected. To confirm it works, see Verify the installation below.
6. Selling on your site? Continue with Connect your sales, further down. Without it, Revenue shows visits but no sales.

<head>
  <!-- your existing tags stay as they are -->
  <title>My store</title>

  <script defer data-site="YOUR_PUBLIC_SITE_KEY"
    data-consent="required"
    src="https://adriselab.com/s.js?v=5"></script>
</head>

Shopify

Shopify stores do not paste a snippet. You connect the store once, through a Shopify app you create yourself, and AdRiseLab installs the tracker on your storefront and starts receiving your paid orders. It takes about ten minutes and does not change how your store looks.

Why an app: Shopify's checkout runs no third-party script, so a sale can never be seen from the browser. It has to be reported by Shopify itself, and Shopify only reports orders to an app the store has installed. The app is yours: it lives in your own Shopify organization, it has two permissions, and you can uninstall it at any time.

What you need: the store owner account, or a staff account that can create and install apps. The app and the store must belong to the same Shopify organization, which is the case when you create the app from the account that owns the store. Your storefront must be a Shopify Online Store theme; see the note below for headless storefronts.

1. Open the Shopify Dev Dashboard at dev.shopify.com/dashboard and sign in with the account that owns your store.
2. Click Create app and give it a name you will recognise later, for example AdRiseLab Revenue. The name is only shown to you.
3. Open the app's configuration and find Access scopes. Add exactly two: read_orders and write_script_tags. Do not add anything else; AdRiseLab reads no customers and no products.
4. Release the app version. If Shopify shows a dialog asking for a version name or message, you can leave those fields empty.
5. Back on the app's Home page, click Install app, choose your store, and approve the installation in Shopify admin. The approval screen lists the same two permissions.
6. Open the app's Settings and find Credentials. Copy the Client ID and the Client secret. Treat the secret like a password.
7. In AdRiseLab, open Revenue, open the website picker and choose Add Shopify store (on your first visit, click Add your Shopify store instead under the website form). Enter your store's myshopify.com address (for example your-store.myshopify.com, not your custom domain), paste the Client ID and the Client secret, and click Connect store.
8. Your store is now its own website in the picker: its storefront address is the website's domain, and its currency and timezone come from Shopify. Revenue → Settings → Shopify shows Connected to your-store.myshopify.com. If one of your websites was already on that domain, the store is connected to it instead.
9. Open your store in a new browser tab, accept analytics cookies if your store shows a banner, and browse a couple of pages. Revenue → Setup turns green when the first event arrives.

Google Tag Manager

Use this method if your website already has Google Tag Manager (GTM) installed, which is common when a marketing team manages tracking tags. You can then add the tracker without touching your website's code. What you need: Publish access to your site's GTM container at tagmanager.google.com.

If GTM is not on your site yet, installing it only for AdRiseLab adds a step. Use the HTML method instead.

1. In AdRiseLab, open Revenue → Setup, select the Tag Manager tab and copy the snippet.
2. Open tagmanager.google.com and select the container for your website.
3. Go to Tags and click New. Name the tag something recognisable, for example AdRiseLab Revenue.
4. Click Tag Configuration and choose Custom HTML. Paste the snippet into the HTML box.
5. Click Triggering and choose All Pages, so the tracker loads on every page.
6. Click Save.
7. Optional: click Preview, enter your website address and confirm the new tag is listed under Tags Fired.
8. Click Submit, then Publish. The tag reaches your live site only after you publish.

<script defer data-site="YOUR_PUBLIC_SITE_KEY"
  data-consent="required"
  src="https://adriselab.com/s.js?v=5"></script>

Next.js

This method is for websites built with Next.js using the App Router, which means the project has an app folder with a layout.tsx (or layout.js) file in it. This is a developer task. If you do not work on the code yourself, forward this section and the snippet to whoever does.

The snippet goes into the root layout, the file that wraps every page. It uses Next.js's own Script component, which loads the tracker after the page becomes interactive, so it does not slow the first paint.

1. In AdRiseLab, open Revenue → Setup, select the Next.js tab and copy the snippet.
2. Open app/layout.tsx (or app/layout.js), the root layout at the top of the app folder, not one inside a subfolder.
3. Add import Script from "next/script"; with the other imports at the top of the file, if it is not already there.
4. Paste the <Script … /> element inside <body>, for example right after {children}.
5. Run the site locally or deploy it as usual. The tracker loads on every route, including pages reached through client-side navigation.

import Script from "next/script";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        {children}
        <Script
          src="https://adriselab.com/s.js?v=5"
          data-site="YOUR_PUBLIC_SITE_KEY"
          data-consent="required"
          strategy="afterInteractive"
        />
      </body>
    </html>
  );
}

Stripe

Use this if your website sends buyers to Stripe Checkout and your own server creates the Checkout Session. Stripe's checkout page is on Stripe's domain, so the tracker cannot see the payment. Two steps close the gap, and you need both: Stripe tells Revenue about each payment, and your server tells Stripe which visitor is paying.

The second step is a developer task and nothing can do it for you. Without it every payment is still counted, but it is credited to no visit and no ad.

About the key you hand over: it has one permission, so it can manage webhooks and nothing else. It cannot read payments or customers, and it cannot charge, refund or move money. AdRiseLab uses it for a single request, asking Stripe to create the webhook, and then discards it. What AdRiseLab keeps is the signing secret Stripe returns for that webhook, which can only confirm that an incoming payment event really came from Stripe. You can delete the key in Stripe as soon as the card shows Connected, and the webhook stays visible and removable in your Stripe account under Developers → Webhooks.

1. In AdRiseLab, open Revenue → Settings → Stripe and click the restricted API key link. It opens Stripe with the one permission, Webhook Endpoints: Write, already selected. Create the key without changing any permissions and copy it.
2. Back in the Stripe card, paste the key and click Connect Stripe. The key is used once to register a webhook on your Stripe account and is not stored.
3. In your server code, find where the Checkout Session is created. Read the adriselab_vid cookie from the buyer's request and add it to the session's metadata under the same name, as in the code below.
4. For subscriptions, add the same value to subscription_data.metadata as well, so renewals are credited too.
5. Deploy, make a purchase through your own checkout and check that it appears once in Revenue → Transactions with the source of the visit.

const visitor = (await cookies()).get("adriselab_vid")?.value ?? "";

const session = await stripe.checkout.sessions.create({
  mode: "payment",
  line_items: [/* your items */],
  metadata: { adriselab_vid: visitor },
  // Subscriptions only, so renewals are credited too:
  // subscription_data: { metadata: { adriselab_vid: visitor } },
});

Shopify

There is no separate step for orders. The connection described under Install the tracker → Shopify already registered the webhooks, so paid orders and refunds start arriving as soon as the card shows Connected.

How a sale is credited to an ad: a buyer clicks an ad and lands on your store, where the script records the visit and the ad it came from. When they add to cart, the script writes its visitor ID into the cart as a hidden attribute. Shopify copies cart attributes onto the order, and when the order is paid Shopify sends it to Revenue with that ID attached. Revenue then looks up that visitor's visits in the 30 days before the payment and credits the sale to the visit, the campaign and the ad behind it.

Some orders never have a cart: Buy it now and the express buttons go straight from the product page to checkout. Those orders are credited from the campaign tags on the page the visit landed on, which Shopify records on the order. That credits the campaign and the ad, though not the individual visit.

The script also sends two events you can use in goals and funnels without adding code: add_to_cart and initiate_checkout. Express buttons such as Shop Pay render inside Shopify's own frames, so they are not seen as initiate_checkout; the order is still recorded.

About the secret you hand over: Shopify signs every order it sends with your app's Client secret, so AdRiseLab has to keep it to check that an order is genuine. Unlike a Stripe key, it cannot be discarded after connecting. It is stored encrypted, never shown again and never sent to a browser. The app has two permissions, reading orders and managing script tags: it cannot read customers or products, and it cannot change, cancel or refund an order. From each order Revenue keeps the amount, currency, time, order number, sales channel, discount codes and item names. It does not keep the buyer's name, email, phone or address.

1. Place a test order on your store from a normal browser window, after accepting analytics cookies. A real payment that you refund afterwards works; Shopify's test orders are ignored on purpose, because they are not money.
2. Open Revenue → Transactions. The order appears within a minute, under the same order number you see in Shopify, for example #1001.
3. Check that the order shows the source of the visit. If it shows Unattributed, see the table below.
4. Refund the test order in Shopify and confirm the refund is subtracted from that sale.