### Configure Keywords and Negative Phrases (JavaScript)

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Sets up keywords to trigger ads and negative phrases to exclude irrelevant queries. It supports various matching operators for precise targeting and defines limits for keywords. This configuration also includes campaign and ad group level negative phrases, with examples for different industries.

```javascript
// Keyword configuration
{
  "keywords": {
    // Basic keyword - shows for queries containing all words
    "basic": "buy laptop moscow",

    // Keyword with operators
    "operators": {
      "+": "+how to setup laptop",      // Preserve stop words
      "!": "!buy !new laptop",          // Exact word form only
      "[]": "[laptop buy]",             // Exact word order
      "\"\"": "\"buy laptop moscow\""   // Exact phrase match
    },

    // Limits
    "maxLength": 4096,        // Characters including operators
    "maxWordsPerPhrase": 7,
    "maxPhrasesPerGroup": 200
  },

  // Negative phrases - block unwanted queries
  "negativePhrases": {
    // Campaign level - applies to all ad groups
    "campaignLevel": [
      "free",
      "download",
      "how to",
      "DIY"
    ],

    // Group level - specific to one ad group
    "groupLevel": [
      "used",
      "repair",
      "broken"
    ],

    // Common negative phrase lists by industry
    "ecommerce": ["free shipping", "coupon", "discount code", "clearance"],
    "b2b": ["jobs", "career", "salary", "resume", "interview"]
  },

  // Stop words (automatically excluded unless fixed with +)
  "stopWordsExamples": {
    "russian": ["в", "на", "и", "для", "как", "что", "это"],
    "english": ["a", "an", "the", "to", "in", "on", "for", "how"]
  }
}
```

--------------------------------

### Construct URLs with UTM Tags and Yandex Direct Dynamic Parameters

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

This Bash example demonstrates how to construct a complete URL for Yandex Direct campaigns, including standard UTM tags and dynamic Yandex Direct parameters. It shows how to append parameters like campaign ID, ad position, and keyword to track ad performance granularly.

```bash
# Complete URL with UTM tags and dynamic Yandex Direct parameters
https://example.ru/landing\
&utm_source=yandex\
&utm_medium=cpc\
&utm_campaign={campaign_id}\
&utm_content={position_type}.{position}\
&utm_term={keyword}
```

```bash
# All available dynamic parameters
{ad_id}           
{campaign_id}     
{campaign_name}   
{campaign_type}   
{gbid}            
{keyword}         
{phrase_id}       
{device_type}     
{position}        
{position_type}   
{source}          
{source_type}     
{region_id}       
{region_name}     
{match_type}      
{matched_keyword} 
{retargeting_id}  
{yclid}           
```

```bash
# Example full tracking URL
https://shop.ru/product?source={source_type}&block={position_type}&pos={position}&keyword={keyword}&campaign={campaign_id}&device={device_type}&region={region_name}
```

--------------------------------

### Configure Yandex Direct Report Builder

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Defines settings for generating detailed campaign performance reports. Includes date ranges, dimensions (e.g., Campaign, AdGroup, Device), metrics (e.g., Impressions, Clicks, Conversions), and attribution models. Supports filtering and sorting for specific insights.

```javascript
// Report Builder configuration
{
  "reportSettings": {
    "dateRange": {
      "from": "2024-01-01",
      "to": "2024-01-31"
    },

    // Available dimensions (срезы)
    "dimensions": [
      "Campaign",
      "AdGroup",
      "Ad",
      "Keyword",
      "SearchQuery",
      "ImpressionCriterion",   // Shows if autotargeting used
      "TargetingCategory",     // Autotargeting categories
      "Device",
      "Region",
      "Placement",             // Search/YAN/specific site
      "PositionType"           // premium/dynamic_places/other
    ],

    // Key metrics
    "metrics": [
      "Impressions",
      "Clicks",
      "CTR",
      "Cost",
      "AvgCPC",
      "Conversions",
      "ConversionRate",
      "CostPerConversion",
      "Revenue",
      "ROAS"
    ],

    // Attribution models
    "attributionModels": {
      "lastClick": "Last Yandex Direct Click (LYDC)",
      "lastSignificant": "Last Significant Click",
      "automatic": "Automatic (ML-based)",
      "crossDevice": true  // Track across devices
    }
  },

  // Example: Conversion performance report
  "conversionReport": {
    "dimensions": ["Campaign", "ImpressionCriterion"],
    "metrics": ["Impressions", "Clicks", "Conversions", "ConversionRate", "CostPerConversion"],
    "filters": [
      {"field": "Conversions", "operator": ">=", "value": 1}
    ],
    "sortBy": {"field": "CostPerConversion", "order": "ASC"}
  }
}
```

--------------------------------

### Configure Autotargeting Settings (JavaScript)

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Defines autotargeting parameters for Unified Performance Campaigns. It enables automatic ad matching to relevant search queries based on ad text and landing pages. This configuration includes query categories, brand mention settings, and bid strategies.

```javascript
// Autotargeting settings for Unified Performance Campaign
{
  "autotargeting": {
    "enabled": true,
    "placement": "search_and_networks",  // or "search", "networks"

    // Query categories (at least one required for search)
    "queryCategories": {
      "targeted": true,      // Exact match queries (e.g., "buy space tour")
      "narrow": true,        // More specific queries (e.g., "romantic space tour")
      "broad": true,         // General category queries (e.g., "choose tour")
      "alternative": true,   // Substitute product queries (e.g., "underwater tour")
      "related": false       // Related product queries (e.g., "buy spacesuit")
    },

    // Brand mention settings
    "brandMentions": {
      "ownBrand": true,           // Queries with your brand name
      "competitorBrands": false,  // Queries with competitor brands
      "noBrand": true             // Queries without any brand
    },

    // Manual bid for autotargeting (in manual strategy)
    "bidSettings": {
      "type": "auto",  // or "manual"
      "manualBid": null,
      "autoBidFormula": "WeightedAverage(keyword_bids × keyword_clicks)"
    }
  },

  // Example autotargeting queries by category
  "exampleQueries": {
    "targeted": "buy trip to mars from moscow",
    "narrow": "romantic trip to mars for honeymoon",
    "broad": "space tourism options",
    "alternative": "moon tourism instead of mars",
    "related": "what to pack for space travel"
  }
}
```

--------------------------------

### YML Feed for Product Campaigns

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

This section details the YML (Yandex Market Language) feed format used for product campaigns. It allows for automatic generation of product ads by providing product details such as prices, images, and attributes from your catalog.

```APIDOC
## YML Feed for Product Campaigns

### Description
Product feeds in YML (Yandex Market Language) format enable automatic generation of product ads from your catalog. The feed contains product details including prices, images, and attributes for dynamic ad creation.

### Method
GET (or POST for upload, depending on implementation)

### Endpoint
`/feed/yml` (example endpoint)

### Parameters
#### Query Parameters
- **feed_url** (string) - Required - URL to the YML feed file.

#### Request Body
(Not applicable for feed retrieval, but would be used for feed upload)

### Request Example
(No direct request example for retrieval, but the structure of the YML feed is provided below)

### Response
#### Success Response (200)
- **yml_feed** (string) - The content of the YML feed.

#### Response Example
```xml
<?xml version="1.0" encoding="utf-8"?>
<yml_catalog date="2024-01-15 12:00">
  <shop>
    <name>Example Store</name>
    <company>Example LLC</company>
    <url>https://example.ru</url>

    <currencies>
      <currency id="RUB" rate="1"/>
    </currencies>

    <categories>
      <category id="1">Electronics</category>
      <category id="2" parentId="1">Smartphones</category>
    </categories>

    <offers>
      <offer id="SKU12345" available="true">
        <url>https://example.ru/product/smartphone-x</url>
        <price>45990</price>
        <oldprice>52990</oldprice>
        <currencyId>RUB</currencyId>
        <categoryId>2</categoryId>
        <picture>https://example.ru/img/phone-front.jpg</picture>
        <picture>https://example.ru/img/phone-back.jpg</picture>
        <name>Smartphone XPro 256GB Black</name>
        <vendor>TechBrand</vendor>
        <description>Flagship smartphone with 6.7" display</description>
        <param name="Color">Black</param>
        <param name="Storage" unit="GB">256</param>
        <param name="RAM" unit="GB">12</param>
      </offer>

      <offer id="SKU67890" type="vendor.model" available="true">
        <url>https://example.ru/product/laptop-pro</url>
        <price>89990</price>
        <currencyId>RUB</currencyId>
        <categoryId>1</categoryId>
        <picture>https://example.ru/img/laptop.jpg</picture>
        <typePrefix>Laptop</typePrefix>
        <vendor>NoteBrand</vendor>
        <model>Pro 15 i7/16GB/512GB</model>
        <description>Professional laptop for work and creativity</description>
      </offer>
    </offers>

    <collections>
      <collection id="smartphones-2024">
        <url>https://example.ru/catalog/smartphones</url>
        <picture>https://example.ru/img/smartphones-banner.jpg</picture>
        <name>New Smartphones 2024</name>
        <description>Latest smartphone models with best prices</description>
      </collection>
    </collections>
  </shop>
</yml_catalog>
```
```

--------------------------------

### Conversion Center - Offline Conversions Upload

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

This section describes how to upload offline and call conversions using the Conversion Center. Data can be uploaded via CSV files, HTTP/HTTPS links, FTP/SFTP servers, or Google Sheets to enhance campaign optimization.

```APIDOC
## Conversion Center - Offline Conversions Upload

### Description
The Conversion Center allows uploading offline and call conversions from CRM systems to enrich campaign optimization data. Conversions are matched to site visits using email, phone, or ClientID identifiers.

### Method
POST

### Endpoint
`/conversions/upload` (example endpoint)

### Parameters
#### Query Parameters
- **source_type** (string) - Required - Type of upload source (e.g., `csv_url`, `ftp`, `google_sheets`).
- **source_location** (string) - Required - The URL, FTP path, or Google Sheet identifier.

#### Request Body
- **conversion_data** (string) - Required - The content of the CSV file or a reference to the data source.

### Request Example
(Example using a CSV URL)
```json
{
  "source_type": "csv_url",
  "source_location": "https://example.com/conversions.csv"
}
```

### Response
#### Success Response (200)
- **status** (string) - Indicates the upload status (e.g., `processing`, `completed`).
- **message** (string) - A confirmation message.

#### Response Example
```json
{
  "status": "processing",
  "message": "Conversion data upload initiated successfully."
}
```

### CSV File Format Details

- **Separator**: Semicolon (;)
- **Required Columns**: `create_date_time` and at least one identifier (`client_uniq_id`, `client_ids`, `emails`, `phones`).

**Example CSV Content:**
```csv
id;create_date_time;client_uniq_id;client_ids;emails;phones;order_status;revenue
ORD001;2024-01-15 14:30:00;CRM_12345;1234567890123456;customer@email.com;79991234567;PAID;15000.50
ORD002;2024-01-15 16:45:00;CRM_12346;;buyer@mail.ru;79997654321;IN_PROGRESS;8500
ORD003;2024-01-15 18:00:00;CRM_12347;9876543210123456;"mail1@ya.ru,mail2@ya.ru";;PAID;22000
```

**Order Status Values:**
- `PAID` - Order completed and paid (default)
- `IN_PROGRESS` - Order created but not paid
- `CANCELLED` - Order cancelled
- `SPAM` - Spam order
- `<JavaScript_goal_id>` - Custom goal identifier from Metrica

**Upload Sources Supported:**
- HTTP/HTTPS link to CSV file
- FTP/SFTP server
- Google Sheets (share with `import@yandex-direct-conversions.iam.gserviceaccount.com`)

**Attribution Window:** 21 days from last site visit
**Update Window:** 90 days after attribution for status changes
```

--------------------------------

### YML Feed Structure for Product Campaigns

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Defines the XML structure for Yandex Market Language (YML) feeds used to generate product ads. It includes product details like price, images, and attributes. This format is essential for dynamic ad creation from a product catalog.

```xml
<?xml version="1.0" encoding="utf-8"?>
<yml_catalog date="2024-01-15 12:00">
  <shop>
    <name>Example Store</name>
    <company>Example LLC</company>
    <url>https://example.ru</url>

    <currencies>
      <currency id="RUB" rate="1"/>
    </currencies>

    <categories>
      <category id="1">Electronics</category>
      <category id="2" parentId="1">Smartphones</category>
    </categories>

    <offers>
      <!-- Simplified offer type -->
      <offer id="SKU12345" available="true">
        <url>https://example.ru/product/smartphone-x</url>
        <price>45990</price>
        <oldprice>52990</oldprice>
        <currencyId>RUB</currencyId>
        <categoryId>2</categoryId>
        <picture>https://example.ru/img/phone-front.jpg</picture>
        <picture>https://example.ru/img/phone-back.jpg</picture>
        <name>Smartphone XPro 256GB Black</name>
        <vendor>TechBrand</vendor>
        <description>Flagship smartphone with 6.7" display</description>
        <param name="Color">Black</param>
        <param name="Storage" unit="GB">256</param>
        <param name="RAM" unit="GB">12</param>
      </offer>

      <!-- Vendor.model offer type -->
      <offer id="SKU67890" type="vendor.model" available="true">
        <url>https://example.ru/product/laptop-pro</url>
        <price>89990</price>
        <currencyId>RUB</currencyId>
        <categoryId>1</categoryId>
        <picture>https://example.ru/img/laptop.jpg</picture>
        <typePrefix>Laptop</typePrefix>
        <vendor>NoteBrand</vendor>
        <model>Pro 15 i7/16GB/512GB</model>
        <description>Professional laptop for work and creativity</description>
      </offer>
    </offers>

    <!-- Collections for catalog page ads -->
    <collections>
      <collection id="smartphones-2024">
        <url>https://example.ru/catalog/smartphones</url>
        <picture>https://example.ru/img/smartphones-banner.jpg</picture>
        <name>New Smartphones 2024</name>
        <description>Latest smartphone models with best prices</description>
      </collection>
    </collections>
  </shop>
</yml_catalog>
```

--------------------------------

### Configure Yandex Direct Seasonal Demand Adjustment

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Sets up strategies to adjust for seasonal demand fluctuations, such as sales or holidays. It specifies a period, expected conversion rate increase, and availability for different campaign strategies. This helps prevent anomalies during conversion spikes.

```javascript
// Seasonal conversion rate adjustment
{
  "seasonalAdjustment": {
    "name": "New Year Sale 2024",
    "period": {
      "start": "2024-12-28",
      "end": "2024-12-30"
    },
    "expectedCRIncrease": 50,  // Percentage increase expected

    // Example calculation
    "calculation": {
      "normalCR": "10%",       // Regular conversion rate
      "expectedCR": "15%",     // Expected during sale
      "increase": "50%"        // (15-10)/10 * 100 = 50%
    },

    // Availability
    "availableFor": [
      "MaxConversions strategy",
      "MaxClicks strategy (CPC payment)"
    ],
    "notAvailableFor": [
      "CPA payment model campaigns"
    ],

    // How to apply
    "steps": [
      "Select campaigns on 'My Campaigns' page",
      "Click 'Actions' > 'Seasonal conversion rate growth'",
      "Set date range and expected CR increase percentage",
      "Click 'Apply'"
    ]
  }
}
```

--------------------------------

### Define Moderation Rules and Requirements (YAML)

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Outlines the moderation process for Yandex Direct ads, including required checks for ad text, landing pages, and images. It specifies criteria for special categories, age restrictions, and common reasons for ad rejection.

```yaml
# Moderation checklist for ad approval
moderation:
  required_checks:
    - text_compliance:
        - No misleading claims
        - No prohibited characters for emphasis
        - No contact info in ad text (use extensions)
        - Correct grammar and punctuation

    - landing_page:
        - Page must be accessible
        - Content must match ad claims
        - Price on landing must match ad
        - Required legal disclaimers present

    - images:
        - Minimum size: 450x450 pixels
        - Formats: JPG, PNG, WebP, GIF
        - Max file size: 10 MB
        - No excessive text overlay
        - Product must occupy 2/3 of image area

    - special_categories:  # Require documentation
        - Medical services and products
        - Financial services
        - Alcohol (advertising restricted)
        - Real estate
        - Education services

  age_restrictions:
    automatic_labels:
      - "0+": General audience content
      - "6+": Content with mild action
      - "12+": Teen appropriate content
      - "16+": Older teen content
      - "18+": Adult content

  processing_time: "Several hours (depends on campaign size)"

  rejection_reasons:
    common:
      - "Landing page not accessible"
      - "Price mismatch between ad and website"
      - "Missing required disclaimer"
      - "Prohibited product category"

```

--------------------------------

### Offline Conversions Upload Format (CSV)

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

Specifies the CSV format for uploading offline and call conversions to Yandex Direct's Conversion Center. It requires a creation timestamp and at least one identifier (ClientID, email, or phone) for matching. Supports various order statuses and upload methods.

```csv
# CSV file format for conversion upload (semicolon-separated)
# Required columns: create_date_time + at least one identifier

id;create_date_time;client_uniq_id;client_ids;emails;phones;order_status;revenue
ORD001;2024-01-15 14:30:00;CRM_12345;1234567890123456;customer@email.com;79991234567;PAID;15000.50
ORD002;2024-01-15 16:45:00;CRM_12346;;buyer@mail.ru;79997654321;IN_PROGRESS;8500
ORD003;2024-01-15 18:00:00;CRM_12347;9876543210123456;"mail1@ya.ru,mail2@ya.ru";;PAID;22000

# Order status values:
# PAID - Order completed and paid (default)
# IN_PROGRESS - Order created but not paid
# CANCELLED - Order cancelled
# SPAM - Spam order
# <JavaScript_goal_id> - Custom goal identifier from Metrica

# Upload sources supported:
# - HTTP/HTTPS link to CSV file
# - FTP/SFTP server
# - Google Sheets (share with import@yandex-direct-conversions.iam.gserviceaccount.com)

# Attribution window: 21 days from last site visit
# Update window: 90 days after attribution for status changes

```

--------------------------------

### Configure Retargeting Conditions with Yandex Metrica Goals

Source: https://context7.com/vkirill/yandex-direct-docs/llms.txt

This JavaScript object defines a retargeting condition named 'Cart Abandoners - Last 14 Days'. It uses Yandex Metrica goals to identify users who added items to their cart but did not complete a purchase within the last 14 days. It also lists predefined and automatic segments available in Yandex Direct.

```javascript
{
  "retargetingCondition": {
    "name": "Cart Abandoners - Last 14 Days",
    "rules": [
      {
        "type": "ALL",
        "items": [
          {
            "source": "metrika_goal",
            "goalId": 12345678, 
            "period": 14, 
            "includeLookAlike": false
          }
        ]
      },
      {
        "type": "NONE",
        "items": [
          {
            "source": "metrika_goal",
            "goalId": 87654321, 
            "period": 14
          }
        ]
      }
    ]
  },

  "predefinedSegments": {
    "visitors": "All site visitors (last 540 days)",
    "similarToVisitors": "Look-alike audience based on visitor behavior",
    "goalAchievers": "Users who completed campaign goals",
    "cartAbandoners": "Added to cart but didn't purchase",
    "viewedNotBought": "Viewed products without purchase",
    "repeatBuyers": "Multiple purchases completed"
  },

  "autoSegments": [
    "newVisitors", 
    "returningVisitors", 
    "searchTraffic", 
    "adTraffic", 
    "bounceVisitors", 
    "mobileUsers", 
    "desktopUsers"
  ]
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.