Yandex Direct API reports offer four attribution models: first click, last click, last significant click, and last click from Yandex Direct. The Direct API attribution model defines the rule for distributing conversions in a report: the same lead or sale may be attributed to different advertising campaigns.
To ensure that spend, clicks, impressions, CTR, visits, and conversions reflect one consistent logic, API requests, the report structure, and automated data exports need to be configured together. Advertising statistics should be reconciled with Yandex Metrica, CRM, and BI analytics without mixing incomparable data sources.
- Audit your current Yandex Direct, Metrica, and CRM reports.
- Choose an attribution model that matches the sales cycle and conversion type.
- Configure API requests and the export structure.
- Reconcile campaigns, goals, filters, and metrics.
- Document the calculation logic and the rules for interpreting the report.
If the task requires a paid model—for example, GPT-5.6 Terra—it is cheaper to obtain access through the Clodex partner service rather than directly from the vendor. The price difference is shown below.
| Price type | Official vendor price | Through Clodex |
|---|---|---|
| Input tokens | 2 $ / 1 million tokens | 0,07 $ / 1 million tokens |
| Output tokens | 12 $ / 1 million tokens | 0,56 $ / 1 million tokens |
| Difference | Input tokens — в 28,6 times cheaper; Output tokens — в 21,4 times cheaper | |
Partner price source: Clodex. Price check date: 2026-08-18.
SEO Mind42 does not sell API access or provide tokens: we recommend a third-party service Clodex. This is an affiliate link.
How to configure an attribution model in the Yandex Direct API
The attribution model in the Yandex Direct API applies to a specific report. It is not assigned to the advertising account, does not change the campaign strategy, and does not affect the ad-serving algorithm. The parameter only determines which visit or traffic source receives the conversion in the statistics.
- Define the purpose of the report. What decisions should be made based on the data: reallocating the budget, monitoring channel profitability, evaluating the first touchpoint, analyzing leads, or reconciling paid sales. Describe the target actions: an order, lead, call, payment, repeat purchase, or change of status in the CRM.
- Check the data sources. Yandex Direct advertising campaigns, Yandex Metrica goals, CRM reference data, online store product data, manual spreadsheets, and existing BI reports. Before configuring the API, it is important to rule out situations where one comparison combines clicks from Direct, visits from Metrica, and CRM sales that use different lead deduplication rules.
- Choose an attribution model. First-click attribution is suitable for attracting a new audience. Last-click attribution is used to assess the channel immediately before a lead or purchase. A long sequence of touchpoints requires separate analysis because one model cannot answer all marketing and sales questions.
- Configure the API request and report composition. Define the reporting period, report type, fields for campaigns, ads, spend, impressions, clicks, CTR, and conversions. Then set filtering and grouping, create source breakdowns, and pass the attribution model in the report specification. At this stage, the attribution model for Direct API requests is matched with Yandex Metrica goals and the counter ID.
- Automate the export. Set up data transfer to a spreadsheet, database, CRM, Data Studio, or another BI system. The automated export should preserve a consistent field structure, handle request errors, and update statistics on schedule. Even after launch, reporting still requires monitoring when goals, campaigns, access permissions, or reference data change.
- Reconcile the results. Match spend, visits, sessions, conversions, advertising channels, and traffic sources. Check the period, time zone, filters, conversion window, breakdowns, attribution model, and data composition. Discrepancies do not always indicate an API error: the CRM may deduplicate leads, Metrica may count goals according to its own logic, and sales may enter the system after the click.
- Document the setup. Describe the report, the rules for calculating metrics, and recommendations for the marketer, analyst, and manager—so the report becomes an understandable tool for adjusting advertising decisions rather than a collection of figures from different systems.
Attribution models in Yandex Direct API reports
| Model | What it shows | When it is suitable |
|---|---|---|
| First click, FC | The channel through which the user first encountered the advertising or website. | Evaluating new-audience acquisition and the top of the funnel. |
| Last click, LC | The last interaction before the conversion. | A short path to purchase and prompt performance monitoring. |
| Last significant click, LSC | The last click that the system considers significant in the sequence of touchpoints. | Analyzing the user journey across multiple traffic sources. |
| Last click from Yandex Direct, LYDC | The last advertising touchpoint specifically from Yandex Direct. | Evaluating the contribution of Direct campaigns in a multichannel funnel. |
The FC, LC, LSC, and LYDC codes are used when generating a report in the Yandex Direct API. Before launching regular data loading, check whether the selected model is supported for the required report type in the service's current specification, because the parameter set and reporting capabilities may change.
Illustrative case: an online store received 100 orders during the reporting period. Under the last-click model, more orders were attributed to campaigns that brought the user back before the purchase. Under the first-click model, some of these same orders were attributed to campaigns that first brought the customer to the website. After separating the reports, the company stopped disabling top-of-funnel campaigns solely because they had a low number of last clicks.
Python, spreadsheets, databases, and BI analytics are suitable for automation—the choice depends on the set of sources. Approaches to automating marketing tasks and working with neural networks are also collected in the AI for SEO and analytics.
For which tasks should Direct API attribution and reports be configured?
Online stores and product advertising
An online store needs to distinguish between the campaign that first brought a customer to the website and the campaign that brought the customer back to place an order. A summary report can match the advertising campaign, category, product, traffic source, spend, and revenue from the order system. For a site running on OpenCart, the setup depends on what information is available in the CMS and how orders, statuses, and product identifiers are transmitted.
An attribution model for products does not exist separately from the report. Products, categories, and orders serve as additional analytical dimensions, while the conversion-allocation rule is selected according to the business objective. One report helps evaluate demand acquisition; another shows the campaign preceding order placement.
Lead-generation services with a long sales cycle
A user may submit a lead after several visits, while the sale may appear in the CRM after negotiations. In this setup, it is not enough to compare form conversions with the number of payments. The configuration links Yandex Metrica goals, advertising visits, lead statuses, and deduplication rules so that the marketer can see the path from inquiry to result.
Which figure should be considered primary: a lead or a paid sale? The answer depends on the management task. Leads and calls are useful for monitoring traffic; evaluating the quality of an advertising channel requires CRM statuses, revenue, and reasons for lost sales, if the sales department records them.
B2B and complex sales
In B2B, one deal often includes several touchpoints: search, advertising, a direct visit, a repeat inquiry, and communication with a manager. The report should distinguish the advertising channel involved in the first contact from the source involved before the inquiry. This reduces the risk of disabling a demand-generating campaign simply because it rarely receives the last click.
Cross-channel analytics does not create absolute accuracy by itself. It helps document matching rules, distinguish duplicates from new leads, and show where Direct data ends and CRM data begins.
Marketplaces and sales through multiple channels
Ozon can serve as a source of commercial data for consolidated analytics if the business matches advertising spend with sales through the website, marketplace, and other channels. The Yandex Direct API does not automatically receive marketplace attribution. This scenario requires a separate scheme for combining advertising statistics, product data, and revenue-calculation rules.
Here it is useful to separate the metrics in advance. Direct provides spend, impressions, clicks, CTR, and conversions for available goals. The sales system stores orders, returns, fulfilled purchases, and margin. A BI report combines these datasets only after the keys, periods, and level of detail have been reconciled.
Agencies and multiple advertising accounts
Agencies need batch exports of statistics by client, account, campaign, and period. Consistent data-structure, filtering, and grouping rules make it possible to repeat reporting without manually collecting files. Access permissions should be separated between clients so that the calculation logic remains transparent to the account manager and analyst.
To monitor search visibility and compare advertising traffic with SEO metrics, the Topvisor overview for SEO analytics and rank monitoring is useful. It does not replace the Yandex Direct API, but it helps separate search-promotion tasks from contextual advertising.
If you decide to purchase a paid plan while reading, compare the official price with the partner price before subscribing directly: the difference is usually several times over, and the calculation is provided at the beginning and end of the article.
What to check before launching an automated export
Before launch, you need access permissions for the advertising account, Yandex Metrica counters, and approved CRM sources. Check goal IDs, periods, time zones, filters, report fields, and campaign-matching rules. An error in any of these elements can change the comparison result even when the API request itself is correct.
Advertising statistics by themselves do not always contain personal data. The risk arises when phone numbers, email addresses, lead IDs, contact history, or other information that can identify a person are added to an export or external database. In such cases, anonymized statistics and personal information should preferably be separated at the levels of access, storage, and reporting views.
What makes configuring the Direct API and attribution models more difficult
The workload does not grow linearly: one account with several goals and an export to a spreadsheet takes hours, while several advertising accounts, a CRM, product analytics, and regular loading into a BI system already constitute a full-scale project.
- Number of advertising accounts and campaigns—the more sources there are, the more difficult it is to control the data structure.
- Number of goals and conversion types—each requires a separate check of the accounting logic and attribution model.
- Presence of a CRM—it may be necessary to match leads, sales, statuses, and advertising sources.
- Output format—a spreadsheet, database, and BI dashboard require different amounts of work.
- Quality of the source analytics—incorrect goals, duplicate leads, and inconsistent reference data increase the amount of preliminary audit work.
FAQ
What is an attribution model in simple terms?
It is a rule used to assign a conversion to one of the advertising visits or sources in the user's journey. The selected rule determines which advertising campaign receives the conversion in the report.
Where do I specify the attribution model in the Direct API?
The model is specified when generating a report through the Yandex Direct API. It is passed in the report specification parameters and checked together with the period, goals, filters, and other request settings.
Why do conversions differ in Yandex Direct, Yandex Metrica, and the CRM?
Systems may use different attribution models, time periods, time zones, filters, goal-tracking rules, and sales statuses. Before comparing them, check the calculation methodology and the data included in each report.
Can one attribution model be selected for all reports?
A single rule can be used for regular management reporting. Different views serve different purposes: the first touch evaluates audience acquisition, while the last touch shows the channel before conversion.
Will this work for an OpenCart online store or sales through Ozon?
Yes, if order, product, and sales data are available for integration in an agreed format. The Yandex Direct API provides advertising statistics, while integration with a CMS, CRM, or marketplace is configured using a separate analytics setup.
Set up Direct API reports without mixing incomparable data
Start by checking the data sources, access permissions, goals, and expected output format. Then choose the attribution logic, configure the API request, automated data export, and reconciliation with Yandex Metrica, a CRM, or BI analytics, following the steps above.
- A consistent way to allocate conversions across advertising campaigns.
- Clear reports on advertising spend, visits, clicks, and results.
- Regular statistics uploads without manually combining files.
- Documented calculation rules for marketing teams and managers.
SEO Mind42 develops an educational blog with practical materials on SEO, analytics, and AI tools.
Paid access via API
If the free limits are not enough, you can get API access to models directly from the vendor or through the Clodex partner service. Below is a comparison of official prices and partner pricing. For example, GPT-5.6 Terra costs 28,6 times less through the partner than at the official price. The full list of models is in the table.
| Model | Official: input / output | Through Clodex: input / output |
|---|---|---|
| qwen3.6-flash | Input: 0,25 $ / 1 million tokens Output: 1,5 $ / 1 million tokens | Input: 0,019 $ / 1 million tokens Output: 0,019 $ / 1 million tokens |
| qwen3.6-plus | Input: 0,5 $ / 1 million tokens Output: 3 $ / 1 million tokens | Input: 0,032 $ / 1 million tokens Output: 0,032 $ / 1 million tokens |
| qwen3.7-plus | Input: 0,4 $ / 1 million tokens Output: 1,6 $ / 1 million tokens | Input: 0,045 $ / 1 million tokens Output: 0,045 $ / 1 million tokens |
| codex-auto-review | — | Input: 0,0525 $ / 1 million tokens Output: 0,0525 $ / 1 million tokens |
| gemini-3.7-flash | Input: 0,75 $ / 1 million tokens Output: 3,75 $ / 1 million tokens | Input: 0,06 $ / 1 million tokens Output: 0,24 $ / 1 million tokens |
| gemini-3.7-flash-high | Input: 0,75 $ / 1 million tokens Output: 3,75 $ / 1 million tokens | Input: 0,06 $ / 1 million tokens Output: 0,24 $ / 1 million tokens |
| gemini-3.7-flash-low | Input: 0,75 $ / 1 million tokens Output: 3,75 $ / 1 million tokens | Input: 0,06 $ / 1 million tokens Output: 0,24 $ / 1 million tokens |
| gemini-3.7-flash-medium | Input: 0,75 $ / 1 million tokens Output: 3,75 $ / 1 million tokens | Input: 0,06 $ / 1 million tokens Output: 0,24 $ / 1 million tokens |
| qwen-image-2.0 | — | 0,06 $ / шт. |
| gpt-5.6-luna | Input: 0,2 $ / 1 million tokens Output: 1,2 $ / 1 million tokens | Input: 0,063 $ / 1 million tokens Output: 0,504 $ / 1 million tokens |
| grok-composer-2.5-fast | — | Input: 0,068 $ / 1 million tokens Output: 0,068 $ / 1 million tokens |
| clodex-cursor | — | Input: 0,07 $ / 1 million tokens Output: 0,07 $ / 1 million tokens |
| gpt-5.6-terra | Input: 2 $ / 1 million tokens Output: 12 $ / 1 million tokens | Input: 0,07 $ / 1 million tokens Output: 0,56 $ / 1 million tokens |
| deepseek-v4-pro | Input: 1,32 $ / 1 million tokens Output: 3,96 $ / 1 million tokens | Input: 0,08 $ / 1 million tokens Output: 0,08 $ / 1 million tokens |
| grok-4.5 | Input: 2 $ / 1 million tokens Output: 6 $ / 1 million tokens | Input: 0,08 $ / 1 million tokens Output: 0,08 $ / 1 million tokens |
| grok-4.6 | Input: 2 $ / 1 million tokens Output: 6 $ / 1 million tokens | Input: 0,08 $ / 1 million tokens Output: 0,08 $ / 1 million tokens |
| clodex-cursor-pro | — | Input: 0,084 $ / 1 million tokens Output: 0,084 $ / 1 million tokens |
| gemini-3.6-flash | Input: 0,75 $ / 1 million tokens Output: 3,75 $ / 1 million tokens | Input: 0,09 $ / 1 million tokens Output: 0,36 $ / 1 million tokens |
| kimi-k3 | — | Input: 0,09 $ / 1 million tokens Output: 0,09 $ / 1 million tokens |
| glm-5.2 | — | Input: 0,1 $ / 1 million tokens Output: 0,1 $ / 1 million tokens |
| gpt-image-2 | — | 0,1 $ / шт. |
| nano-banana-2 | — | 0,1 $ / шт. |
| deepseek-v4-flash | Input: 0,44 $ / 1 million tokens Output: 1,32 $ / 1 million tokens | Input: 0,12 $ / 1 million tokens Output: 0,12 $ / 1 million tokens |
| qwen-image-2.0-pro | 0,075 $ / шт. | 0,12 $ / шт. |
| qwen-image-3.0-pro | — | 0,12 $ / шт. |
| qwen3.7-max | Input: 2,5 $ / 1 million tokens Output: 7,5 $ / 1 million tokens | Input: 0,13 $ / 1 million tokens Output: 0,13 $ / 1 million tokens |
| glm-5.3 | — | Input: 0,15 $ / 1 million tokens Output: 0,15 $ / 1 million tokens |
| MiMo-V2-Flash | — | Input: 0,162116 $ / 1 million tokens Output: 0,162116 $ / 1 million tokens |
| qwen3.8-max | — | Input: 0,17 $ / 1 million tokens Output: 0,17 $ / 1 million tokens |
| grok-imagine-video-1.5 | — | 0,18 $ / шт. |
| MiniMax-M2.1 | — | Input: 0,2 $ / 1 million tokens Output: 0,2 $ / 1 million tokens |
| MiniMax-M2.5 | — | Input: 0,22233 $ / 1 million tokens Output: 0,22233 $ / 1 million tokens |
| MiniMax-M2.7 | — | Input: 0,22233 $ / 1 million tokens Output: 0,22233 $ / 1 million tokens |
| MiniMax-M3 | — | Input: 0,22233 $ / 1 million tokens Output: 0,22233 $ / 1 million tokens |
| gpt-5.5 | Input: 5 $ / 1 million tokens Output: 30 $ / 1 million tokens | Input: 0,25 $ / 1 million tokens Output: 1,5 $ / 1 million tokens |
| gpt-5.6-sol | Input: 5 $ / 1 million tokens Output: 30 $ / 1 million tokens | Input: 0,25 $ / 1 million tokens Output: 2 $ / 1 million tokens |
| claude-haiku-4-5 | Input: 1 $ / 1 million tokens Output: 5 $ / 1 million tokens | Input: 0,2805 $ / 1 million tokens Output: 1,4025 $ / 1 million tokens |
| claude-haiku-4-5-20251001 | Input: 1 $ / 1 million tokens Output: 5 $ / 1 million tokens | Input: 0,2805 $ / 1 million tokens Output: 1,4025 $ / 1 million tokens |
| claude-opus-4-7 | Input: 5 $ / 1 million tokens Output: 25 $ / 1 million tokens | Input: 0,3 $ / 1 million tokens Output: 1,5 $ / 1 million tokens |
| claude-sonnet-4-6 | Input: 3 $ / 1 million tokens Output: 15 $ / 1 million tokens | Input: 0,34125 $ / 1 million tokens Output: 1,70625 $ / 1 million tokens |
| claude-sonnet-5 | Input: 2 $ / 1 million tokens Output: 10 $ / 1 million tokens | Input: 0,35 $ / 1 million tokens Output: 1,75 $ / 1 million tokens |
| Kimi-K2 | — | Input: 0,423486 $ / 1 million tokens Output: 0,423486 $ / 1 million tokens |
| Kimi-K2-Thinking | — | Input: 0,423486 $ / 1 million tokens Output: 0,423486 $ / 1 million tokens |
| MiniMax-M2.7-highspeed | — | Input: 0,44466 $ / 1 million tokens Output: 0,44466 $ / 1 million tokens |
| claude-opus-4-8 | Input: 5 $ / 1 million tokens Output: 25 $ / 1 million tokens | Input: 0,45 $ / 1 million tokens Output: 2,25 $ / 1 million tokens |
| kimi-k2.5 | — | Input: 0,489655 $ / 1 million tokens Output: 0,489655 $ / 1 million tokens |
| kimi-k2.6 | — | Input: 0,701398 $ / 1 million tokens Output: 0,701398 $ / 1 million tokens |
| kimi-k2.7-code | — | Input: 0,701398 $ / 1 million tokens Output: 0,701398 $ / 1 million tokens |
| claude-opus-5 | Input: 5 $ / 1 million tokens Output: 25 $ / 1 million tokens | Input: 0,85 $ / 1 million tokens Output: 0,85 $ / 1 million tokens |
| kimi-k2.7-code-highspeed | — | Input: 1,402797 $ / 1 million tokens Output: 1,402797 $ / 1 million tokens |
| claude-fable-5 | Input: 10 $ / 1 million tokens Output: 50 $ / 1 million tokens | Input: 2,5 $ / 1 million tokens Output: 2,5 $ / 1 million tokens |
Partner price source: Clodex. Price check date: 2026-08-18.
SEO Mind42 does not sell API access or provide tokens: we recommend a third-party service Clodex. This is an affiliate link.
Compare models before you start
The service sets its plans, limits and model catalog. If they differ from this article, contact us so we can update it and record a new review date.
Browse modelsAffiliate link: your price stays the same and the project earns a commission.