Koleksiyonlar ile düzeninizi koruyun
İçeriği tercihlerinize göre kaydedin ve kategorilere ayırın.
Alt hesap yapısı
Alt hesaplarınızın nasıl yapılandırılması gerektiğine ve daha da spesifik olarak site_uri alanının nasıl görünmesi gerektiğine karar verirken platformunuzun URL yapısı temel belirleyicidir.
AFP'nin desteklediği farklı site yapısı türlerini aşağıda görebilirsiniz:
Kullanım alanı
URL yapısı
API'deki site_uri alanının değeri
API'deki request_id alanının değeri
Alt alan adları
Kök: https://littlepig.example.com
İçerik: https://littlepig.example.com/food.html
littlepig.example.com
littlepig (veya kullanıcıyla ilişkilendirilmiş dahili benzersiz kimlik)
Alt klasörler
Kök: https://example.com/littlepig veya https://example.com/sites/littlepig
İçerik: https://example.com/littlepig/food.html veya https://example.com/sites/littlepig/food.html
example.com/littlepig veya example.com/sites/littlepig
littlepig (veya kullanıcıyla ilişkilendirilmiş dahili benzersiz kimlik)
littlepig (veya kullanıcıyla ilişkilendirilmiş dahili benzersiz kimlik)
Kullanıcılarınızın platformunuzda birden fazla mülkü varsa alt hesaplar oluşturma
Alt hesapların kullanıcılarla eşlenmesi amaçlanmıştır. Tek bir kullanıcının platformunuzda birden fazla mülke (ör. alt alan adı, klasör veya profil sayfası) sahip olması durumunda, bu kullanıcıyla eşlenen alt hesap, söz konusu kullanıcıyla ilişkili tüm mülkleri içermelidir.
Bu senaryoda "request_id" için değer
Platformunuz kullanıcı başına birden fazla mülke izin veriyorsa request_id alanında kullanıcı için dahili bir benzersiz tanımlayıcı kullanmanızı öneririz. Gelecekte get account API yöntemi, bu alanın değerine göre hesap almanıza olanak tanıyacak.
[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."]]
