Identify Call
Link IPs to users and update user features.
The identify endpoint serves three purposes:
- It can be used to pass user-level features after (or before) a price has already been tied to them using the main price endpoint.
- It can be used to link IPs to user_ids so that prices persist to a user as they see a price -> login in -> check the price again.
- It is used during mobile integrations to inform Corrily about original Apple and Google purchase IDs.
Body Params
An IP you wish to tie the user to. For more information read our anonymous users guide.
Optional field which indicates the country which the user belongs to. If the country given is not part of the experiment for the ip user, the user id given wont be added to the experiment via identify. Please note this country wont be stored against user. This is used only for validating if the experiment characteristics for previous user from the ip can be applied to the user id. The user country will be locked to the country given in subsequent price call.
An object containing arbitrary key-value pairs that represent characteristics of this user which may affect their optimal price. The keys can be any valid JSON key. The values can be strings, integers, or floats.
Pass an original_transaction_id for a user when they purchase an IAP product. (Note that in the backend, this will not overwrite any previously stored transaction IDs for this user).
Pass an purchaseToken for a user when they purchase an in-app product. (Note that in the backend, this will not overwrite any previously stored purchase tokens for this user).
Response
Its an optional field. If the identify call copied experiment attributes from ip to the user, this attribute will be included in the response. Otherwise, it wont be included in the response.