Many of our users deal with multiple websites and for multiple clients. A common question is how should we setup Schema App to handle these. First, let’s define the Graph ID and how it’s used.
What is your Account ID?
The Graph ID is your account identifier, it’s used to lookup your account information and what we use to locate your data. The Graph ID is unique and generated based on the Company field during the registration process.
How do we use the Account ID?
The Graph ID is used in the WordPress Plugin or Google Tag Manager to help the lookup your data. There is no restriction on the domains, one Graph ID can be used for multiple domains. If you are one company that has multiple websites, that’s probably just what you want. However, if you have multiple clients, some with multiple websites it’s less than ideal. Mixing client data can clutter the reporting and the editor’s autocomplete lookups.
We recently introduced Schema App SubAccounts which is designed for working with multiple clients. You can use this to separate reporting by client accounts, do exports or transfer data to the client. From the sub-accounts page you can create and then switch to the client account. The page shows when you’ve switched accounts and has a new link to switch to back to your main account. In the image we see one account that is the Current Account ID. For client account management you should add a subaccount for each client. The client sub-account could in turn be used across multiple client domains.
Mark van Berkel is the co-founder and COO of Hunch Manifest and the creator of Schema App. He is an expert in Semantic Technology and Semantic Search Marketing. Mark built Schema App to solve his own challenges in writing and validating schema markup.