Media > Advertisers > [Advertiser_Name] > Tag Management > Tag Managers
Important: To activate this feature, please contact your customer success manager
Note: This feature is protected by the following permission:
Tag Manager - Allow server to server calls
For example, it is not possible to use the Tag Manager JS code in a mobile app, but a client would like to track users who have seen Sizmek ads for a particular app, and then installed the app. In cases like these, we can establish a process by which a server implements code to call the Sizmek server directly, similar to an API call. In this example, the server that calls Sizmek Tag Manager is a server that belongs to an app attribution vendor like AppsFlyer or Tune.
In the Developer's tab, verify that the check box for server to server calls is enabled.
Verify that the server that calls the Sizmek server does not send a User-Agent in the request header.
If the server sends a User-Agent and is listed in the IAB whitelist, Sizmek will process the call.
If the server sends a User-Agent and is not listed in the IAB whitelist, it is considered a bot and will be dropped.
The following is an example of the URL that is used in a server-to-server call:
http://bs.serving-sys.com/Serving?cn=ot&onetagid=[tag_manager_id]&dispType=js&sync=0&pageurl=[URL_provided_by_vendor]&activityValues=$$[activity_values]$$&acp=$$[conditional_parameter]$$&ns=1&ebaddid=[advertising_device_id]&rnd=[unix time stamp]&usercookie=u2=[sizmek_user_ID_received_on_the_click_event]
The code must include either a device ID (
ebadid) or user cookie (
For more information about device tokens, see Adding Tokens to URLs .
For more information about activity values, see <noscript> Mode.