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

# Singular

> Enrich your analytics in Singular with event data from your warehouse.

## Overview

This integration lets you send server-to-server events to Singular without writing a custom pipeline. Whether you're calculating cross-device attribution, analyzing ROI, or using Singular for fraud prevention, including event data helps you have a more complete analytics view.

## Supported syncing

| Type | Description | Supported Sync Modes |
| - | - | - |
| **Events** | Hightouch supports syncing in-app events to Singular | Insert only |

## Connect to Singular

Start by creating an instance of Singular destination in Hightouch. Upon creating your instance, you must enter a Singular API key for authentication.

### Authenticating with an API key

To get your API key, navigate to `Developer Tools` > `API Keys` and copy your API key into Hightouch.

![](https://mintcdn.com/hightouch-3c037897/L_vQfA0JQEpeGUUo/images/destinations/destination-singular-api-key.png?fit=max\&auto=format\&n=L_vQfA0JQEpeGUUo\&q=85\&s=be1cba1a6506f00ec4b818e0801f8447)

## Syncing data

### Events

Any records added to [your source](https://docs.hightouch.com/getting-started/concepts.md) are treated as new events and are sent to Singular when your sync runs.

> [!WARNING]
>
> To ensure syncs send each event, your event model must use a truly unique [primary key](https://docs.hightouch.com/getting-started/concepts.md#unique-primary-key-requirement). See the [events syncs](https://docs.hightouch.com/syncs/types-and-modes.md#event-syncs) documentation for more information.

#### Select API version

Singular's EVENT endpoint has two versions. V2 identifies devices with the Singular Device ID (SDID). V1 uses legacy device identifiers such as IDFA, IDFV, AIFA, and ASID.

> [!WARNING]
>
> Singular accounts created on or after July 15, 2026 must use V2. Singular
> rejects V1 requests from these accounts.

For standard event syncs, choose the version under **Which Singular EVENT API version should this sync use?**:

| Version | Use when |
| - | - |
| **V2 (SDID)** | Your Singular account was created on or after July 15, 2026, or your account has SDID enabled. |
| **V1** | Your account predates July 15, 2026 and uses legacy device identifiers. |
| **Automatic (legacy)** | Your sync predates this setting. Hightouch picks V2 for rows with an SDID value and V1 otherwise. |

V2 requires mapping the `sdid` field. Rows with an empty SDID value are rejected with an error instead of being sent to V1. New syncs default to V2.

> [!NOTE]
>
> Custom ID event syncs always use V1. Singular doesn't document a V2 equivalent
> for custom ID events.

`Platform`,`Package Name`, and `OS Version` fields are the minimum required fields to make the API call to Singular. For a richer analytics, we recommend that you provide all relevant fields in your use case.

![](https://mintcdn.com/hightouch-3c037897/L_vQfA0JQEpeGUUo/images/destinations/destination-singular-dst-mappings.png?fit=max\&auto=format\&n=L_vQfA0JQEpeGUUo\&q=85\&s=d9f53848c07d1d7885403899182b9ccb)

> [!NOTE]
>
> The supported platforms are `iOS` and `Android`, case sensitive. If the
> platform is `Android`, `andi` field is also required.

> [!WARNING]
>
> If you don't map the `ip` field, it will be defaulted with one from
> Hightouch's servers.

You can use custom mappings to attach custom data relevant to your application.

![](https://mintcdn.com/hightouch-3c037897/L_vQfA0JQEpeGUUo/images/destinations/destination-singular-dst-custom-mappings.png?fit=max\&auto=format\&n=L_vQfA0JQEpeGUUo\&q=85\&s=bc3852b5b4ab790fe15967e3f90e92a3)

> [!NOTE]
>
> Custom mappings are included as the [`e`
> parameter](https://support.singular.net/hc/en-us/articles/31496864868635-Server-to-Server-EVENT-Endpoint-API-Reference)
> of the API request payload.

For more information about required fields, refer to [Singular's documentation](https://support.singular.net/hc/en-us/articles/31496864868635-Server-to-Server-EVENT-Endpoint-API-Reference).

## Tips and troubleshooting

To see the exact API requests and responses from each sync run, use the [live debugger](https://docs.hightouch.com/syncs/debugger.md). To get notified by Slack, PagerDuty, SMS, or email when a sync fails, set up [sync alerts](https://docs.hightouch.com/syncs/alerting.md). If you run into an issue this page doesn't cover, [contact support](#pylon-chat).

If you receive errors, ensure that your including all of Singular's required fields: `Platform`, `Package Name`, `OS Version` and `andi` if your `Platform` is `Android`.