Settings

• Track ID
• Track Domain
• Manual exclusion of referrers
• Cookie

Search for new links on the website 

Activate this to parse your page for link elements again. Useful for lazyloading mechanisms.

Track page information:

• Page name
  By default, the pixel creates a name on the basis of the page URL. Parameters and hashes in the URL are not automatically taken into account for the page name.
  Use this field to manually create a page name.
  
  
• Predefined page parameters
  Allows the tracking of additional information. Choose between a set of predefined parameters and simplify the setup process.
  Make sure that you've set up the parameters in Mapp Q3. Find more information here.
  
  
• Page parameter
  Allows the tracking of additional information. Add your custom parameter here.
  Make sure that you've set up the parameters in Mapp Q3. Find more information here.
  
  
• Content group
  Allows the categorization of pages.
  Make sure that you've set up the categories in Mapp Q3. Find more information here.
  
  

Track product information with an array of objects, that can have the following keys:

• id
• status ('view', 'basket', 'confirmation', 'list')
• cost
• quantity
• soldOut
• variant
• product parameter (ecommerce parameter)
• product categories

You can use the Mapp Intelligence Product variable for creating this array from an existing dataLayer structure.

Track order:

• order ID
• order Value
• currency
• coupon Value
• predefined order parameter:
  • paymentMethod
  • shippingService
  • shippingSpeed
  • shippingCost
  • grossMargin
  • orderStatus
• order parameter (ecommerce parameter)

When using website goals, all central goals (e.g., order tracked, user registration, newsletter sign-up) are quickly available for analyzing and filtering. Furthermore, the calculation of the customer journey is based on website goals. Find out more on this page.

• manually track a media code (campaignId) instead of using one from the url
• set 'Track once per session'
• campaign parameter

Track customer data:

• customerId
• overwrite customer validation
• predefined URM parameter:
  
  • emailRID
  • gender
  • birthday
  • country
  • city
  • street
• URM categories

Configure advanced settings:

• requestQueue:
• activate
• interval
• time in queue
• max. number of requests
• Cross Device Bridge:
  •  activate
  • image cache
• secure cookie
• request obfuscation
• send via SDK
• opt-out cookie name

Pick the tracking method here:

• Send track request: Let the underlying Smartpixel decide which request you need to track the data you mapped (recommended).
• Force page request: Sends a page request and omits all data that cannot be put in a page request (e.g. event name).
• Force event request: Sends an event request and omits all data that cannot be put in an event request (e.g. page parameter).
• No track request: Do not send a track request at all. This is useful if you only want to
  • reload form and link elements
  • just configure Mapp Intelligence
  • just add data but do not want to track it yet, because you might wait for more data in another trigger

By default, after each track request the Smartpixel is emptied. Check the 'keep data' box, if you want to reuse the data for another request.
Keeping the data does not work if the page is reloaded between requests.