Project settings

Project settings contain access management and settings for campaigns - languages, policies, consents, and channels. You can also set up SSH tunnels here.



Depending on your role and access rights, you might not see or be able to edit some of the sections visible in the screenshot below.

Project - General


You can change the project supervisor here, who serves as the main point of contact for important notifications and billing information. Project token and project secrets are also shown here. These are used for integration and tracking purposes.

Access management

You can read more about the role and access management in the following article.

API settings

  • Located under "Access management"*

Read more about API settings here


You can set up SSH tunnels here.

Campaigns - General

You can set the default utm_source parameter under "General campaign settings". Read more about UTM parameters.


You can define which languages your project uses to create multilanguage templates used in campaigns. "Name" is a human-readable name displayed in the UI (English). "Value" is the value tracked in the customer attribute language (en).


When you want to send an email campaign to customers in 3 different countries, you can create just one campaign with 3 different versions. In the screenshot below, all customers with an attribute language = en will receive the English version. The same logic applies to any language. Customers who don't have this attribute filled will receive the campaign in the default language, which would be Polish in this case.


Privacy management - Frequency policy and consents

Frequency policy

In this section, you can define frequency policies for email/SMS/webhook/notification campaigns to limit the number of campaigns a customer can receive in a certain time period. To create the frequency policies that can be used in a campaign, go to Settings > Project settings > Privacy management > Frequency policy. You can choose multiple settings for a single policy. To do so, click on edit.



A single policy is identified using a unique ID (used in campaign events, property name campaign_policy), a user-facing name and at least one segment.


Each segment may define a number of rules that define the policy's behaviour for customers matching the segment. Simpler policies will use just a single segment matching all customers, with the same set of rules applying to all customers. Different customers may, however, have different preferences, so you may define multiple segments (using customer filters) with different rules. Thus one segment matching customers with a high email open rate may allow multiple emails per week, while the segment catching the rest of customers with a low open rate will limit the communication to just one email per week. One policy may define up to 12 segments. The last segment must always catch the rest of the customers, i.e. those not matched by any of the previous segments.

Max. messages per customer/period

Max. messages per customer/period defines how many messages can be sent within a relative time frame. It is composed of an integer limit and a duration, for example, 3 messages per 7 days. A limit of 0 per any duration can be used to suppress all communication for a segment. Up to 4 may be defined in one segment, all rules will need to pass in order for a message to be sent. It's also possible for a segment to define no 'max. messages per customer/period' constraints, which means no communication limits will be imposed.


An email campaign or scenario node may then use one of the policies.


Campaign Groups / Consents


Campaign Groups have been replaced with our new Consents management. If your project is still using campaign groups, we recommend switching to consents for easier GDPR compliance.

After enabling consent management, the setting of campaign groups will be no longer available.

You can define categories of emails or sms from which customers can unsubscribe separately. This will also create a customer attribute unsubscribed_from, which is a list attribute.

Each campaign sent has to belong to a campaign group. By default, there is only one campaign group called All Communication. Campaign groups with their names and descriptions will be shown as options to subscribe to/ unsubscribe from on the unsubscribe page ( the link to it can be sent via {{ email.unsubscribe }} ).

Once a customer chooses to unsubscribe from a campaign group, an event subscriptions_changed will be generated, and an attribute unsubscribed_from will be updated. This attribute can also be changed manually when editing the customer or through imports.


You can define your campaign groups if you have not enabled the consent framework yet.

If you are using our consent management, apart from setting the consent and legitimate interest categories, you can also access and edit the consent page here: