Home Integrations Singular Integration

Singular Integration

Last updated on May 27, 2026

This guide explains how to set up the integration between Singular and UCLIQ. The integration is based on postbacks: Singular sends conversion data back to UCLIQ, and UCLIQ attributes the conversion using the click_id.

1. Integration Logic

When a user clicks a UCLIQ tracking link, UCLIQ generates a unique click_id.

This click_id must be passed to Singular during the click flow. Later, when Singular records an install, purchase, subscription, revenue event, or custom event, Singular sends a postback to UCLIQ and includes the same click_id.

UCLIQ uses this click_id to match the conversion with the original click, offer, and publisher.

2. Base Postback URL

The postback URL has the following structure:

https://client.utrfk.com/pb/aaabbbcccddd

Where:

client.utrfk.com — the client’s specific postback domain.

aaabbbcccddd — the client’s specific security key.

This means the client should not copy the example URL as-is. They need to use their own postback domain and security key from UCLIQ.

Example:

https://track.ucliq.com/pb/VpJjTBwsaZWk6KRigzaLkzmmpoK9ubo4P6MdE5C2QrY

3. Postback Parameters

Required Parameter

click_id=

This is the most important parameter. It is mandatory because UCLIQ uses it to attribute the conversion.

In Singular templates, the UCLIQ click ID is passed through this macro:

{cl}

So the parameter should be added like this:

click_id={cl}

Optional Parameters

sum=

The purchase, subscription, or revenue amount. It should be passed as a decimal value with a dot separator.

Examples:

0.01
10.50
125.99

In Singular, use:

{CONVERTED_REVENUE}

currency=

The currency of the amount. It should be passed in ISO 3-letter format.

Examples:

USD
EUR

In Singular, use:

{CURRENCY}

goal=

The conversion goal. It can be used to separate installs, revenue events, custom events, purchases, and other actions.

The value should be alphanumeric, without spaces or special characters.

Examples:

INSTALL
CPA
CPS
CUSTOM
PURCHASE

Important: If the offer in UCLIQ is configured in Goals mode, the goal value must match the goal alias configured in UCLIQ.

tid=

A unique transaction ID generated on Singular’s side. This parameter is optional, but strongly recommended because it helps prevent duplicate conversions.

In Singular, use:

{RAND}

Example:

tid={RAND}

If several events may be sent for the same click_id, it is better to always pass a unique tid.

ext1..ext6=

Additional fields that can be used to pass extra data from Singular to UCLIQ.

For example, ext1 can be used to pass the Singular event name:

ext1={EVTNAME}

And ext2 can be used to mark the platform:

ext2=ANDROID

Or:

ext2=iOS

4. General Singular Postback Template

The general template from the file is:

https://client.utrfk.com/pb/aaabbbcccddd?sum={CONVERTED_REVENUE}&currency={CURRENCY}&click_id={cl}&goal=CPA&ext1=TESTCONVERSION

Example of a final URL:

https://track.ucliq.com/pb/VpJjTBwsaZWk6KRigzaLkzmmpoK9ubo4P6MdE5C2QrY?sum=0.01&currency=USD&click_id=06cb93120683337e9ebd7d8b3dea0f9c&goal=CPA&ext1=TESTCONVERSION

5. Android Postback Templates

Install Postback

Use this postback to send attributed installs:

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=INSTALL&tid={RAND}&ext2=ANDROID

This sends:

click_id={cl} — the UCLIQ click ID
goal=INSTALL — the install goal
tid={RAND} — a unique transaction ID
ext2=ANDROID — Android platform marker

Revenue Event Postback

Use this postback for revenue events, such as purchases or subscriptions:

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=CPS&sum={CONVERTED_REVENUE}&currency={CURRENCY}&ext1={EVTNAME}&tid={RAND}&ext2=ANDROID

This sends:

goal=CPS — revenue conversion
sum={CONVERTED_REVENUE} — revenue amount
currency={CURRENCY} — revenue currency
ext1={EVTNAME} — Singular event name
tid={RAND} — unique transaction ID
ext2=ANDROID — Android platform marker

Custom Event Postback

Use this postback for custom events:

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=CUSTOM&ext1={EVTNAME}&tid={RAND}&ext2=ANDROID

Here, ext1={EVTNAME} helps show which custom event was passed from Singular.

Fraud Install Postback

Use this postback for installs that Singular marks as fraud:

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=INSTALL&ext1=FRAUD&tid={RAND}&ext2=ANDROID

Here, ext1=FRAUD is used to mark the install as fraud.

6. iOS Postback Templates

Install Postback

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=INSTALL&tid={RAND}&ext2=iOS

Revenue Event Postback

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=CPS&sum={CONVERTED_REVENUE}&currency={CURRENCY}&ext1={EVTNAME}&tid={RAND}&ext2=iOS

Custom Event Postback

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=CUSTOM&ext1={EVTNAME}&tid={RAND}&ext2=iOS

Fraud Install Postback

https://client.utrfk.com/pb/aaabbbcccddd?click_id={cl}&goal=INSTALL&ext1=FRAUD&tid={RAND}&ext2=iOS

7. What Needs To Be Replaced

Before adding the postback to Singular, replace:

client.utrfk.com

With the client’s actual UCLIQ postback domain.

Replace:

aaabbbcccddd

With the client’s actual security key.

Do not manually replace Singular macros such as:

{cl}
{RAND}
{EVTNAME}
{CONVERTED_REVENUE}
{CURRENCY}

Singular will automatically replace these macros with real values when sending the postback.

8. Important Notes

The most important parameter is:

click_id={cl}

Without it, UCLIQ will not be able to attribute the conversion.

For revenue events, pass:

sum={CONVERTED_REVENUE}
currency={CURRENCY}

This allows UCLIQ to receive the conversion amount and currency.

For repeated events or multiple events under the same click, use:

tid={RAND}

This helps UCLIQ identify each transaction as unique and avoid duplicate processing.

To separate platforms, use:

ext2=ANDROID

For Android, and:

ext2=iOS

For iOS.

To pass the event name from Singular, use:

ext1={EVTNAME}

For fraud installs, use:

ext1=FRAUD

9. Recommended Setup Flow

  1. Take the postback URL from UCLIQ for the required advertiser account or offer.

  2. Replace the postback domain and security key in the template.

  3. Select the correct postback template depending on the event type: install, revenue event, custom event, or fraud install.

  4. Add the postback URL in Singular.

  5. Make sure the UCLIQ click_id is passed to Singular during the click flow.

  6. Make sure Singular returns this value to UCLIQ as {cl}.

  7. Generate a test click.

  8. Trigger a test event in Singular.

  9. Check whether the conversion appears in UCLIQ under Analytics → Conversions.

10. Client Checklist

Before going live, check that:

  • The postback domain and security key are taken from the correct UCLIQ account.

  • The URL includes the required click_id={cl} parameter.

  • Revenue events include sum={CONVERTED_REVENUE} and currency={CURRENCY}.

  • Each event passes a unique tid={RAND}.

  • Goal values match the offer or goal setup in UCLIQ.

  • Android and iOS postbacks are configured separately if platform separation is needed.

  • Test conversions are successfully received in UCLIQ.