Organizations, accounts and websites
Everything in AdPix sits under three levels — organization, account, website — and a fourth beneath them: the data stream. Where a setting lives, and who can change it, follows from that shape.
Four levels, not three#
The AdPix structure is always the same:
organization → account → website → data stream.
- Organization is the top level and the data boundary. Yours is created when your account is opened, and you own it. Every event carries an organization id and a website id, and every report query is bounded by both.
- Account is an organizing layer: it groups websites. If you run an agency or several brands, the account is where you draw the line between teams.
- Website is the reporting unit. Everything you see in a report belongs to one website, and the picker at the top of the console switches between them.
- Data stream is one input into that website — usually one domain. The tag ID belongs to the data stream, not to the website.
What is defined at each level#
| Level | What lives here | Minimum role to change it |
|---|---|---|
| Organization | Organization-level members, organization settings, permanent erasure of one person's data | Org owner |
| Account | Account name, account members, creating websites, deleting and restoring websites, Trash | Account admin |
| Website | Name, primary domain, time zone, attribution window, excluded CIDRs, events and key events, custom definitions, cookie consent | Editor (website members: website admin) |
| Data stream | Tag ID, collection mode, domain and cross-domains | Editor |
A website's plan — Free or Premium — is not in that list, because AdPix sets it, not the people in your business. Its effect is covered in roles and data restrictions.
Access flows down the chain#
Membership can be granted at any of the three levels. A person's effective authority on a website is the highest of what reaches them by three routes: a membership on the website itself, on the account above it, and on the organization.
The practical consequence: an organization-level membership means access to every website you have today and every website you create tomorrow. If someone should see exactly one website, grant the membership on that website.
In the access panel, rows that arrive from a higher level are marked inherited and are managed where they were granted — not here.
No report ever reads past the organization and website it was asked for. That bound is written into the database query itself, not into the interface — so even a hand-made API call cannot return another website's data.
What cannot be undone#
Most things here are reversible: names can be changed, deleted websites and accounts go to Trash and come back, roles can be taken away. These three are the exceptions:
- A website's place is fixed. It stays in the account it was created in; there is no way to move it to another account or organization.
- Deleting a data stream is final. The data stream and its keys are removed and the tag ID does not come back. Past events stay where they are, but the tag installed on your site no longer reaches this website with that ID.
- Erasing one person's data has no undo. The path is described in data retention and deletion.
Two website settings that also change the past#
Time zone does not only affect new data. Every window bound and every day, hour, week and month bucket in the reports is evaluated in the website's time zone, so changing it re-buckets the whole history. Yesterday's numbers will move.
Excluded CIDRs work the other way round: matching requests are dropped before anything is written, so they only clean going forward. Internal traffic already recorded does not leave the reports when you add a CIDR.
Where you see this in the console#
If you have not created a website yet, start at create an account and a website; if the website exists but no data arrives, go to install the tag.
Frequently asked questions#
What is the difference between an organization and an account?
The organization is the top level and the data boundary - every event carries its id and no report ever reads past it. An account is only an organizing layer inside that organization - it groups websites so you can grant access to a group of them at once.
One website for my site and app, or two?
If you want their numbers read together, create one website with two data streams under it. Events do not carry a data stream id, so every data stream of a website rolls up into the same reports. If you want them reported separately, create two websites.
Can I move a website to another account?
No. A website stays in the account it was created in, and there is no path to move it. If the structure is wrong, create a new website and point the tag at it - the old website's history does not come with it.
Does deleting a website delete its data?
No. Deleting a website or an account is a soft delete - it moves to Trash, drops out of the lists, and an account admin can restore it. The recorded events are untouched. Actually removing data is a separate path.
Thanks — your feedback helps us improve the docs.