Samsung Pixel Implementation Guide

09 Apr 2026
4 Minutes to read

Share
Dark
Light

Samsung Pixel Implementation Guide

Updated on 09 Apr 2026
4 Minutes to read

Share
Dark
Light

Article summary

Did you find this summary helpful?

Thank you for your feedback!

If you are using a direct HTML code, a Tag Manager, or JavaScript, this guide provides a comprehensive walkthrough for integrating Samsung pixels into your website, By following these steps, you can accurately capture key events such as page views, lead generation, and purchases, enabling Samsung Ads to deliver more targeted and efficient ad campaigns.

Implementing Samsung pixels

Implementing Samsung Pixels into your website(s) require(s) access to your website(s), HTML, or a Tag Manager if one is in use. Learn more at Create a Samsung pixel.

Pixel types

Static pixels: Pixels that do not obtain and send dynamic values to Samsung Ads. Currently in the UI, there are three pixel types you can choose from: Purchase, Page View, and Lead Generation.
Dynamic pixels: Pixels supporting dynamic parameters that are sent to Samsung Ads, value={purchase_revenue} and oid={order_id}. These dynamic parameters will be utilized for both order tracking confirmation and Return on Ad Spend (ROAS) metrics calculation. Currently in the UI, the Purchase Event Type’s default code snippet provided has the dynamic parameters included, however, to obtain these actual values from your system, see the Tag Managers section below.

Universal & event-specific pixels

It is recommended that you use at least two pixels on all Purchase and Lead Generation campaigns: a Page View pixel on all pages your customers can access and an outcome event pixel, such as the Purchase pixel, on only the page(s) where that event occurs.

Implementing Page View pixels on all relevant website pages your customers can access, enables Samsung Ads to both collect signals for page views and your selected conversion event, and collect other signals for Samsung Ads’ Machine Learning optimization models.

Inserting Samsung pixels into your website

Samsung Ads provides simple HTML code snippets for direct use in your website code via a Tag Manager, or via JavaScript as detailed below.

HTML

Implement the code snippet provided in the Ad Manager UI by copying-and-pasting the snippet in between the <body> opening and closing HTML tags, as shown below.

HTML Page View snippet example:

<img src="https://amp.samsungads.com/pixel/AM-1234?event_type=page_view" width="1" height="1" style="display:none;">

NOTE:
The tag shown above is an example and should not be used – instead, use the code snippet provided in the Ad Manager Events Manager.

HTML Lead Generation snippet example:

<img src="https://amp.samsungads.com/pixel/AM-1234?event_type=lead_generation" width="1" height="1" style="display:none;">

NOTE:
The tag shown above is an example and should not be used – instead, use the code snippet provided in the Ad Manager Events Manager.

HTML Purchase snippet example:

<img src="https://amp.samsungads.com/pixel/AM-1234?event_type=purchase&value={purchase_revenue}&oid={order_id}" width="1" height="1" style="display:none;">

NOTE
The tag shown above is an example and should not be used – instead, use the code snippet provided in the Ad Manager Events Manager.

Tag Managers

Google Tag Manager

The content below is provided as a general guide for utilizing the Samsung Ads pixel code snippet with Google Tag Manager (GTM). We recommend reviewing Google’s documentation prior to any changes to ensure the latest official instructions from Google are utilized, ensuring success.

Get dynamic data into your pixel

Below is a step-by-step workflow to get dynamic data into your pixel:

Expose the Data via the dataLayer.
Google Tag Manager (GTM) doesn't know order details unless it’s told – the cleanest way to do this is to push an object to the window.dataLayer on your order confirmation web page.
Code snippet: Place this above your GTM container snippet or as part of your checkout success logic.
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
  'event': 'purchase',
  'order_id': '12345', // This should be a dynamic variable from your backend/state
  'order_value': 99.99, // This should be a dynamic variable from your backend/state
  'currency': 'USD'
});
Create a Data Layer Variable in GTM.
Now that the data is available to the browser, map it so GTM can use it as a variable:
1. Open your GTM container and go to Variables.
2. Under User-Defined Variables, click New.
3. Choose Data Layer Variable as the type.
4. Data Layer Variable Name: Enter order_id (it must match the key in your JavaScript exactly).
5. Name the variable dlv - order_id and Save.
6. Follow the same steps for order_value using the variable dlv - order_value.
Create a Trigger.
You only want your pixel to fire when a purchase actually happens, not on every page load.
Follow the steps below to create a trigger:
1. Go to Triggers > New.
2. Choose Custom Event.
3. Event Name: Enter purchase (matching the 'event' key from your code in Step 1).
4. Name it Event - Purchase and Save.
Instrument the Pixel Tag.
Insert the dynamic variables into your pixel code.
1. Go to Tags > New.
2. Choose Custom HTML.
3. In the code area, replace the hardcoded value with your GTM variable in double curly braces:
```
<img src="https://amp.samsungads.com/pixel/AM-1234?event_type=purchase&value={{dlv - order_value}}&order_id={{dlv - order_id}}" width="1" height="1" style="display:none;">
```
4. Set the Triggering to your Event - Purchase trigger.
Use GTM's Preview Mode to ensure everything is firing correctly. Follow the steps below to verify that everything is working correctly.
1. Click Preview in GTM and navigate to your site's purchase confirmation page.
2. Complete a test purchase.
3. In the Tag Assistant window, look for thdse purchase event in the left sidebar.
4. Click the Variables tab to verify that dlv - order_value is pulling the correct numerical amount from your code.
5. Ensure your backend doesn't send the value as a string with currency symbols (e.g., "$99.99"). Samsung Ads expects a Float value (e.g., 99.99).

JavaScript pixel implementations

If you prefer to utilize JavaScript for your pixel, we recommend following the examples below.

Google Tag Manager Custom HTML with Order ID and Order Value dynamic variables

(See Step #4 in the Google Tag Manager instructions above).

<script> (functio(){ var AMPIXEL = newImge(); AMPIXEL.src = "https://amp.samsungads.com/pixel/AM-1234?event_type=purchase&value={{dlv - order_value}}&order_id={{dlv - order_id}}"; })(); </script>

Google Tag Manager Custom HTML without dynamic variables

(See Step #4 in the Google Tag Manager instructions above).

<script> (function() { var _AM_PIXEL = new Image(); _AM_PIXEL.src = "https://amp.samsungads.com/pixel/AM-1234?event_type=purchase"; })(); </script>

Custom webpage HTML without dynamic variables

Simply update the src element "https://amp.samsungads.com/pixel/AM-1234?event_type=purchase" shown below with your pixel src from the Ad Manager UI.

<script> (function() { var _AM_PIXEL = new Image(); _AM_PIXEL.src = "https://amp.samsungads.com/pixel/AM-1234?event_type=purchase"; })(); </script>

Samsung pixel FAQs

How long will it take to see pixel events data in the UI?

Data from pixel fires should normally appear within 15-30 minutes from the page firing the pixel.

Was this article helpful?

What's Next

Audiences

Table of contents

Implementing Samsung pixels
Samsung pixel FAQs