Project settings

Project settings is at the bottom of the navigation. Owners and admins can open it. Members, billing and the plan are on the organization: see Organizations and roles.

Project

General

• Project name.
• Timezone: reports start each day at midnight in this time zone.
• Reporting currency: revenue is converted into it at each day's rate.
• Default attribution model: First-touch or Last-touch.

Sessions

• Web inactivity timeout: 15, 30, 60 or 120 minutes.
• Mobile background timeout: 10 seconds, 30 seconds, 2 minutes or 5 minutes.

The SDKs pick up a change the next time they fetch the project's config; they cache it for up to 5 minutes. See Sessions.

Conversions

Add key events as conversions. The first one is the primary conversion; Make primary changes it. See Key events and conversions.

Data quality

• Internal traffic: IP ranges in CIDR form, such as your office network. Events from them are marked as internal and left out of reports. Ingest checks the IP address, then drops it.
• Bot filtering: when on, web events whose user agent is a known bot are marked as bots and left out of reports.

Both are applied when an event arrives, so a change applies to events received after it, not to past ones.

• Raw event retention: how long events are kept, from the plan. See Data retention.

Choose Save changes when you're done.

Danger zone

• Transfer project: move the project to another organization you belong to.
• Delete project: deletes its events, sessions, people and transactions, and its keys stop working. Type the project's name to confirm.

An organization's last project can't be transferred or deleted; delete the organization instead.

Privacy & data

How data is kept

Where the data is stored (EU — Germany), that IP addresses are never stored, and the plan's retention.

Sensitive property blocking

Add property names that Rabolic should remove from every event, such as email or phone. Rabolic already removes names like password, card_number, cvv, iban and ssn. See Consent and privacy.

Data subject requests

Find a person by user id, email or anonymous id with Find person, then:

• Export data: downloads a JSON file of their profile, identities and events;
• Delete person: deletes their profile, identities, events and transactions, including people merged into them.

The table lists every request with its type, the person, when it was made and its status. Requests work even while the organization is read-only.