Skip to main content

​
Artifacts

アーティファクト は広告掲載面に隣接するコンテンツの単位です。ブランドセーフティ/適合性の評価とは「このアーティファクトは自社広告に適切か？」を問うことです。

​
アーティファクトとは

アーティファクトは広告表示コンテキストを表します:
  • A news article on a website
  • A podcast segment between ad breaks
  • A video chapter in a YouTube video
  • A social media post in a feed
  • A scene in a CTV show
  • An AI-generated image in a chat conversation
アーティファクトは property_id + artifact_id で識別します。property がコンテンツの所在地を、artifact_id がそのコンテンツ固有の識別子を表します。artifact_id の形式は柔軟で、URL パスやプラットフォーム固有 ID、内部で一貫して使う任意の ID で構いません。

​
構造

Schema: artifact.json 
{
  "property_id": {"type": "domain", "value": "reddit.com"},
  "artifact_id": "r_fitness_post_abc123",
  "assets": [
    {"type": "text", "role": "title", "content": "Best protein sources for muscle building", "language": "en"},
    {"type": "text", "role": "paragraph", "content": "Looking for recommendations on high-quality protein sources...", "language": "en"},
    {"type": "image", "url": "https://cdn.reddit.com/fitness-image.jpg", "alt_text": "Person lifting weights"}
  ]
}

​
必須フィールド

FieldDescription
property_idこのアーティファクトの所在。標準の識別子型（domain, app_id, apple_podcast_id など）を使用
artifact_idプロパティ内で一意の識別子。形式はプロパティ所有者が定義
assetsドキュメント順のコンテンツ（テキスト、画像、動画、音声など）

​
任意フィールド

FieldDescription
variant_id特定のバリアント（A/B テスト、翻訳、時間差バージョン）を識別
format_idフォーマットレジストリ参照（クリエイティブの format と同様）
urlアーティファクトの Web URL がある場合
metadataアーティファクト単位のメタデータ（OGP、JSON-LD、著者情報など）
published_time公開日時
last_update_time最終更新日時

​
バリアント

同一アーティファクトに複数バリアントが存在する場合があります:
  • Translations - English version vs Spanish version
  • A/B tests - Different headlines being tested
  • Temporal versions - Content that changed on Wednesday
variant_id で区別します: 
// English version
{
  "property_id": {"type": "domain", "value": "nytimes.com"},
  "artifact_id": "article_12345",
  "variant_id": "en",
  "assets": [
    {"type": "text", "role": "title", "content": "Breaking News Story", "language": "en"}
  ]
}

// Spanish translation
{
  "property_id": {"type": "domain", "value": "nytimes.com"},
  "artifact_id": "article_12345",
  "variant_id": "es",
  "assets": [
    {"type": "text", "role": "title", "content": "Noticia de última hora", "language": "es"}
  ]
}

// A/B test variant
{
  "property_id": {"type": "domain", "value": "nytimes.com"},
  "artifact_id": "article_12345",
  "variant_id": "headline_test_b",
  "assets": [
    {"type": "text", "role": "title", "content": "Alternative Headline Being Tested", "language": "en"}
  ]
}
artifact_id と variant_id の組み合わせはプロパティ内で一意としてください。どのバリアントが配信されたかをレポートと突き合わせられます。

​
アセットタイプ

アセットはアーティファクト内の実コンテンツです。タイトル、本文、画像、動画などすべてアセットとして表現します。

​
Text

{"type": "text", "role": "title", "content": "Article Title", "language": "en"}
{"type": "text", "role": "paragraph", "content": "The article body text...", "language": "en"}
{"type": "text", "role": "description", "content": "A summary of the article", "language": "en"}
{"type": "text", "role": "heading", "content": "Section Header", "heading_level": 2}
{"type": "text", "role": "quote", "content": "A quoted statement"}
Roles: title, description, paragraph, heading, caption, quote, list_item Each text asset can have its own language tag for mixed-language content.

​
画像 (Image)

{
  "type": "image",
  "url": "https://cdn.example.com/photo.jpg",
  "alt_text": "Description of the image"
}

​
動画 (Video)

{
  "type": "video",
  "url": "https://cdn.example.com/video.mp4",
  "transcript": "Full transcript of the video content...",
  "duration_ms": 180000
}

​
音声 (Audio)

{
  "type": "audio",
  "url": "https://cdn.example.com/podcast.mp3",
  "transcript": "Today we're discussing...",
  "duration_ms": 3600000
}

​
メタデータ

アーティファクト全体を表すメタデータです。個別アセットではありません: 
{
  "metadata": {
    "author": "Jane Smith",
    "canonical": "https://example.com/article/12345",
    "open_graph": {
      "og:type": "article",
      "og:site_name": "Example News"
    },
    "json_ld": [
      {
        "@type": "NewsArticle",
        "datePublished": "2025-01-15"
      }
    ]
  }
}
これはコンテンツ自体ではなくアーティファクトコンテナに関する情報のため、アセットとは分離しています。

​
セキュアなアセットアクセス

AI 生成画像、プライベート会話、有料コンテンツなど公開されないアセットが多数あります。アーティファクトスキーマは認証付きアクセスをサポートします。

​
事前設定（推奨）

継続的な提携では、リクエストごとではなくオンボーディング時にアクセス設定を行います:
  1. Service account sharing - Grant the verification agent access to your cloud storage
  2. OAuth client credentials - Set up machine-to-machine authentication
  3. API key exchange - Share long-lived API keys during setup
This happens during the activation phase when the seller first receives content standards from a buyer.

​
アセット単位の認証

事前設定ができない場合は、アセットごとに認証情報を含めます: 
{
  "type": "image",
  "url": "https://cdn.openai.com/secured/img_abc123.png",
  "access": {
    "method": "bearer_token",
    "token": "eyJhbGciOiJIUzI1NiIs..."
  }
}
Note on token size: For artifacts with many assets, per-asset tokens can significantly increase payload size. Consider:
  1. Pre-configured access - Set up service account access once during onboarding
  2. Shared token reference - Define tokens at the artifact level and reference by ID
  3. Signed URLs - Use pre-signed URLs where the URL itself is the credential
The url field is the access URL - it may differ from the artifact’s canonical/published URL. For example, a published article at https://news.example.com/article/123 might have assets served from https://cdn.example.com/secured/....

​
Access Methods

MethodUse Case
bearer_tokenOAuth2 bearer token in Authorization header
service_accountGCP/AWS service account credentials
signed_urlPre-signed URL with embedded credentials (URL itself is the credential)

​
Service Account Setup

For GCP: 
{
  "access": {
    "method": "service_account",
    "provider": "gcp",
    "credentials": {
      "type": "service_account",
      "project_id": "my-project",
      "private_key_id": "...",
      "private_key": "-----BEGIN PRIVATE KEY-----\n...",
      "client_email": "[email protected]"
    }
  }
}
For AWS: 
{
  "access": {
    "method": "service_account",
    "provider": "aws",
    "credentials": {
      "access_key_id": "AKIAIOSFODNN7EXAMPLE",
      "secret_access_key": "...",
      "region": "us-east-1"
    }
  }
}

​
Pre-Signed URLs

For one-off access without sharing credentials: 
{
  "type": "video",
  "url": "https://storage.googleapis.com/bucket/video.mp4?X-Goog-Algorithm=GOOG4-RSA-SHA256&X-Goog-Credential=...&X-Goog-Signature=...",
  "access": {
    "method": "signed_url"
  }
}
The URL itself contains the credentials - no additional authentication needed.

​
Property Identifier Types

The property_id uses standard identifier types from the AdCP property schema:
TypeExampleUse Case
domainreddit.comWebsites
app_idcom.spotify.musicMobile apps
apple_podcast_id1234567890Apple Podcasts
spotify_show_id4rOoJ6Egrf8K2IrywzwOMkSpotify podcasts
youtube_channel_idUCddiUEpeqJcYeBxX1IVBKvQYouTube channels
rss_urlhttps://feeds.example.com/podcast.xmlRSS feeds

​
Artifact ID Schemes

The property owner defines their artifact_id scheme. Examples:
Property TypeArtifact ID PatternExample
News websitearticle_{id}article_12345
Redditr_{subreddit}_{post_id}r_fitness_abc123
Podcastepisode_{num}_segment_{num}episode_42_segment_2
CTVshow_{id}_s{season}e{episode}_scene_{num}show_abc_s3e5_scene_12
Social feedpost_{id}post_xyz789
The verification agent doesn’t need to understand the scheme - it’s opaque. The property owner uses it to correlate artifacts with their content.