We’ve stumbled across something quite strange and are curious to know what is going on.
We keep encountering an INTERNAL_ERROR response when creating a Web Event Tag using the name ‘test’ (using any other names besides ‘test’ works fine). Also, this issue appears to be isolated to the 4no6av account as we haven’t been able to reproduce this with other accounts.
Using name ‘test’
$ twurl -X POST -H ads-api.twitter.com "/0/accounts/4no6av/web_event_tags?name=test&retargeting_enabled=true&click_window=14&view_through_window=1&type=CUSTOM"|jsonpretty
{
"errors": [
{
"code": "INTERNAL_ERROR",
"message": "Internal Error"
}
],
"request": {
"params": {
}
}
}
Same request using name ‘test1’
$ twurl -X POST -H ads-api.twitter.com "/0/accounts/4no6av/web_event_tags?name=test1&retargeting_enabled=true&click_window=14&view_through_window=1&type=CUSTOM"|jsonpretty
{
"data_type": "web_event_tag",
"data": {
"name": "test1",
"view_through_window": 1,
"click_window": 14,
"embed_code": "...",
"id": "nuex4",
"retargeting_enabled": true,
"type": "CUSTOM",
"deleted": false
},
"request": {
"params": {
"name": "test1",
"view_through_window": 1,
"click_window": 14,
"retargeting_enabled": true,
"account_id": "4no6av",
"type": "CUSTOM"
}
}
}
I did notice that there is a deleted web event tag with the name test for the 4no6av account.
Requesting deleted ‘test’ web site tag
$ twurl -H ads-api.twitter.com "/0/accounts/4no6av/web_event_tags/nttmh?with_deleted=true"|jsonpretty
{
"request": {
"params": {
"web_event_tag_id": "nttmh",
"account_id": "4no6av",
"with_deleted": true
}
},
"data_type": "web_event_tag",
"data": {
"name": "Test",
"view_through_window": 1,
"click_window": 14,
"embed_code": "...",
"id": "nttmh",
"retargeting_enabled": true,
"type": "DOWNLOAD",
"deleted": true
}
}
So I thought that perhaps you cannot create a new web even tag using the same name as that of a tag that has been deleted, but that does not really seem to be the case as I have successfully created several other tags reusing names of other previously deleted tags.
Any idea what might be causing this odd behavior?