We are having trouble setting tailored audience targeting with web event tags.
Following are the request / response logs from our system (including all targeting parameters). Is there a whitelist for this feature?
info] c.b.i.t.s.TwitterAdService$ - Create Targeting Criteria: twurl -H ads-api.twitter.com -d “locations=96683cc9126741d1&line_item_id=2pu7n&tailored_audiences_excluded=l6cqv&tailored_audiences=l6cqw&platforms=4&wifi_only=false” /0/accounts/68ey9r/targeting_criteria
DefaultHttpRequest(chunked: false)
PUT /0/accounts/68ey9r/targeting_criteria HTTP/1.1
Host: ads-api.twitter.com
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Authorization: OAuth oauth_consumer_key=“HDgMOrYesLgvwbFl9ZzokSV4U”, oauth_nonce="-7445013918442823691", oauth_signature=“c09%2BGxm7eb6710461vHxemlXhQY%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1435691183”, oauth_token=“376931583-4ahGl9CXKFg97XQPXz4IkBuF9uSQzw1hI2zkMLEM”, oauth_version="1.0"
Connection: keep-alive
Accept: /
User-Agent: NING/1.0
Content-Length: 132
[debug] c.n.h.c.p.n.NettyAsyncHttpProvider -
Request DefaultHttpRequest(chunked: false)
PUT /0/accounts/68ey9r/targeting_criteria HTTP/1.1
Host: ads-api.twitter.com
Content-Type: application/x-www-form-urlencoded; charset=utf-8
Authorization: OAuth oauth_consumer_key=“HDgMOrYesLgvwbFl9ZzokSV4U”, oauth_nonce="-7445013918442823691", oauth_signature=“c09%2BGxm7eb6710461vHxemlXhQY%3D”, oauth_signature_method=“HMAC-SHA1”, oauth_timestamp=“1435691183”, oauth_token=“376931583-4ahGl9CXKFg97XQPXz4IkBuF9uSQzw1hI2zkMLEM”, oauth_version="1.0"
Connection: keep-alive
Accept: /
User-Agent: NING/1.0
Content-Length: 132
Response DefaultHttpResponse(chunked: false)
HTTP/1.1 404 Not Found
content-disposition: attachment; filename=json.json
content-length: 128
content-type: application/json;charset=utf-8
date: Tue, 30 Jun 2015 19:06:22 GMT
server: tsa_a
set-cookie: guest_id=v1%3A143569118211646483; Domain=.twitter.com; Path=/; Expires=Thu, 29-Jun-2017 19:06:22 UTC
strict-transport-security: max-age=631138519
x-access-level: read-write-directmessages
x-connection-hash: d144ad88927551cda2703b340fc6a702
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-rate-limit-limit: 300
x-rate-limit-remaining: 298
x-rate-limit-reset: 1435691237
x-response-time: 30
x-runtime: 0.021391
x-transaction: 122d23c21f78b493
x-tsa-request-body-time: 0
x-xss-protection: 1; mode=block
[debug] c.n.h.c.p.n.NettyConnectionsPool - Adding uri: https://ads-api.twitter.com:443 for channel [id: 0xff3130e9, /192.168.2.4:61073 => ads-api.twitter.com/199.59.150.10:443]
[info] c.b.i.t.s.TwitterAdService$ - 404: {“errors”:[{“code”:“NOT_FOUND”,“message”:“Targeting Criterion l6cqw was not found for Account 68ey9r”}],“request”:{“params”:{}}}
[error] c.b.i.t.s.TwitterAdService$ - Failed to create targeting criteria: Targeting Criterion l6cqw was not found for Account 68ey9r
