After working with the Real-Time Audience API:
https://dev.twitter.com/ads/audiences/ta-realtime-integration-guide
We just noticed that an audience we updated through the Real-time API does not reflect the right size.
Initially we upload TON bucket of 1587 users and then we update with 154308 new users through the Real-Time.
This was the request:
[{
operation_type: 'Update',
params: {
membership_type: 'LIST_MEMBERSHIP',
advertiser_account_id: advertiserAccountId,
user_identifier: twitterUserIdStr,
user_identifier_type: 'TWITTER_ID',
audience_names: 'TEST - Sandbox Realtime Membership'
}
}, {}, ...]
Screenshot:
We didn’t notice that a second audience was created since the Real-Time Audience request was made with the LIST_MEMBERSHIP membership type.
It would be great to know if something was wrong in the update audience processing or this it the right way to create an initial audience and then update it.