Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.corrily.com/llms.txt

Use this file to discover all available pages before exploring further.

One of the first things you need to do before using Corrily is to decide on a long-term system for identifying users. Without stable user identifiers (IDs), Corrily will not be able to learn from the results of the price experimentation. In other words, Corrily needs user IDs so that it can associate the following events together:
  • The price that Corrily generated for this user (and you subsequently displayed to the user)
  • Whether or not the user subscribed to your service, purchased an item, cancelled or renewed their subscription and so on

​
Types of IDs

​
Custom IDs

If your system uses any kind of stable, long-term ID system, such as UUIDs, you can provide that ID to Corrily. See Segment’s description of User ID for more general discussion of this concept.

​
IP addresses

You can use IPv4 or IPv6 addresses to represent users. If you call Corrily’s API endpoints directly from a client device, Corrily can derive the user’s IP from the API request.