Organizations
Check that your B2B accounts are grouped correctly by organization_id, name them, and find the hardest session across an account's members.
Organizations groups the end users of the selected environment by their
organization_id attribute. There is no organization object to create: an account appears
once one of its members identifies with that attribute set, or arrives with it in an Import
(Bring Your Own Data).
Setting it up
Send the id, and a name so the list shows more than the id:
arcy.identify("user_123", {
organization_id: "org_acme",
organization_name: "Acme Inc",
})Every attribute prefixed organization_ or plan_ rolls up to the account, taking the value
from the most recently seen member that sent it. Declare them first on
Attributes.
What it changes
The list. One row per account: Organization (the name with the id under it, or the id alone), Members, Last seen across all members, Domain(s) and Members accepted, the members whose latest consent answer is a grant over all members. Search matches id and name. Sort by organization, members or last seen. Search, sort and paging run on the server. A page holds 25 rows until you pick another size, which the table remembers. Groups ARCY finds among these accounts are read as Insights on Home.
The account page. Click a row. The header shows Organization ID, Members and Sessions. Attributes is the account-level bag rolled up from members. Members lists every user carrying the id, with Email, User ID (No user id yet for a member imported by email alone) and Consent, each linking to the person's page on Users; search it by name, email or id, and sort by Consent to find who has not accepted. What an answer means is on Consent. Sessions is one table across every member, one row per session, with the same columns as a user's own session table plus User. Sort by Struggle and open the top row to reach the hardest session in the account. The columns, the identity outcomes and the Activity page are described on Users. Imported events follows, with a User column: the past events an Import brought for any member, each tagged Imported.
There is no merged timeline of live activity for an account and no export. The unit at account level is the session.
When it goes wrong
An account is missing. No member has identified with organization_id in this
environment yet, or the attribute is not declared. Check Attributes
and the environment in the address.
An account shows only its id. No member has sent organization_name. The page says so
under the header.
Two accounts for one customer. Members are sending two different organization_id
values. Send one.