Click Ident
Click-Ident 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.
Request
Name | Description |
HTTP-Method | GET |
Content-Type | None |
Path |
|
HTTPOnly Cookie
The API sets a umdid
cookie, which is used as lookup identifier.
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 |
---|---|---|
| UUID | The Unified Marketing Device Identifier, specific to a device. |
| UUID | The Unified Marketing Identifier, specific to a profile. |
| Digit | A number between 0 and 2 describing the current profile identified method. 0 = anonymous visistor profile |
Sample:
OTBlNjgxZDAtZTEzZi00NTYwLTllYzEtY2Y5NzJlMTlkZjcyfDE1ZDI2NTY4LWVmMzgtNGRiMy05Y2NkLTJmY2YzODI1ODE5Mnwy
Decoded:
90e681d0-e13f-4560-9ec1-cf972e19df72|15d26568-ef38-4db3-9ccd-2fcf38258192|2
Parameters
Name | Required | Description |
---|---|---|
| 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:
|
| Yes | Can be any query string parameter name for the required customer identifier, which should be a hashed or encrypted string. |
[Any other parameter] | No | Other required query string parameters can be added. These query string parameters can be included in the destination uri for example to personalise the destination experience. |
Customer identifier query string parameter names can be freely defined in the pipeline.
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. |
404 | Not Found | Incorrect request method or path or pipeline does not exist. |
413 | Payload Too Large | The request headers are larger than the configured maximum on the server. |
500 | Internal Server Error | An error occurred on the server side. For example the DB access timed out. |
Samples
Click to Call
<a href="https://funnelconnect.brand-demo.com/op/brand-demo-click-ident/click?hemail=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=tel%3A%2B447782324970">Call: +447782324970</a>
Click to Web Page
<a href="https://funnelconnect.brand-demo.com/op/brand-demo-click-ident/click?hemail=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=https%3A%2F%2Fwww.teavaro.com%2F">Go to www.teavaro.com</a>
Click to App
<a href="https://funnelconnect.brand-demo.com/op/brand-demo-click-ident/click?hemail=b8788a436ab91569a45fbccd1efe36e74ec940ce210e7f1edb88a09555d4b9e4&uri=fb%3A%2F%2F">Open your FB App</a>
Sample Click Ident URL Builder
https://tv-public-file.s3.eu-central-1.amazonaws.com/click-ident-url-generator.html