web_event_tag - ID confusion


#1

Is the id supposed to be the same id in the embedded code ?
I get this response - “nuqgf” is in the embedded code, but the id is “nuogb”

“data_type”: “web_event_tag”,
“data”: {
“name”: “TestWebTag”,
“view_through_window”: 30,
“click_window”: 30,
“embed_code”: “\u003Cscript src=”//platform.twitter.com/oct.js" type=“text/javascript”\u003E\u003C/script\u003E\u003Cscript type=“text/javascript”\u003Etwttr.conversion.trackPid(‘nuqgf’, \u007B tw_sale_amount: 0, tw_order_quantity: 0 \u007D);\u003C/script\u003E\u003Cnoscript\u003E\u003Cimg height=“1” width=“1” style=“display:none;” alt="" src=“https://analytics.twitter.com/i/adsct?txn_id=nuqgf&p_id=Twitter&tw_sale_amount=0&tw_order_quantity=0” /\u003E\u003Cimg height=“1” width=“1” style=“display:none;” alt="" src="//t.co/i/adsct?txn_id=nuqgf&p_id=Twitter&tw_sale_amount=0&tw_order_quantity=0" /\u003E\u003C/noscript\u003E",
“id”: “nuogb”,
“retargeting_enabled”: true,
“type”: “SITE_VISIT”,
“deleted”: false
},
“request”: {
“params”: {
“name”: “TestWebTag”,
“view_through_window”: 30,
“click_window”: 30,
“retargeting_enabled”: true,
“account_id”: “luyeg”,
“type”: “SITE_VISIT”
}
}
}


#2

I think is not supposed to be the same id.

One is to relate your web_event_tag with your campaign, and the other is to registrer the events wuen you implement the pixel.


#3

I beg to differ, @hector_borras. I think they should be the same. I also checked my web event tags that I have stored in my database and in the pixel’s code it is the same id as the web_event_tag’s id.


#4

Mmmm, this is strange. Look at this:

This is the code I get from Twitter ads UI for a pixel:

`

`

The id is `id: nu20q’.

In our platform, we update and save events every 24h.

Whis is the data related with that web_event_tag -> nu1zt

And I’m going to do the request throught twurl:

twurl -H https://ads-api.twitter.com '/1/accounts/18ce549803x/web_event_tags/nu1zt' | json
{
    "data": {
        "click_window": 7,
        "deleted": false,
        "embed_code": "<script src=\"//platform.twitter.com/oct.js\" type=\"text/javascript\"></script><script type=\"text/javascript\">twttr.conversion.trackPid('nu20q',  { tw_sale_amount: 0, tw_order_quantity: 0 });</script><noscript><img height=\"1\" width=\"1\" style=\"display:none;\" alt=\"\"  src=\"https://analytics.twitter.com/i/adsct?txn_id=nu20q&amp;p_id=Twitter&amp;tw_sale_amount=0&amp;tw_order_quantity=0\" /><img height=\"1\" width=\"1\" style=\"display:none;\" alt=\"\"  src=\"//t.co/i/adsct?txn_id=nu20q&amp;p_id=Twitter&amp;tw_sale_amount=0&amp;tw_order_quantity=0\" /></noscript>",
        "id": "nu1zt",
        "name": "Cyberclick-Reserva-ES",
        "retargeting_enabled": true,
        "type": "PURCHASE",
        "view_through_window": 1
    },
    "data_type": "web_event_tag",
    "request": {
        "params": {
            "account_id": "18ce549803x",
            "web_event_tag_id": "nu1zt"
        }
    }
}

And that’s what I was saying before.

Could you check this @majoritasdev


#5

Yes, I checked and you are right, Hector! I think they’ve changed this in v1 and Ads UI, as the id is not the same anymore. In this case, I’m waiting for a response from Twitter Staff with as much interest as SteelHouse.