Click Ident Track

Click Ident Track enables the setting of a first party cookie using a user or customer identifier profile lookup with redirect to a site, opening a mobile app, or making a mobile voice call. Click-Ident can also be used to propagate identity across more than one domain as long as user consent is provided.

The Click Ident Track pipeline provides a wide range of identification, tracking, and data inlining options, leveraging incoming query string parameters and profile data. For example, for attribution a distinct anonymous user identifier can be inlined and passed on to the destination page.

The Ident provides access to the full Identity Resolution functionality including real-time profile merge, profile switch, etc. based on specified rules including consent validation.

Request

Name	Description
HTTP-Method	GET
Content-Type	None
Path	`/op/[pipeline]/click?param=[hashed/encrypted ID]&uri=[URL encoded destination]`

HTTPOnly Cookie

The API sets a umdid cookie, which is used as lookup identifier.

CODE

umdid=OTBlNjgxZDAtZTEzZi00NTYwLTllYzEtY2Y5NzJlMTlkZjcyfDE1ZDI2NTY4LWVmMzgtNGRiMy05Y2NkLTJmY2YzODI1ODE5Mnwy; Max-Age=31536000; Expires=Thu, 19 Feb 2026 12:18:26 GMT; SameSite=None; Path=/; Domain={your wibsite domain}; Secure; HTTPOnly

The umdid cookie value is a base 64 encoded string consisting of the following values delimitered by pipe:

umdid|umid|type

Name

Type

Description

umdid

UUID

The Unified Marketing Device Identifier, specific to a device.

umid

UUID

The Unified Marketing Identifier, specific to a profile.

type

Digit

A number between 0 and 2 describing the current profile identified method.

0 = anonymous visistor profile
1 = login identified customer profile
2 = network identified customer profile

Sample:

CODE

OTBlNjgxZDAtZTEzZi00NTYwLTllYzEtY2Y5NzJlMTlkZjcyfDE1ZDI2NTY4LWVmMzgtNGRiMy05Y2NkLTJmY2YzODI1ODE5Mnwy

Decoded:

CODE

90e681d0-e13f-4560-9ec1-cf972e19df72|15d26568-ef38-4db3-9ccd-2fcf38258192|2

Parameters

Name	Required	Description
`uri`	Yes	The uri value is the destination, which can be a URL of a landing page, location for an app to be opened, or a phone number to be called. The whole value string needs to be URL encoded. Examples: `uri=tel%3A%2B443432221234` `uri=https%3A%2F%2Fwww.teavaro.com%2F` `uri=fb%3A%2F%2F`
`e10`	No	Customer identifier, for example account ID. This ID is used for IDR operation and by default not passed on to the landing page.
`e11`	No	Hashed email using sha256. This ID is used for IDR operation and by default not passed on to the landing page.
`dynamic-param`	No	This parameter enables you to specify the query string parameter name the UMID gets passed on to the landing page.
Any other parameter	No	Other query string parameters can be added, for example for identification, tracking, attribution, or to pass targeting information to the landing page.

Query String Parameter Inlining / Exclusions

Any incoming query string parameter can be excluded / removed before redirecting to the landing page.

Query string parameters can be configured as part of the pipeline configuration to be inlined / added. This could include targeting information, user identifiers, or user-level anonymous attribution data.

HTTP Status Codes

Code	Name	Description
307	Temporary Redirect	Successful request returning a redirect.
400	Bad Request	The request does not conform to the specification.
500	Internal Server Error	An error occurred on the server side. For example the DB access timed out.

Samples

Click to Call

HTML

<a href="https://funnelconnect.brand-demo.com/op/click?dynamic-param=var1&e11=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=tel%3A%2B447782324970">Call: +447782324970</a>

Click to Web Page

HTML

<a href="https://funnelconnect.brand-demo.com/op/click?dynamic-param=var1&e11=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=https%3A%2F%2Fwww.teavaro.com%2F">Go to www.teavaro.com</a>

Click to App

HTML

<a href="https://funnelconnect.brand-demo.com/op/click?dynamic-param=var1&e11=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=fb%3A%2F%2F">Open your FB App</a>

Click Ident URL Builder

The key part is the URL encoding of the uri value. If you have a simple redirect to landing page, the landing page URL including https:// needs to be URL encoded once. If you would like to run more than one redirect to propagate cookie identity to different domains, you will need to create a full Click Ident URL including URL encoded landing page, which you then URL encode and place as value into the uri query string parameter. We would not recommend more than two Click Ident redirects as that impacts the latency getting to the landing page.

For example:

CODE

https://funnelconnect.publisher-demo.media/op/click?dynamic-param=var1&e11=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=https%3A%2F%2Ffunnelconnect.brand-demo.com%2Fop%2Fclick%3Fdynamic-param%3Dvar1%26e11%3Db8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4%26uri%3Dhttps%253A%252F%252Fwww.teavaro.com%252F

Consisting of:

https://funnelconnect.publisher-demo.media/op/click?dynamic-param=var1&e11=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=..., which sets cookie under publisher-demo.media.
The following being URL decoded by the service before redirecting to Click Ident service again on different domain: https%3A%2F%2Ffunnelconnect.brand-demo.com%2Fop%2Fclick%3Fdynamic-param%3Dvar1%26e11%3Db8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4%26uri%3Dhttps%253A%252F%252Fwww.teavaro.com%252F, which sets cookie under brand-demo.com.
The following being twice URL decoded by the service before redirecting to landing page: https%253A%252F%252Fwww.teavaro.com%252F

https://tv-public-file.s3.eu-central-1.amazonaws.com/click-ident-url-generator.html