Skip to main content
An example of this are your “How do you find this Feature?” Microsurveys. You may want only want to show one per week to limit fatigue. Your Limit Group would have rate_limit_size=1 and rate_limit_kind=7d then include all of the Microsurveys.
Rate Limit Groups can purposefully overlap and work together to form a cohesive Rate Limiting strategy, to learn more or to run your strategy by the Team, feel free to Contact us.

At certain moments an experience can be exempt from a Rate Limit Group policy. These cases are all considered to be manually delivered:
With the Chameleon API for Rate Limit Groups, you can:
  • Retrieve a list of Rate Limit Groups.
  • List all the related data that are connected to this Limit Group; Tours, Microsurveys and/or Tags

Schema

Kinds of Rate Limit Groups (kind property)
A Rate Limit Group creates a dynamic or static group of Experiences over which to apply the rate_limit_size number of Experiences in rate_limit_kind interval of time.

Listing Limit Groups

Retrieve a list of all Limit Groups. An account typically has 1-5 Limit Groups so this response should be relatively small.

HTTP Request

GET

HTTP Response


Showing a Limit Group

Retrieve a single Limit Group.

HTTP Request

GET

HTTP Response


A Limit Group is attached to many Chameleon Experiences (Tours/Microsurveys). This endpoint allows you to get a complete picture of all Experiences currently attached to the Limit Group.

HTTP Request

GET

HTTP Response (Example with kind=campaigns)

Note: this example Limit Group is based on kind=campaigns which means the Chameleon administrator explicitly picked these Experiences from a dropdown menu in the application. Keys returned: limit_group, tours and surveys

HTTP Response (Example kind=tags)

Note: this example Limit Group is based on kind=tags which means the Chameleon administrator explicitly picked a set of Tags from a dropdown menu in the application. Keys returned: limit_group, tags, tours and surveys