We konden deze vermelding niet vinden. Er worden benaderende resultaten weergegeven. Controleer je spelling of stel voor deze term aan het woordenboek toe te voegen.
ユーザーIDアップロード
Create audience for uploading user IDs (by JSON) This spec change allows you to prepare an audience by creating an audience with no recipient specified first, and then adding user IDs or IFAs to the audience later. Recipients of an audience can be now specified by file You can now specify the recipients of an audience by file.
For more information, see Sending messages to multiple users via attribute data or retargeting (narrowcast messages) in the Messaging API documentation. Limit on the number of concurrent operations We'll set a limit of 10 concurrent endpoint operations per audience ID (audienceGroupId), for creating an audience for uploading user IDs and adding user IDs to an audience.
More Outage Report Messaging API 2021/07/05 We have set a limit on the number of concurrent endpoint operations for creating audience for uploading user IDs/adding user IDs As announced on June 21, 2021, we have set a limit on the number of concurrent endpoint operations for creating audience for uploading User IDs and adding user IDs to an audience, for the Messaging API, effective from July 5, 2021.
More 障害報告 Messaging API 2021/07/05 ユーザーIDアップロード用のオーディエンス作成/ユーザーID追加のエンドポイントに同時処理数の制限を設けました 2021年6月21日 にお知らせしたとおり、2021年7月5日よりMessaging APIにおいて、 ユーザーID アップロード用のオーディエンス作成およびオーディエンスへのユーザーID追加のエンドポイントに同時処理数の制限を設けました。
Each audience created can be distinguished by the audience ID passed in the response. Impacted endpoints Create audience for click-based retargeting Create audience for impression-based retargeting Create audience for uploading user IDs (by file) Create audience for uploading user IDs (by JSON) Rename an audience For more information on audiences, see Using audiences in the Messaging API documentation.
Create audience for uploading user IDs (by file) Add user IDs or Identifiers for Advertisers (IFAs) to an audience for uploading user IDs (by file) We've added new webhook events and an API endpoint to the Messaging API.
For more details, see the Error responses section of the Common specifications. Add user IDs or Identifiers for Advertisers (IFAs) to an audience for uploading user IDs (by JSON) Adds new user IDs or IFAs to an audience for uploading user IDs. For this endpoint, use JSON to specify recipients.
Create audience for uploading user IDs (by file) Add user IDs or Identifiers for Advertisers (IFAs) to an audience for uploading user IDs (by file) More Messaging API 2020/07/29 Get all valid channel access tokens v2.1 endpoint and content removed As announced on July 01, 2020, the Get all valid channel access tokens v2.1 API endpoint for Messaging API has been removed.
ユーザーIDアップロード用のオーディエンスを作成する(ファイル指定) ユーザーIDアップロード用のオーディエンスにユーザーIDまたはIFAを追加する(ファイル指定) More Messaging API 2020/07/29 すべての有効なチャネルアクセストークンv2.1を取得するエンドポイントとそのコンテンツを削除しました 2020年7月1日に告知 したとおり 、 すべての有効なチャネルアクセストークンv2.1を取得するMessaging APIのエンドポイントを削除しました。
You can't create a chat tag audience, friend path audience, web traffic audience, video view audience, app event audience, or image click audience with the Messaging API. Create audience for uploading user IDs (by JSON) Creates an audience for uploading user IDs.
Audience Description Audience for uploading user IDs A set of users that can be identified by user IDs or IFA (Identifier For Advertisers) Audience for click-based retargeting A set of users that clicked a URL in a message sent in the past Audience for impression-based retargeting A set of users that opened a message sent in the past Note You can't create a chat tag audience, friend path audience, web traffic audience, video view audience, app event audience, or image click audience with the Messaging API We've set a limit on the number of concurrent endpoint operations We've set a limit on the number of concurrent endpoint operations per audience ID (audienceGroupId), for creating an audience for uploading user IDs and adding user IDs to an audience.
Example response Error response Returns a 400 HTTP status code and the error response. For more details, see the Error responses section of the Common specifications. Create audience for uploading user IDs (by file) Creates an audience for uploading user IDs.
Learn more about Changing audience's authority level in the Messaging API reference. About audience's specifications Audience's specifications are as follows: Item Limit The number of audiences per channel Max limit: 1,000 Retention period of an audience Up to 180 days (15,552,000 seconds) The number of user IDs or IFAs you can upload to an audience for uploading user IDs per request When using JSON: Max limit: 10,000 When using file: Max limit: 1,500,000 The number of users per audience Audience for uploading user IDs: No limit Audience for click-based retargeting: Minimum 50 Audience for impression-based retargeting: Minimum 50 The period during which the retargeting audience* can be created after the message is sent Maximum 60 days (5,184,000 seconds) Audience for click-based retargeting and audience for impression-based retargeting.
Domain name Endpoint Get content Create audience for uploading user IDs (by file) Add user IDs or Identifiers for Advertisers (IFAs) to an audience for uploading user IDs (by file) Upload rich menu image Download rich menu image api.line.me Other API endpoints Rate limits The Messaging API applies the following rate limits for each endpoint.
Er worden alleen voorbeelden gegeven om u te helpen het woord of de woordcombinatie waarop u hebt gezocht, te vertalen. Deze worden niet door ons geselecteerd of gevalideerd en kunnen ongepaste taal bevatten. Wij vragen u melding te maken van voorbeelden die dienen te worden aangepast of verwijderd. Vertalingen met grof of informeel taalgebruik worden meestal rood of oranje gemarkeerd.