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

# Track organic posts

> See, for each creator and post, how many people clicked a creator link and reached your result.

A creator's organic post brings people to your site. Some of them do something that you care about: they buy, sign up, or attend a webinar. That is your result. SideShift follows each person from the creator link to the result. It credits the result to the creator, and to the post, that brought the person.

Use this page to send your events to SideShift and read the results in **Analytics → Attribution**.

> [!NOTE]
>
> Pixel and store tracking must be enabled for your company. If you do not see **SideShift Pixel** under **Ads → Settings → Integrations**, contact SideShift.

## Set up your sites

1. Open **Ads → Settings → Integrations**, then **Manage** on **SideShift Pixel**. Add each site that a person goes through as a **Website**: the landing page, the sign-up page, and the checkout. Give each one its name and its public HTTPS domain. See [SideShift Pixel](https://docs.sideshift.app/platform/store-attribution.md).

2. Paste the script of each Website into the `<head>` of its pages. See [Install SideShift Pixel](https://docs.sideshift.app/pixel/installation.md). Connect your consent manager: the script records nothing before the person gives consent.

3. On the page that a person reaches after sign-up, tell SideShift who the person is, then send the event. Call `identify` first and wait for it, so that the event carries the person's email hash:

   ```javascript theme={"system"}
   async function reportRegistration(email) {
     await window.sideshift?.identify(email);
     await window.sideshift?.track('registered');
   }
   ```

   The `?.` makes the call do nothing when the script has not loaded or the person has not given consent. The script hashes the email in the browser. The raw email never leaves the browser. See [Identify a shopper](https://docs.sideshift.app/pixel/events.md#identify-a-shopper).

4. For an event that does not happen on one of your pages, send the event from your tool. See [Send an event from a tool](#send-an-event-from-a-tool).

The script runs on the Website's own domain and on its subdomains. A page on another domain, such as a hosted checkout or a webinar tool's shared domain, cannot send its event with the script. SideShift refuses events from that page. Send that event through the events endpoint instead.

After you send an event, SideShift lists it in the Website's card. The card shows each event name from the last 90 days with its count and the time of the last event. Use it to check that your set-up works.

### Event names from the script

`track` takes the event name as its first argument. SideShift makes the name lowercase and replaces spaces and hyphens with `_`. `Webinar Attended` becomes `webinar_attended`. The result must have 1 to 60 lowercase letters, digits, or `_`. SideShift does not record an event with another name. It also does not record the names `comment`, `dm_sent`, `link_click`, `store_order`, `identify`, `consentwithdrawn`, `custom`, and `saleofdataoptin`.

To give an event a value, pass `value` and `currency` in major units:

```javascript theme={"system"}
await window.sideshift?.track('purchased', { value: 49, currency: 'USD' });
```

## Send an event from a tool

Use the events endpoint when an event happens in a tool: a webinar platform, a course checkout, or a no-code automation. Authenticate with the **API key** of the Website that the event belongs to. The key starts with `ss_orders_`. Keep it secret. A Shopify store's key does not work here.

Download the [OpenAPI specification](https://app.sideshift.app/openapi/commerce-orders.yaml) for client generation.

```http theme={"system"}
POST https://app.sideshift.app/api/commerce/events
Authorization: Bearer YOUR_ORDERS_API_KEY
Content-Type: application/json
```

```json theme={"system"}
{
  "event": "webinar_attended",
  "email": "shopper@example.com",
  "occurredAt": "2026-11-11T19:05:00Z",
  "eventId": "webinar-2026-11-11-1042"
}
```

| Field | Required | Meaning |
| - | - | - |
| `event` | Yes | The event name. 1 to 60 lowercase letters, digits, or `_`. The names `comment`, `dm_sent`, `link_click`, `store_order`, `identify`, `consentwithdrawn`, `custom`, and `saleofdataoptin` belong to SideShift and return `400`. |
| `email` | One of the three | The person's email, at most 320 characters. SideShift hashes it on arrival and does not store it. |
| `emailHash` | One of the three | SHA-256 of the lowercase email, as 64 lowercase hexadecimal characters. Make it as in [Buyer identity](https://docs.sideshift.app/pixel/orders-api.md#buyer-identity). |
| `visitorId` | One of the three | The visitor ID from `window.sideshift.getVisitorId()`, 16 to 128 letters, digits, `_`, or `-`. |
| `occurredAt` | No | When the event happened, as an ISO 8601 time with a UTC offset. The default is the time of the request. It cannot be more than five minutes in the future or more than 90 days in the past. |
| `eventId` | No | Your own ID for this event, 1 to 200 characters. Use it for safe retries. It cannot hold an email address or a phone number. |
| `valueCents` | No | The value of the event as an integer from 0 to 100,000,000,000 in the currency's minor unit: USD 49.00 is `4900`. Send it with `currency`. |
| `currency` | No | A supported uppercase ISO 4217 currency code. Send it with `valueCents`. |

Send `email` or `emailHash`, not both. Send `valueCents` and `currency` together or not at all. A request with any other field returns `400`. The body can have at most 64 KiB.

A raw `email` is the one difference from the [Orders API](https://docs.sideshift.app/pixel/orders-api.md). That endpoint takes hashes only. This endpoint takes a raw email because a webinar tool or an automation cannot hash it. SideShift hashes the email in memory and then drops it. It never stores or logs the raw email.

A `visitorId` of a visitor who withdrew consent, or whose data was erased, is ignored. The event is then kept with the email hash alone. When the request has no email, SideShift refuses it with `400`.

### Example

```bash theme={"system"}
curl -X POST https://app.sideshift.app/api/commerce/events \
  -H "Authorization: Bearer $SIDESHIFT_ORDERS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event":"webinar_attended","email":"shopper@example.com","eventId":"webinar-2026-11-11-1042"}'
```

In a no-code tool such as Zapier, add a **Webhooks by Zapier** action with the method `POST`, the URL above, the header `Authorization: Bearer YOUR_ORDERS_API_KEY`, and a JSON body that maps the person's email from the trigger and sets `event` to your event name.

### Responses and retries

A successful response is HTTP `200`:

```json theme={"system"}
{ "data": { "id": "3f0c8f0e-5a63-4a6b-9a39-0d6c3b8b2a55" } }
```

A repeat of the same `eventId` for the same Website and event name returns the first event's ID and writes nothing. Without `eventId`, each request writes a new event, so a retry can count a person twice. Send an `eventId` whenever your tool can retry.

| Status | Action |
| - | - |
| `400` | Correct the request fields. The `error` message names the first problem. |
| `401` | Check or replace the API key. |
| `404` | Store tracking is not enabled for this deployment. |
| `413` | Reduce the body below 64 KiB. |
| `429` | Retry after the `Retry-After` delay. The limit is 600 requests per minute for each Website. |
| `500` / `502` | Retry with the same `eventId`. |

## How people are matched

A person on your landing page and the same person on your checkout use two domains. The script's visitor ID is a cookie on one domain, so the two sites share no visitor. SideShift matches the person by the email hash instead.

When `identify` runs, or when an event carries an email or email hash, SideShift links the hash to the visitor. An event then counts the creator clicks of every visitor that the same hash is linked to, on any Website of your company. The same person is one person in the report, whatever the site.

A person who never gives an email, and never reaches an event that carries one, is known only by the visitor. Their later events on another domain cannot join their click.

The script's consent rules apply. The script records a visit, an identity, and an event only after the person gives consent. When the person withdraws consent, SideShift removes the visitor's identity links. An event that also has the person's email stays, without the visitor. SideShift deletes an event that has only the visitor and no email. The events endpoint has no consent check of its own. Send events only for people whose consent you hold. To erase a person's data, use [Erase a shopper](https://docs.sideshift.app/pixel/orders-api.md#erase-a-shopper). An erasure request for a Website deletes the person's events on that Website and removes the credit that came from their visits to it. The person's events on another Website of your company stay until you send an erasure request for that Website too.

## Creator links

A creator link is a URL to your site with the creator's `ss` code. The person opens your page and the script records the click. A creator's link in bio and a link that SideChat sends open a SideShift address first. SideShift counts the visit or tap, then opens your page with the creator's `ss` code. Each link must point to a page on one of your Websites.

* **Bio link.** The creator's link in bio. There is one link for each creator and brand, with one URL for each platform. A click on it credits the creator, but it cannot name a post. See [Link in bio](#link-in-bio).
* **Post link.** One link for each approved submission. SideShift makes it without a message.
* **DM link.** With SideChat on, the DM that the creator's account sends carries a link code. The code is the link of the post that got the comment. When the comment's post has no tracked link, the code is the creator's bio link. SideShift adds the code to a link that you chose: the campaign link, or the link that you set for that creator. The link must be on a connected Website. A creator's own referral link is sent as it is.

### Link in bio

Link in bio is off for a campaign until you turn it on. When it is on, SideShift creates the creator's link in bio for your brand when the creator's contract becomes active. SideShift does not create a link for a campaign-manager campaign. SideShift also does not create a link when your brand has no products and no valid website.

The link has the form `app.sideshift.app/b/{brand}/{creator}/{code}`. The code names the platform: `ig` for Instagram, `tt` for TikTok, `yt` for YouTube, `th` for Threads, `x` for X, `fb` for Facebook, `sc` for Snapchat, and `li` for LinkedIn. The creator gets one URL for each platform that the contract or the campaign names. When they name no platform, the creator gets Instagram, TikTok, and YouTube URLs.

SideShift does not send the URLs in a chat message. The creator finds them in the campaign, in the **Link in bio** row of the campaign overview. The row shows one URL for each platform, with a copy button. When you turn on link in bio after a creator is approved, the creator sees the URLs the next time they open the campaign. A later contract with your brand keeps the same URLs, and the link then follows the newer contract. The link continues to work after the contract ends.

The link opens a SideShift page with your products. When you picked products for the link, the page shows only those products, in the order that you picked them. When you picked no products, the page shows the campaign's products. When none of your picked products is on sale, the page also shows the campaign's products. When the campaign has no products, the page shows your catalog. When you have no products, or you choose **Website**, the link opens your website. An unknown link returns a 404 page.

A tap on a product or on your site adds these parameters to the URL:

* `utm_source`: the platform of the link, or `sideshift` for the link with no platform code.
* `utm_medium`: `bio`.
* `utm_campaign`: the campaign name as a slug.
* `utm_content`: the creator's part of the link.

A UTM parameter that is already in the URL keeps its value. When the URL is on one of your connected stores, SideShift also adds the creator's `ss` code. A store on `www.example.com` also covers a URL on `example.com`. Each platform's link has its own code, so store sales show which bio an order came from.

To turn on link in bio when you create or edit a UGC or influencer campaign, go to the **Requirements** step. Under **Creator accounts**, turn on **Send creators a link in bio**. In **Link opens**, select **Products** or **Website**. For **Website**, SideShift fills in your company website. You can enter another URL.

To change the setting of an existing campaign, open the campaign's **Edit** menu and select **Link in bio**. Select **Products** or **Website**. For **Products**, select the products that the page shows. A number on each selected product shows its place on the page. You can search for a product by name. The page shows up to 48 products. For **Website**, enter a URL. SideShift refuses social network and SideShift addresses. Select **Save**. When link in bio is off for the campaign, **Save** turns it on. When you switch to **Website**, SideShift keeps your product selection for a later switch back to **Products**.

To turn off link in bio, edit the campaign and turn off **Send creators a link in bio** in the **Requirements** step. SideShift then does not create new links for the campaign, and the campaign no longer shows the links to creators. Links that creators already put in their bios continue to work.

The campaign's creators table shows a **Bio link clicks** column. It counts the human visits to each creator's link in bio. SideShift counts a visit once for each visitor, hour, and platform. SideShift does not count link-preview fetches.

## Read the Attribution page

Open **Analytics → Attribution**. With no Website, the page asks you to connect one.

### Pick dates, filters and a result

Use the date filter to set the range.

Select **Filters** to open the filter panel. Use the filters to count only some creator links. You can pick more than one item in each filter, except **Post Type**: you pick one type. When you use two filters, a link must match both. The number on **Filters** is the number of items that you picked. Select **Clear Filters** to remove all of them.

| Filter | What it keeps |
| - | - |
| **Post Type** | The post links of posts of the type that you pick: videos and reels, carousels, or photos. This filter shows only when Instagram carousel tracking is on for your company. |
| **Product** | The links of submissions that have the product that you pick, and the SideChat links to that product. |
| **Brief** | The links of submissions that have a brief that you pick. When the submission has no brief, the brief of its post counts. |
| **Campaigns** | The creator links of the campaigns that you pick. |
| **Platforms** | The post links of posts on the platforms that you pick. A SideChat link with no post counts on the platform of the first DM that sent it. |
| **Creators** | The creator links of the creators that you pick. |
| **Post Tags** | The post links of posts that have the tags that you pick. **Any of** keeps a post with one or more of the tags. **All of** keeps a post with all of them. **Exactly** keeps a post with the tags and no other tags. |
| **Creator Tags** | The creator links of the creators that have a tag that you pick. |

A bio link, and a SideChat link with no post, have no post. They do not show when you pick a post type or a post tag. A bio link also does not show when you pick a platform. A SideChat link with no post shows only when you pick the platform of the first DM that sent it. A SideChat link that no DM sent yet counts as Instagram. The **Product**, **Brief**, and **Creator Tags** filters show only when your company has products on submissions, briefs with picks, or creator tags.

With a filter on, the counts, the value, and each creator's share are of the links that the filter keeps. **Views** shows the views of the creator's posts that match the campaigns, platforms, post tags and post type that you pick. With a product or a brief picked, it shows the views of the posts of the links that the filter keeps. The filters stay in the page address, so a link to the page opens with the same filters.

The table ranks creators by a result:

| Result | What it counts |
| - | - |
| **Store order** | Buyers of store orders that are not cancelled and not samples. |
| Your own events | Each event name that your Websites received in the last 90 days, such as **Registered** or **Webinar attended**. |

When your Websites sent no event of their own, the result is **Store order** and the filter panel has no **Result** section. When they sent events, select **Filters** and pick one result in the **Result** section. **Clear Filters** does not change the result. The page opens on **Store order** if your store has orders. Else it opens on the event that your sites sent most often.

The page has no model or window picker. It credits each person with your saved default model and window. The default is **Last non-direct click** with a 7-day window. Under this default, the credit goes to the last creator link, or other non-direct visit, that the person made before the result and inside 7 days.

### The table

The table has one row for each creator, ranked by the result. Select a column header to sort. Select a creator to see their posts, one row for each post link, the bio link rows, and the SideChat rows. Each platform's link in bio has its own row, for example **Bio link · Instagram**.

| Column | What it shows |
| - | - |
| **Creator** | The creator, or one of their posts or their bio link. Select a post name to open the post. |
| **Views** | The views of the creator's posts that went live in the date range, as the **Top Creators** table of **Analytics** shows them. |
| **Link clicks** | The people who clicked the row's creator links. |
| Your result | The people who reached the result, with the creator's share of all the people that creators brought to it. |
| **Conversion** | The result's count divided by **Link clicks**. It shows a dash when **Link clicks** is 0, or when the result's count is more than **Link clicks**. |
| **Value** | The credited value of the result in the date range. It shows only when the result has a value, and only to team members who can see financial data. |

When no creator brought anyone in the date range, the page shows **No activity in this range**. With a filter on, it shows **No activity for these filters**.

### Export the table

Select **Export** to download the table as a CSV file. The file has the result, the date range and the filters that are on the page. It has one row for each creator, and one row for each post, SideChat and bio link row of that creator. The columns are **Creator**, **Row** (the kind of row), **Name**, **Post URL**, and the columns of the table. **Value** and **Currency** are in the file only when the result has a value. **Export** shows only to team members who can see financial data.

### How SideShift counts

A count is a number of people. A person counts once, by the first event of the result that the person sent in the date range. A person is the email hash. An event with no email hash takes the email hash of its visitor: the hash of another event of that visitor, or the hash that `identify` linked to the visitor. So an event sent before `identify` and an event sent after it are one person. A visitor linked to two or more email hashes, such as a shared device, stays a person of its own. A visitor with no email hash is a person of its own.

* **Link click** counts people. A visitor linked to an email hash is that person, so a person who clicked on a phone and on a laptop counts once. A person counts once on a row, also when the person clicked more than one link of that row.
* **Store order** counts buyers, not orders. A buyer is the email hash of the order. An order with no email hash takes the email hash of the other orders of the same customer ID in that store, when those orders have one email hash. Else the buyer is the store's customer ID. A buyer with two orders in the range counts once, by the first order. An order with no buyer identity counts as one person.
* When your company has no event of the result in the date range, the result shows a dash. When it has events, a creator with none shows 0.
* **Value** is the sum of the credited value of all events of the result in the date range: every order and every event with a value, not only the first event of each person. When all the values have one currency, **Value** shows that currency. When they have more than one, SideShift converts each value to USD.

An event that your site sends counts on its creator's row as soon as it arrives. A **Store order** counts on a creator's row after SideShift builds the order's path, about 15 minutes after the order.

## Next steps

* [SideShift Pixel](https://docs.sideshift.app/platform/store-attribution.md)
* [Browser SDK reference](https://docs.sideshift.app/pixel/events.md)
* [Orders API](https://docs.sideshift.app/pixel/orders-api.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.