Fusify Pixel — a simple way to see the real impact of advertising

Key Features of the Pixel

• Conversion Tracking. See which campaigns and channels deliver results and optimize your budget based on data.
• Post-click and Post-view Conversions. Evaluate the impact of ads not only after clicks but also after impressions.
• Impression Optimization. Use data on visits and engagement to select the most effective platforms, creatives, and audiences.
• Custom Segments. Create your own audiences and use them in retargeting to boost sales.

What We Collect

We only collect information available in standard web browsers and necessary for ad analytics:

• Website Events: Page views, clicks on key elements, adding to cart, etc.
• IP Address: To determine the country/city of the event.
• Timestamp: Records the time of the event.
• User-Agent: Device type, operating system, and browser.
• Cookies: Link user visits and actions to ad impressions and clicks.

What We Don’t Collect

We do not collect or request personal data from visitors, such as: name, phone number, email, physical address, payment details, or passwords. We also do not use digital fingerprinting technologies.

Use Case Examples

Session Tracking — We can track how many ad clicks lead to actual user sessions on the advertiser’s website.‍

Example:

• Site A delivered 100 clicks, with 80 sessions recorded — strong result.
• Site B also delivered 100 clicks, but only 40 sessions — weak result.
  → In this case, consider excluding Site B from the campaign.

Engagement Tracking — We can measure the share of sessions that lead to user engagement and optimize campaigns based on this metric. A session is considered engaged if at least one of the following conditions is met:

• The user spends more than 10 seconds on the site.
• The user scrolls more than 50% of the page.
• The user clicks on any element on the site.‍

‍Example:

• Out of 100 sessions from Site A, 60 are engaged users — strong result.
• Out of 100 sessions from Site B, 20 are engaged users — weak result.
  → Site B should likely be excluded from future placements.

Audience Collection for Remarketing — We can collect audiences from the client’s website for use in remarketing campaigns, including:

• Visitors to the entire site.
• Visitors to specific sections.
• Visitors meeting specific conditions (e.g., coming from Facebook).

Conversion Tracking — We can track conversions on the client’s website to help optimize campaign results. The pixel supports multiple types and paths of conversions, including:

• Click-Through Conversion (Direct Click Conversion) — A conversion that occurs when a user sees an ad, clicks on it, and completes a target action (e.g., purchase or registration) on the advertiser’s site. This type of conversion directly links the user’s action to the ad click, demonstrating its effectiveness.
• Assisted Click Conversion (Post-Click Conversion) — A conversion that occurs after clicking an ad but not immediately: the user returns later through another traffic source and completes the action. This metric highlights the supporting role of ads in the decision-making process.
• View-Through Conversion (Post-View Conversion) — A conversion that occurs when a user sees an ad (without clicking) and later converts through another traffic source. This type of conversion shows the impact of ad impressions on the user’s subsequent decision.

Pixel Code

1<script async src="https://pixel-tag.smartytech.io/tag.js?id=1"></script>
2<script>
3  window.pixelTagData = window.pixelTagData || [];
4  function fusifyTag(){pixelTagData.push(arguments);}
5  fusifyTag('js', new Date());
6  fusifyTag('id', '1');
7</script>

• The pixel code is the same for all advertisers except for the ID, which is unique to each account.
• The pixel performs domain verification. If the domain does not match the pixel’s settings, data is not sent.
• The pixel code loads asynchronously and generally does not affect page load speed for users.
• The pixel can be installed directly on the site or through tag managers like Google Tag Manager, Floodlight, etc.
• All events collected by the pixel are sent to the URL endpoint: https://events.smartytech.io/signal.

How to create a Pixel

Overview of the Pixel Section

To create a new pixel, go to the Management → Pixels section.

Here you can:

• View Pictorial view of the list of all existing pixels.
• See the number of unique users recorded in the last 7 days for each pixel.
• Access pixel editing options through the context menu.
• Create a new pixel by clicking the “+” button in the top left corner of the table.

Creating a Pixel

After clicking the “+” button, you will be taken to the pixel creation screen.

• Pixel Name — In most cases, the site’s address will suffice.
• Owner — Select the owner; only the owner will have access to the data and can use the pixel in their ad campaigns. Note that the owner cannot be changed after the pixel is created.
• Tracked Domains — Typically, this is the main domain of the site, but advertisers may have domains in different language zones. List all domains to be tracked.
  
  • This field serves as a security measure to prevent data collection from unauthorized domains.
  • If the pixel is installed on an unverified domain, data will not be collected.
• Click “CONFIRM” to complete the pixel creation.

Obtaining the Pixel Code

You can obtain the pixel code by using the corresponding menu item.

Installing the Pixel Code on the Website

Installing the pixel on the website is typically handled by the client’s technical team. The pixel can be embedded directly into the page’s source code or through a tag management system, such as Google Tag Manager.

In most cases, the pixel should be installed on all pages of the advertiser’s website.The process of installing our pixel is no different from installing ad pixels used by Facebook, Taboola, TikTok, and other advertising platforms.

Verifying Pixel Installation on the Website

To ensure the pixel is correctly installed on the website, follow these steps:

1. Open the browser.
2. Open the developer console and go to the Network tab.
3. In the search/filter field, enter smartytech.
4. Without closing the console, navigate to the website where the pixel is installed.
5. After the page loads, you should see network events containing signal? — if these events are visible, the pixel is working correctly.
6. Visit several different pages on the site to ensure the pixel is installed on all pages.

Overview of pixel signals

After creating a pixel, a default set of signals is automatically generated:

• load_page — Triggers when a page loads.
• session — Triggers at the start of a user session. A session is defined as a site visit with a 30-minute inactivity timeout. If a user returns after 30 minutes, a new session is recorded.
• click — Triggers on any click on the site.
• engagement — Triggers when a user engages; recorded once per user per session. Engagement is counted if at least one of the following conditions is met:
  
  • The user spends more than 10 seconds on the page.
  • The user scrolls at least 50% of the page.
  • The user clicks on any element on the page.

The Signals table displays the following data:

• Name — The name of the signal.
• Type — The type of signal, possible values:
  
  • Basic — Automatically created by the system.
  • Business — Manually created by the user.
• Created At — The date and time the signal was created.
• Lifetime — The period during which users remain in the signal.
  This is a critical parameter, as each signal can be used as an audience segment for targeting.
  Example: If the lifetime is set to monthly, a user added to the signal on March 1, 2025, will be automatically removed on March 31, 2025, and will no longer be available for targeting.
  In most cases, it is not recommended to set an excessively long retention period, as users may lose interest in the product or service, making further targeting less effective.
• Users (7 days) — The number of users added to the signal in the last 7 days.

Additionally, through the context menu, advanced reports for the last 30 days are available, including:

• Unique Users in Audience — The total number of unique users currently in the signal.
• Signals (Last 30 Days) — A daily count of signal events over the last 30 days.
• Unique Users (Last 30 Days) — A daily count of unique users added to the signal over the last 30 days.

How to create a business signal

Basic Settings

To create a new signal, click the “+” button in the top left corner of the Signals screen for your pixel. After clicking, you will be taken to the signal creation screen.

• Signal Name — Enter the signal name.
  Only Latin characters are allowed — no spaces.
  Example: "signal name" — incorrect, "signal_name" — correct.
  Important: The signal name cannot be changed after creation.
  If an error is made in the name, you must delete the signal and create a new one.
  If the signal has already collected data, deleting it will result in the loss of that data — it cannot be transferred to another signal.
• Conversion (Yes/No) — Check this option if the signal represents a conversion. If enabled, the signal will appear in campaign reports, and the system will allow analysis and optimization based on this metric.
• Lifetime — Specify how long users remain in the signal. You can choose a duration from 1 day to 3 months. Configure this thoughtfully and select a duration that aligns with your business goals.
  This only affects the time users remain in the signal’s audience, not the overall availability of analytical data.
• Source — Select the type of event that will trigger the signal.
  In most cases, load_page is optimal.
  Sometimes — for example, if the conversion is a form submission — form_submit is more appropriate.
  If you’re unsure about the choice, contact us.

All Events / Custom Events

• When selecting All Events, the signal triggers every time the selected Source event occurs.
• When selecting Custom Events, the signal triggers only when additional conditions are met.

Setting Up Additional Conditions

Additional conditions allow you to create business signals that track specific user actions. Below, we’ll explore the creation of several such signals.

Use Case 1: Tracking Users Who Completed a Purchase by Visiting the “Thank You” Page

After placing an order, users are redirected to a thank-you page, e.g., https://anabel-arto.com/thanks/34917. We want to track visits to these pages.

Signal Settings:

• Name: thank_you_page
• Lifetime: Monthly
• Source: load_page — since we are tracking the page load event

Custom Event Conditions:

• Type: document_location — checks the page URL
• Assert: contains — checks if the URL contains the specified value
• Value: /thanks/ — part of the thank-you page URL

Use Case 2: Tracking Users Who Signed Up for a Test Drive via a Form

Example: https://www.nissan.ua/test-drive.html

After analyzing the page code, it was found that the form does not have a unique name. Nevertheless, tracking form submissions is possible.

Signal Settings:

• Name: test_drive_submit
• Lifetime: Monthly
• Source: form_submit — tracking the form submission event
• Custom Event: Enabled

Custom Event Conditions:

• document_location — uses the page URL for verification
• Assert: contains — checks if the URL contains the specified value
• Value: /test-drive — to rule out unrelated forms, ensures the page URL contains /test-drive

Use Case 3: Tracking Users Who Clicked to View the Price List

Example: https://www.nissan.ua/vehicles/new-vehicles/x-trail.html

To track this event, you need to identify the CSS class of the button on the site. The business signal should be configured as follows:

Signal Settings:

• Name: view_price_list
• Lifetime: Monthly
• Source: click — since we are tracking a click event
• Custom Event: Enabled

Custom Event Conditions:

• Type: click_class — checks the class of the clicked element
• Assert: contains — checks if the element has the specified value
• Value: ns-secondary-header-button ns-button-light — the button class value obtained from the advertiser’s site