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

# Lemrock conversion tracking

> Install the Lemrock Pixel to see which Lemrock ads lead to sales on your site.

The Lemrock Pixel shows which Lemrock ads lead to sales on your site, so Lemrock can report your results and deliver more toward buyers.

## Before you start

* **Your pixel ID.** It looks like `lr_px_` followed by 22 characters. Your Lemrock contact gives it to you.

## The four events

Lemrock tracks four events. Send all four.

| Event | When it happens |
| - | - |
| `order_created` | a visitor places an order |
| `checkout_started` | a visitor starts checkout |
| `items_added` | a visitor adds an item to the cart |
| `contents_viewed` | a visitor views a product |

All four take the same fields: the amount, the currency and the items involved. Send them whenever you have them. See [Event fields](/en/conversion-tracking/reference#event-fields).

## Choose your method

<CardGroup cols={3}>
  <Card title="Google Tag Manager" icon="tags" href="/en/conversion-tracking/gtm/setup">
    No code: configuration in GTM only.
  </Card>

  <Card title="Shopify" icon="shopify" href="/en/conversion-tracking/shopify">
    One snippet pasted in your Shopify admin.
  </Card>

  <Card title="Script" icon="code" href="/en/conversion-tracking/script">
    Code in your site.
  </Card>
</CardGroup>

You can mix GTM and script, for example loading the pixel with GTM and reporting an event from your code, but report each event one way only.

Alongside any method, your backend can also send orders through the [server API](/en/conversion-tracking/server-api).


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