Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Struttura del subaccount
La struttura dell'URL della tua piattaforma è il fattore principale che determina la struttura dei subaccount e, più specificamente, l'aspetto del campo site_uri.
Di seguito sono riportati i diversi tipi di strutture del sito supportate da AFP:
littlepig (o un ID univoco interno associato all'utente)
Come creare subaccount se gli utenti hanno più proprietà sulla tua piattaforma
I subaccount devono essere mappati agli utenti. Se un singolo utente può possedere più di una proprietà (ad es. un sottodominio, una cartella o pagine del profilo) sulla tua piattaforma, il subaccount mappato a quell'utente deve contenere tutte le proprietà associate a quell'utente.
Il valore di "request_id" in questo scenario
Se la tua piattaforma consente più proprietà per utente, ti consigliamo di utilizzare un identificatore univoco interno per l'utente nel campo request_id. In futuro, il metodo dell'API get account consentirà di ottenere gli account in base al valore di questo campo.
[null,null,[],[[["\u003cp\u003eSub-account structure depends on your platform's URL structure, determining the \u003ccode\u003esite_uri\u003c/code\u003e field's value.\u003c/p\u003e\n"],["\u003cp\u003eAFP supports various site structures like subdomains, subfolders, their combination, and individual URLs, each with specific \u003ccode\u003esite_uri\u003c/code\u003e formats.\u003c/p\u003e\n"],["\u003cp\u003eSub-accounts represent users and should encompass all properties owned by a single user, even if they have multiple websites or profiles.\u003c/p\u003e\n"],["\u003cp\u003eFor platforms with multiple properties per user, utilize an internal unique user identifier for the \u003ccode\u003erequest_id\u003c/code\u003e field, enabling future account retrieval.\u003c/p\u003e\n"],["\u003cp\u003eCurrently, adding multiple \u003ccode\u003esite_uri\u003c/code\u003e instances to a single account requires consultation with your account manager due to API limitations.\u003c/p\u003e\n"]]],["The sub-account structure is determined by the platform's URL structure, defining the `site_uri` field. Supported structures include subdomains, subfolders, a combination of both, and individual URLs. For subdomains, `site_uri` is the subdomain; for subfolders, it's the root path. The `request_id` should be a unique identifier. If users have multiple properties, sub-accounts must include all associated properties, and it's advised to use a unique user ID for `request_id`. The API currently only supports one instance of `site_uri` per account.\n"],null,["Sub-account structure\n---------------------\n\nThe URL structure of your platform is the main driver for how your sub-accounts should be structured, and more specifically, what the `site_uri` field should look like.\n\nSee below the different types of site structures AFP supports:\n\n| Use case | URL structure | Value of `site_uri` field in API | Value of `request_id` field in API |\n|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|\n| Subdomains | Root: `https://littlepig.example.com` \u003cbr /\u003e Content: `https://littlepig.example.com/food.html` | `littlepig.example.com` | `littlepig` (or an internal unique ID associated with the user) |\n| Sub folders | Root: `https://example.com/littlepig` or `https://example.com/sites/littlepig` \u003cbr /\u003e Content: `https://example.com/littlepig/food.html` or `https://example.com/sites/littlepig/food.html` | `example.com/littlepig` or `example.com/sites/littlepig` | `littlepig` (or an internal unique ID associated with the user) |\n| Combination of subdomains and sub folders | Root: `https://sites.example.com/sites/littlepig` \u003cbr /\u003e Content: `https://sites.example.com/sites/littlepig/food.html` | `sites.example.com/sites/littlepig` | `littlepig` (or an internal unique ID associated with the user) |\n| Individual URLs | Root (or creator profile): `https://example.com/user/littlepig` \u003cbr /\u003e Content: `https://example.com/nf8ag4n` | `example.com/user/littlepig` \u003cbr /\u003e **Important:** for this use case, we additionally require the [\"Platform author\" meta tag](/adsense/platforms/direct/meta-tags#platform_author) to be present on all pages. | `littlepig` (or an internal unique ID associated with the user) |\n\nHow to create sub-accounts if your users have multiple properties on your platform\n----------------------------------------------------------------------------------\n\nSub-accounts are intended to be mapped to users. If a single user can own more than one property (i.e. a subdomain or folder, or profile pages) on your platform, the sub-account mapped to that user must contain all of the properties associated with that user.\n\n### The value for \"request_id\" in this scenario\n\nIf your platform allows multiple properties per user, we recommend using an internal unique identifier for the user in the `request_id` field. In the future, the [get account API method](/adsense/platforms/reference/rest/v1alpha/platforms.accounts/get) will allow getting accounts based on the value of this field.\n| **Note:** Currently the Platforms API doesn't have a sites method to add multiple instances of `site_uri` to one account, and the account creation API only supports one instance of `site_uri`. Please speak with your account manager if your platform fits this type of structure."]]
