# Endpoint: `http(s)://www.woopra.com/track/identify` # Identify requests Identify requests can be used to ID a visitor and/or add properties to that visitor. The endpoint is: `http(s)://www.woopra.com/track/identify` and the parameters are the same as a regular tracking request (event data will be ignored) #### GET Request Parameters

Parameter	Required	Type	Example	Description
`project`	*Required*	<string>	"my-project.com"	The name of your project in Woopra.
`cookie`	* \Optional\\* (See Description)	<string>	"kDei34gy3h25F"	The Cookie should be thought of as a device id. It can also be used for anonymous ids. Required if no `cv_{Visitor Identifier}`. See [The Cookie](doc:profile-id-system)
`cv_{Visitor Identifier}`	* Optional\* (Required to identify a user)	<string>	`cv_email`: "[tigi@woopra.com](mailto:tigi@woopra.com)"	An identifier or multiple identifiers to associate with this visitor. Required if no `cookie`. See [Visitor Properties](doc:visitor-properties) and [Woopra Profile Id](doc:profile-id-system)
`cv_{Visitor Property}`	Required	Various (See Description)	`cv_first_name`: "Tigi"	Properties to set on the visitor's profile. These can be strings, numbers, dates, etc. See [Visitor Properties](doc:visitor-properties)

## Example ```curl curl http://www.woopra.com/track/identify\ ?host=mywebsite.com\ &cookie=AH47DHS5SF182DIQZJD\ &cv_email=tigi@brembo.com\ &cv_name=Tigi\ &cv_age=31 ```