Organizations, accounts and properties
Everything you create in AdPix sits under one of three levels. The organization is the outer boundary, the account groups things inside it, and the property is what you actually measure and report on.
Three levels, top to bottom#
Organization → account → property → data stream.
The order never changes, and everything has exactly one parent.
- The organization is the outer boundary. Users and org-wide settings attach to it, and data never crosses it.
- An account groups things inside the organization — typically a brand, a business unit, or a client if you are an agency.
- A property is a website or app you measure. Every report you open reads exactly one property.
- A data stream is how data enters that property. The Measurement ID belongs to the stream, not to the property and not to the account.
You see this same tree in the console under Admin → Account details & hierarchy: your organizations, the accounts under each, and the properties under each account with their primary domain.
What belongs at each level#
| Level | What lives under it | Who can create it |
|---|---|---|
| Organization | Accounts, organization members | Not created by hand; it appears through signup or a platform administrator |
| Account | Properties, Trash, account access | Org admin or Org owner |
| Property | Data streams, events, key events, custom definitions, property access | Account admin of that account, or Org admin / Org owner |
| Data stream | The Measurement ID and the tag snippet | Editor or above on that property |
Roles are held at a level and cascade downwards: a role on the organization carries the same authority over every account and property beneath it. The full ladder is in roles and data restrictions.
The plan — Free or Premium — belongs to the property, not to the organization and not to you. With several properties, a feature can be open on one and locked on another. AdPix sets the plan, not the people in your business.
The property is the unit of reporting#
This is the fact that shapes your structure more than any other: no report adds two properties together. The picker at the top of the page activates one property, and every number on screen belongs to it alone.
Three settings that matter belong to the property, not the account:
| Setting | What it drives | Default | Editable later? |
|---|---|---|---|
| Time zone | The day boundary and every time bucket in reports | UTC |
Yes |
| Attribution window | How far back a touch can still earn credit for a conversion | 365 days | Yes |
| Currency | The unit of revenue and cost across reports | USD |
No — chosen when the property is created |
Admin → Property details edits the property name, the attribution window, the time zone and the excluded CIDRs. Currency is not on that form; it is chosen when the property is created.
The console has no way to move a property from one account to another. If your structure will hold several brands or several clients, build it before you install the tag — doing it later means a new property and starting data collection over.
Create an account and a property#
A brand-new property has no data stream yet, and no Measurement ID until you create one. Continue in install the measurement tag.
If you have no property yet#
If you belong to an organization but have nothing to report on, the console shows the welcome screen instead of reports. Two cases:
- You are allowed to create one — you get a Create your first property button and finish right there.
- You are not — the message tells you to ask an account administrator to create a property or grant you access. Refresh the page once they have.
Switching between properties#
The picker at the top of the page (Search accounts & properties) lists everything you have access to, with Favorites, Recents, Accounts and Properties tabs. Your choice is remembered in that browser, so you land on the same property next time.
Deleting and restoring#
Deleting a property or an account is a soft delete: the row disappears but nothing is destroyed. Both are listed under Admin → Trash and come back with Restore. Deleting and restoring require Account admin or above. Change history and the details of Trash are covered in change history and trash.
Where these ids show up again#
If you work with the API or raw exports, the same structure comes back under different names:
| In the console | In data and the API |
|---|---|
| Organization | tenant_id |
| Property | site_id (the site parameter on report queries) |
Every report query is bound to both values — that is what keeps the data boundary between organizations intact.
Frequently asked questions#
What is the difference between an organization and an account?
The organization is the outer boundary — data never crosses it, and users and memberships attach to it. An account is only a grouping inside that organization, usually a brand, a business unit or a client. One organization can hold several accounts; an account always sits under exactly one organization.
Can I see several properties in one report?
No. Every report reads exactly one property, and every query is scoped to that organization and that property. If you need several domains in one report, measure them as separate data streams under one property rather than as separate properties.
Where do I set the time zone, and what does it affect?
Admin → Property details. The time zone belongs to the property, and every date range and every daily, hourly, weekly and monthly bucket in your reports is evaluated in it. Changing it moves the day boundary across every report.
I deleted a property by mistake. Can I get it back?
Yes. Deleting a property is a soft delete: it moves to Trash under account settings and Restore brings it back. Deleting and restoring both require Account admin or above.
Thanks — your feedback helps us improve the docs.