# Custom conversions

Source: https://skro.eu/docs/postback/custom-conversions

Create custom conversion events in Skro, choose how they affect reports, and map event names for each traffic source.

Custom conversions let you report separate events such as registrations, purchases, upsells, and deposits. Send the event value in the `ce` parameter of your Skro postback URL.

```text
https://skrotrack.com/postback?clickId=REPLACE&ce=InitiateCheckout
```

Your subscription determines how many custom events you can create, up to 20. Use a single-word event value and match its spelling and capitalization across your setup.

<Callout title="Skro events and traffic source events">
Skro custom conversions are configured independently of the custom conversion features in Meta or TikTok. A Skro custom event can map to a standard event supported by your traffic source.
</Callout>

## Event settings [#event-settings]

These settings determine how an event appears in reports and whether it is sent to the traffic source.

| Setting | Effect |
| --- | --- |
| **Custom Conversion Event Name** | Sets the column title in reporting views. |
| **Values of the CE parameter** | Defines the accepted `ce` values. You can add multiple values for providers that use different names. |
| **Use as Approved conversion type** | Includes the event in **Conversions (Approved)** and the CR, CV, and AP calculations. |
| **Include in Conversions (All) column** | Includes the event in the total conversion count. |
| **Include in Revenue column** | Includes the event’s payout in revenue. |
| **Include in conversions Daily Cap value** | Counts the event toward the offer’s configured daily conversion cap. |
| **Send postback to Traffic Source** | Sends the event to the traffic source through its postback or conversion API integration. |
| **Include Payout value in postback** | Includes the payout when sending the event to the traffic source. |
| **Include in Cost column** | Includes the event in cost calculations for CPA and CPS (RevShare) campaign cost models. |

## Create conversion events [#create-conversion-events]

<Steps>

### 1. Open Custom Conversions [#1-open-custom-conversions]

In Skro, go to **Custom Conversions** and select **Create**.

![Open Custom Conversions in Skro](/images/docs/shopify/shopify1.png)

### 2. Create an AddToCart event [#2-create-an-addtocart-event]

Set the event name and accepted `ce` value to **AddToCart**, then choose the reporting options you need.

![Configure the AddToCart event](/images/docs/shopify/shopify28.png)

```text
https://skrotrack.com/postback?clickId=REPLACE&ce=AddToCart
```

### 3. Create an InitiateCheckout event [#3-create-an-initiatecheckout-event]

Create a second event with the value **InitiateCheckout**.

![Configure the InitiateCheckout event](/images/docs/shopify/shopify2.png)

```text
https://skrotrack.com/postback?clickId=REPLACE&ce=InitiateCheckout
```

### 4. Create a Purchase event [#4-create-a-purchase-event]

Create an event with the value **Purchase**. Configure its revenue and approved-conversion settings to match your reporting needs.

![Configure the Purchase event](/images/docs/shopify/shopify3.png)

Include the revenue and transaction identifier when reporting a purchase:

```text
https://skrotrack.com/postback?clickId=REPLACE&payout=REPLACE&transactionId=REPLACE&ce=Purchase
```

</Steps>

Replace each placeholder with the appropriate value or provider macro. See the [postback parameter reference](/docs/postback/parameters-in-postback-urls) for field descriptions.

## Map event names for a traffic source [#map-event-names-for-a-traffic-source]

Use custom conversion mappings when traffic sources expect different event names for the same internal Skro event. Your incoming postback can keep one `ce` value while Skro sends the mapped event name to each source.

1. Go to **Traffic Sources** and edit the relevant source.

![Edit a traffic source](/images/docs/custom-conversion/ccm-1.png)

2. Enable **Allow custom conversion event name mappings**.
3. Select **Add Mapping**. You can configure up to 20 mappings.
4. Choose the **Custom Conversion** and enter the **New Event Name** required by the traffic source.

![Configure custom conversion event mappings](/images/docs/custom-conversion/ccm-2.png)

### Example: Meta and NewsBreak [#example-meta-and-newsbreak]

Suppose a conversion arrives with `ce=Purchase`. The same internal event can be sent as:

| Traffic source | Outgoing event name |
| --- | --- |
| Meta | `Purchase` |
| NewsBreak | `complete_payment` |

The incoming postback remains the same:

```text
https://skrotrack.com/postback?clickId=REPLACE&payout=REPLACE&transactionId=REPLACE&ce=Purchase
```

## Verify your events [#verify-your-events]

Trigger a test event using a real Skro click ID. Confirm that the event appears in its reporting column, contributes to the intended totals, and uses the expected outgoing event name in the traffic source.

If the event is missing, check that the incoming `ce` value matches one of the event’s configured values. If it appears in Skro but not in the source, check **Send postback to Traffic Source**, the selected integration, and any event-name mapping.

## Related guides [#related-guides]

<Cards>
  <Card title="Postback URL parameters" href="/docs/postback/parameters-in-postback-urls" />
  <Card title="Shopify integration" href="/docs/integrations/shopify-and-skro-integration" />
  <Card title="Meta Conversions API" href="/docs/facebook/how-to-integrate-facebook-capi" />
</Cards>