Page tree
Skip to end of metadata
Go to start of metadata

Description

Altcraft pixel is a stack of tracking technologies based on HTML and JavaScript tracking codes, that you place in your website and messages.

A pixel generates an HTTP request to Altcraft Marketing tracking module. It can retrieve various customer data:

  • geographic location;
  • platform and browser;
  • actions of the subscriber on the site — before and after the subscription;
  • preferences and interests.

Pixels are extremely convenient in segmentation queries: you can segment profiles by pixel activation times, pixel goals and goal values or referer web pages. You can specify a time period to make more precise audience slices. 

Pixel technologies also take a great part in keeping your databases up to date by refreshing profile location and device information.

Pixel goal achievement can be monitored via  Goals report .


Enabling pixels

When using Altcraft Marketing On-premise on your hardware, Pixels must be first enabled in platform administrative panel by ticking "Enable pixel" in account settings.

To use pixels, you need to configure HTTPS protocol for both your website and the platform.

After activation you'll see the new section "Pixels" in the platform interface.


Creating pixels

Let's create a new pixel script. First of all, you have to give it a name, write a description, set access groups and a database to process.

If you'd like to prevent unwanted pixel double activation, limit the time before another activation in the "Lock double trigger activation" field.

Allow to import data on this pixel — use this field to enable customer profile import at the moment your customer activates a tracking code.

Pixels can update your existing profiles or create the new ones, including for anonymous website visits:

  • HTML pixels (image and URL redirect) use your customers' session data (cookie) for matching profiles. If a profile with the same cookie (e.g. pened mail from the same device) is not found - a new anonymous profile will be imported.
  • JavaScript tracking codes can use both cookie data and customer profiles information. If a profile is found, its data will be updated; if the profile isn't found, a new profile will be created with the data you can specify.

JS pixel import is described further on this page.  

After you save a new pixel, you'll be able to open Get pixel code interface. The first thing is to decide upon tracking technology you need:

  • Show a page a JavaScript code that can be customized to detect user actions like scrolling a page within a specific time period.
  • Show a page (No JS) — this is a somewhat classic pixel technology,  representing a transparent image wrapped in a tracking HTTP request. It can be used for both your website and messages — no JavaScript required.
  • Click a link (No JS) this technology is a hyperlink wrapped in a redirect tracking request. It can be used in social networks and any external resources.

For all pixel types you can set goals and goal values:


When a pixel code is created, give it to your website developers to implement it into your web site or application code  and it will start tracking your customers' actions.

For each script, you can select several goals and a common value for them (cost).

When placed on the page, the code will register the specified goals, no additional action is required. Each code created in a pixel will associate goals with that particular pixel. This logic can be used to compare conversions across different landing pages, websites, and data collection forms.

Web page tracking

Configuring the code

The script is placed on those pages where you want to track your customers' actions. When a user visits the page, pixel will record goals you specify in pixel settings ("Add goals"). You can record one value for these initial goals.

Below you can set to activate pixel at once when the page is loaded, or to wait for page scrolling to exclude random website visitors from the query. 

After you configure a new pixel, give its code from the "Show a page" tab to your website developers along with the information from this page.

Recording goals via API methods

On the web page with the script implemented you can track any of your customers actions based on browser events. For example, these can be a mouse focus on a specific banner - or a popup activation - or leaving a page. On these events you can record customer's target actions and their values. For commercial actions you can register both profit and fees, if any.

For the page elements and browser events use the following method -  ak_pixel_push() :

These arguments are used to record target actions:

  • tags - goal name or names. Can contain a string value or an array of strings.
  • value - value or price for the goals. Can contain positive and negative floating point values.
DescriptionMethod
Simple callak_pixel_push()
Goal registrationak_pixel_push("click")
Goal and value registrationak_pixel_push("click", 100)

Several goals with a negative value. One value will be recorded for all the goals

ak_pixel_push(["click", "cars"], -100.40)

Customer profiles import and update (JS)

If customer profiles import is enabled in pixel settings, you can add arguments for searching an existing profile to update- and for adding profile data: ak_pixel_push(tags, value, match, update, matching_mode):

  • match - this one is used for profile search. It is an object with one or two properties: "search field": "field value" и "db_id": "profile database ID" - in case a database is not specified for the pixel.

    db_id can be ignored when a profile database is specified in pixel settings.

  • update - can contain any customer profile data including subscriptions. 
  • matching_mode - can contain one of the following values: "email", "email_profile", "phone", "profile_id" or "custom" for the corresponding profile search modes.

    matching_mode can be ignored when searching by custom fields. 

Example of goal registration with profile import

ak_pixel_push("registration", 100, {
        "db_id": 12,
	"Client_ID": 12311541
}, {
	"_fname": "Nikita",
	"_lname": "Ryazanskiy",
	"subscriptions": [{
		"resource_id":3,
		"channel": "email",
		"email": "nikita.ryazanskiy@example.com"
	}]
});
Goals and associated values can be recorded to customer profiles with the help of a direct API call as well.

Redirects via pixel settings

If you allow redirects via the pixel, the user will be redirected to the URL you specified at  the moment he hits your pixel.

Redirect links can be used for fraud by sending phishing message with redirect_url. To avoid this, pixel in Altcraft MP does not support redirect by default. To engage this option, you need to activate this flag:

When flag is activated, you can enter domains list allowed for redirect, in the field below

After these settings, redirect in messages with pixel will be available on for enlisted domains. Redirect for other domains will be restricted.


Setting up Altcraft pixel goal registration using Google Tag Manager (GTM)

For the convenience of placing the Altcraft pixel on the site pages, you can use the Google Tag Manager containers (if it's installed on the site).

For this:

1. Create a new pixel and set basic settings: pixel name, description, access groups and associated databases.

2. After saving the pixel, the tracking code configuration interface will be available. Copy the pixel code from the "Show a page" tab.

Before copying the pixel code, uncheck the "Auto load pixel" box. Only this way you can use the tracking code as a library.


3. Your next step is to go to the GTM workspace and create a new tag. Choose Custom HTML as a tag type.


4. Add the Altcraft pixel code to the "HTML" field in the "Tab Configuration" window. Choose "All pages" in the "Triggering" tab. Save it.

When you submit the changes, the container with Altcraft pixel code will be loaded on all pages of your site.

5. Now, to transfer goals and, if necessary, their values to Altcraft, add the required number of "Custom HTML" Tags configured for the Triggers you need.

<script>
	ak_pixel_push("PageView", 0);
</script>

Arguments are added by analogy with Recording goals via API methods.


  • No labels