Set up connected TV campaigns on Samsung TV
With Adjust's partnership with Samsung, you can add your Adjust tracker URL to creatives you serve in Samsung TV campaigns. This lets you measure the success of your CTV campaigns and their role in driving mobile app installs.
Here's what you need to know before getting started.
- Adjust is an approved vendor for Samsung Ads. This means that representatives from Samsung handle the implementation of your creatives and Adjust trackers in the Samsung platform.
To create an Adjust connected TV tracker, follow these steps.
- Find your app and select your app options caret (^).
- Select Tracker URLs.
- Select the Connected TV Trackers tab.
- Select NEW TRACKER.
- Enter a tracker name.
- Select Samsung from the network dropdown menu.
- Select Campaign Structure, and update the campaign structure parameters to map to your preferred Samsung macros.
- Check the full list of available Samsung network macros you can use.
- Before setting up your campaign parameter mappings, always consult your Samsung representative.
- Select APPLY.
- Optional: Customize the attribution window.
- Select CREATE.
- Finally, append the following parameter-value pairs to your tracker URL to support probabilistic impression tracking.
This is an example Samsung connected TV tracker with optional network macros mapped to Adjust campaign parameters, and the necessary impression-tracking parameters appended.
Samsung Ads is a managed service. This means that you do not need to manually upload your creatives to the platform or add Adjust trackers to creatives yourself.
Once you have created your connected TV tracker URL in the Adjust dashboard, reach out to your Samsung Ads representative. You can send them both the tracker(s) and creative(s) you will run in your campaign, and wait for their confirmation. And that's it - you're all set!
|integer||The advertiser ID for this impression. Example: 324|
|string||The URL component encoded name of the advertiser for this impression. Example: "Acme%20Corp"|
|string||The application bundle ID identifying the application from which the ad request was initiated, for in-app advertisements. Example: "com.ae.history"|
This value is configured or passed to the ad exchange by the application publisher or representative for in-app advertisement traffic originating from various app platforms such as iOS, Android, Tizen TV, etc. App bundle ID values may be re-used between platforms so it is advisable to consider this value in conjunction with user-agent or detected device and/or platform type. For example, "com.ae.history" on Tizen TV may be different than "com.ae.history" on Android.
|integer||The campaign ID for this impression.|
|string||The click tracker URL. Example: "http://rtb.adgrx.com/clicks/|
Appending a second URL to this URL will result in AdGear counting a click for this impression and re-directing to the second URL.
|string||Same as __CLICK_TRACKER_URL__ but URL component encoded. |
|integer||The creative ID for this impression. Example: 234|
|string||The device unique ID type. Possible values are: ag_cookie, apple_ifa or google_ifa|
|string||The device unique ID value to go along with the device unique ID type.|
|string||The format/size for this impression. Example: "300x250"|
|integer||The flight ID for this impression. Example: 324|
|string||A random number string typically used to construct non-cacheable URLs.|
|string||The spot ID for the impression, unique to a single spot within a bid request. Example: "5664451242760709529"|
Note: A single bid request may contain multiple spots, so an impression is uniquely identified by the combination of __BID_REQUEST_ID__ and __SPOT_ID__
|integer||The number of seconds elapsed since the epoch date, January 1, 1970 (UTC) at the time of the impression call. Example: 1490936822|
|string||The unique ID for this impression. Example: "c0728d4e-6691-11e3-9c63-|
This is typically used for server-side conversion tracking. It can be passed via a click tracker to the destination page where the destination site later associates it with a transaction and reports it back to AdGear by calling a conversion tag.
Note that this is usually equal to __BID_REQUEST_ID__:__SPOT_ID__
|integer||Numerical version of the __TXN_ID__, useful when you need a unique integer ID for a BidRequest and Impression combo.|
|NOTE: This macro cannot be used for conversion attribution.|
|string||The IP address of the browser/device for this impression. Example: 192.168.1.1|