Your Shorts song join is picking the wrong creator

Описание и применение

Автоматизация обработки таблиц YouTube Shorts предотвращает неверное сопоставление видео с создателем, используя trackId вместо videoId и валидируя обязательные поля.

Задача

Campaign shortlist changes creators after a re-run because the join key uses videoId instead of trackId, causing linked uploads to become campaign targets.

Результат

By separating track identity from video details and validating required fields, the automation prevents incorrect creator assignments and ensures reliable campaign data.

Рабочий процесс

• 1. Request the song chart without video details using ApifyClient with includeVideoDetails:false.
• 2. Keep onlyNew off for warehouse ingestion and let Postgres handle deduplication.
• 3. Store chart entries with trackId, chart observation, optional linked video, and separate creator research.
• 4. Wait for run completion and retain run ID for recovery.
• 5. Validate fields with Zod schemas (StatusRow, TrackRow) to quarantine identity failures.
• 6. Preserve valid rows from failed runs and delay campaign export until run passes release checks.

Доказательства

Your campaign shortlist changes creators after a re-run. The song hasn’t changed. Your join key has.

Источник

If you joined videoId straight into your creator table, a linked upload quietly became the campaign target.

Источник

Start with a narrow research slice. Leave video enrichment out until you’ve a reason to investigate an attached upload.

Источник

Keep the returned ID in your job history. If database ingestion stops halfway through, resume that run instead of asking “latest” for another snapshot.

Источник