---
title: "Connect Skimlinks to Rig — Rig guide"
description: "Connect Skimlinks to Rig with API credentials. Sync commissions, daily performance, link and page reports and payment status."
canonical: "https://rig.so/guides/connect-skimlinks"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Skimlinks to Rig

Sync Skimlinks commissions, daily performance reports, link and page reports, products bought and payment status into Rig. Skimlinks connects with the client ID and secret from your Publisher Hub.

## Before you start

- You need a Skimlinks Publisher Hub login for the publisher account you want to sync.
- Know your numeric publisher ID, the site ID shown in the Publisher Hub.

## Step 1: Get your Skimlinks API credentials

1. Sign in to the Skimlinks Publisher Hub.
2. Go to **Toolbox**, then **APIs**, then **API Authentication credentials**.
3. Copy the client ID and the client secret.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **Skimlinks**, open the card and click `Connect`.
3. **Client ID**: The client ID from the Publisher Hub.
4. **Client Secret**: The client secret from the Publisher Hub.
5. **Publisher ID**: Your numeric Skimlinks publisher (site) ID.
6. **Days of history on first sync (optional)**: Leave it at 365 unless you want a shorter first load. It applies to the daily reports and payment status. Commissions always load in full.
7. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
8. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

Skimlinks lands in its own `skimlinks` schema in your warehouse:

- **Commissions**: one row per commission, including the negative rows some networks post for reversals.
- **Daily performance reports**: snapshots by date, merchant, page, link and device.
- **Click and page reports**: link and page level aggregates.
- **Products bought**: the products behind each sale.
- **Payment status**: invoice and payment state for each commission.
- **Deactivated merchants**: merchants that are no longer active.

The product report covers sales through the Awin, CJ, Rakuten, Impact, Partnerize and Pepperjam networks only.

## Good to know

- Commissions change after the sale, and a reversal can arrive as a separate negative row. Rig keeps those rows because that is how cancellations reconcile.
- Payment status often flips from unpaid to paid months later, so Rig re-pulls the history window each run.
- Skimlinks limits the link and page reports to 5 requests a minute and 100 an hour. Rig uses range queries to stay inside that.
- Skimlinks access tokens last about 7 days, and Rig requests a new one when needed.
- To disconnect Skimlinks, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Find the content that earns
- Understand merchant mix and risk
- Reconcile earned against paid

[More ideas for using Skimlinks](https://rig.so/integrations/skimlinks)

## Skimlinks documentation

- [Skimlinks Reporting API](https://developers.skimlinks.com/reporting.html)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-skimlinks)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)