オークション広告キャンペーンの最適化レバー

最近更新时间：2025 年 3 月

TikTok広告マネージャーのオークション広告では、パフォーマンスに影響を与える多くの要因があります。広告配信を改善し、より多くのプレースメントを獲得するために、パフォーマンスの向上に使用できる一連の最適化レバーをご用意しております。


まだ数回しか広告を配信したことがない場合でも、すでに高パフォーマンスの広告を何度も配信していて、さらなる成果を出したいと考えている場合でも、最適化レバーの利用によりオークション広告キャンペーンの改善を目指せます。

  • Deduplication is not required if an advertiser shares different events separately between the Pixel and the Events API, without event overlap. 

    • For example, sharing AddToCart events through the Pixel, and CompletePayment events through the Events API.

  • Deduplication is required if an advertiser shares the same events through the Pixel and the Events API, with event overlap. 

    • For example, sharing CompletePayment events through both Pixel and the Events API.


How Deduplication Works 

To enable deduplication, developers must ensure the following three parameters are included in the event payload via both Pixel and Events API: 

  • pixel id

  • event (for example, CompletePayment or AddToCart)

  • event_id (a unique string chosen by the advertiser to represent visitor conversion) 


Additionally, we recommend advertisers include the first-party cookie (_ttp) in the event payload. If we do not receive the event_id from the Events API, but receive the TikTok cookie (_ttp), we will attempt to deduplicate between browser/server events based on the _ttp cookie value.


Please follow TikTok For Business Developers' documentation on ways to set up deduplication.


Deduplication Scenarios 

Please refer to the following scenarios and subsequent actions when an overlap occurs between the following:

  • Overlapping between Pixel events

    • We deduplicate any events shared through the Pixel, with the identical event and event_id parameters arriving within a 48-hour window from the first event.

  • Overlap between Events API events.

    • We deduplicate any events shared through the Events API, with the identical event and event_id parameters arriving within a 48-hour window from the first event.

  • Overlap between Pixel and Events API events.

    • We merge events shared by the Pixel and Events API events with the identical event and event_id parameters arriving within 5 minutes of each other and merge extra match keys and parameters into the first event if applicable.        

    • We deduplicate subsequent events shared by the Pixel and Events API events with the identical event and event_id parameters arriving after 5 minutes and within a 48-hour window from the first event.