Settings and administration

You can access project and user settings by clicking on the cog wheel button in the top right corner.

In user settings, you can set your localization (to change the timezone, number and date formats), change your personal details, password, or enable Two-step verification.

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

You can also switch between projects by clicking on the name of your current project.

Users, projects and accounts explained

Users in Exponea are linked to specific people. Each user can have access to multiple projects, even across different accounts. Inviting a new user is free of charge and can be done in the access management part in project settings.

Projects in Exponea are used to differentiate between businesses. Each project has its own project token (ID) that is used when setting event tracking on the website or in mobile apps. Projects are independent of one another, each one has different customers and events, own independent analyses, campaigns, etc. An example would be a company having multiple projects for different countries under the same account. Each project has separate access management.

Accounts are a group of projects for a single client. They share billing, limits for the number of events and other limits. It is possible to set roles in accounts to grant access automatically to all projects under the account.

User settings and timezone

In User Settings, under the "Basic settings" tab, you can edit your personal details, including your name and phone number and also set your timezone. Navigate the left menu to change your password or set up 2-step verification in the "Security" tab.

Project settings

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 invite new users to your project and decide, whether to give the user admin access. They will have to accept your invitation. Until they do so, they will appear in the pending invitations. Do not worry if you accidentally invite someone as an administrator. Even if they should not have total access, you can still make changes to this while the invitation is still pending. Furthermore, you can also further refine their access after they have already accepted the invitation.

Account vs project access

Notice whether you are working in the "Account" or "Project" section of settings as this defines whether you are giving access to the project, or to the whole account. The difference is explained at the beginning of this article.

By scrolling down the Project Team page to the section Teammates you will be able to set the roles of all users with access.

The table below describes the four options for user roles.



The Admin role allows the user to have full access to your project. Admin users will be able to read and write analyses; read, write and execute campaigns; see personal data of customers, export data from the app and finally, they will be able to use the dev tools.


The User role limits the access of a user to read and write analyses; read, write and execute campaigns and export the data. They will not be able to see personal data or use the dev tools.

Use account

By choosing the Use account role, the user will inherit his role from the settings in the Exponea account which contains this project. This allows you to set permission only once per multiple projects.


By choosing the Custom role, you will be able to allow and restrict the user to have only the access that you deem necessary.

The settings are further explained in the following table.



read - open existing analyses
write - create, update and save analyses


read - open existing campaigns
write - create, update and save campaigns
execute - run existing campaigns


Ability to download customer data and analyses reports

Personal data

Grant access to view all PII information in customer properties or events. If this is not enabled, the user will only see *** instead of the real data

Dev. tools

Grant access to catalogs, integrations and campaign access


Overrides all permisions and grant access to everything in a project


Grant access to beta features. These are tagged in Exponea by the beta flag

Project safety and account settings

You are able to decrease the risk of major mistakes and security breaches by carefully restricting the access of your users to perform only the tasks that they really need.

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 behavior 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.

Consents / Campaign Groups

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

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.

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:


Push notifications

You can set up mobile and/or browser push notification IDs and keys here.

Read more about our web push notifications and mobile push notifications.

Support team access

You can easily grant our support team admin access to your project.
Our support team members usually need to access your project in order to provide sufficient help.

Only people with account admin rights can grant access to our support team

When the access is granted, you can see:

  • the person who granted the access
  • date when the access was granted

You can grant an unlimited access or for a certain time period only.

Updated 2 months ago

Settings and administration

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.