Reports displays the details similar to the Dashboard in a list format. You can display reports either for the Staging or Production environment.

While tag details are accessible in the Live Debugging and Dashboard sections, Reports offer critical data for debugging. They provide insights into the tags triggered during a session, including their frequency and associated metrics for data analysis. This information is crucial for diagnosing errors at various levels—whether related to the tag itself, the provider, transformation functions, configuration issues, or missing attributes. Using Reports, users can pinpoint specific problems and missing data that may lead to tag failures.

Related Topics

The Reports section includes the following topics:

Introduction

This document explains the step-by-step procedure to edit a Data Element.

Procedure

To edit the Data Element, perform the following steps:

Step 1: Select the Data Element you want to edit.

Step 2: From the Actions drop-down menu on the top right corner, select Edit.

Step 3: Edit the Data Element details and click Save on the top-right to save the changes.

Introduction

When you select a Project, the default Dashboard opens automatically. However, if you want to create a new Dashboard, follow these steps.

Procedure

Step 1

Introduction

A dashboard can be shared with multiple users, and existing users can also be removed from a shared dashboard as needed.

Procedure

Perform the following steps to share the Dashboard with other users:

Introduction

You can edit the Tag details of a particular tag.

Procedure

To edit the tag, perform the following steps:

Introduction

This document explains step by step how to add Triggers to the server side. All the required information is collected directly from the server.

Procedure

To add a new server-side trigger, perform the following steps:

Introduction

You can edit the Trigger details of a particular Trigger that is already created.

Procedure

To edit the Trigger in Tag Manager, perform the following steps:

The Tag Manager forms the main product in Ingest Labs and comprises the following modules.

Related Topics

Every tag includes a version number on the top-right corner of the screen. Once the tag is published, the version is set to 1. That is Version 1. After subsequent edits and only after publishing the version number keeps updating to the latest version such as version 2, version 3, and so on.

Note: Until the Tag is published, the status displays as Pending Publish. If the Tag is published in staging, the status is updated as Staging. If the Tag is published in production, the status is updated as Production.

Restoring a Tag Version

To restore a specific tag version, follow the steps below:

Ingest Labs includes two environment types to clearly segregate the stages of implementation:

• Staging

• Production

Related Topics

Introduction

A deleted tag can be restored with all its settings using the Restore option.

Procedure

To restore a deleted tag, perform the following steps:

Introduction

You can edit the details of an existing transformer using this option.

Procedure

To edit the Transformer, perform the following steps:

Introduction

You can edit the Provider details of an existing Provider.

Procedure

To edit a Provider, perform the following steps:

Overview

Every Provider includes a version number on the top-right corner of the screen. Once the Provider is published, the Version is set to 1. That is Version 1.

Version Number Location

You can delete a particular alarm.

To delete an alarm in Ingest Labs, perform the following steps:

1. Select the alarm that you want to delete.

2. From the Actions drop-down menu on the top right corner, select Delete.

Introduction

Deleted qualification criteria can be restored using the Restore option.

Procedure

To restore deleted qualification criteria, perform the following steps:

Introduction

You can edit the details of an existing Qualification Criteria using this option.

Procedure

To edit a Qualification Criteria in Tag Manager, perform the following steps:

This documentation portal explains how to ingest, manage, orchestrate, and onboard Ingest Labs on to your website.

• Navigating through UI

• Tag Manager

• Media Data Platform

The Dashboard is the visual representation of data as soon as you log in to the Ingest Labs application. The Dashboard showcases a graph of all the information about tags in a singular view. The Dashboard is available for both Staging and Production environments.

Related Topics

The Dashboard section includes the following topics:

• Dashboard Screen

Introduction

You can delete the newly created dashboard using this option.

Procedure

To delete the dashboard, perform the following steps:

Step 1: Select Delete Dashboard from the newly created dashboard drop-down menu:

Step 2: A confirmatory dialog box appears with the message: Deleting the dashboard will also delete all widgets in it. Would you like to proceed?

Step 3: Click Yes to confirm the deletion.

Step Result: The Dashboard is deleted successfully along with the added widgets.

Introduction

A newly created dashboard can be set as the default dashboard.

Procedure

Follow these steps to set a newly created dashboard as your default dashboard:

Step 1: Select Make Default from the newly created dashboard drop-down menu.

A message pops up confirming, This dashboard has been marked as default.

Step 2: To revert the changes, select Remove as Default.

Note: You must be authorized to perform this action.

Overview

Every Qualification Criteria includes a version number on the top-right corner of the screen. Once the Qualification Criteria is published, the Version is set to 1. That is Version 1.

Version Number Location

After subsequent edits and only after publishing, the version number keeps updating to the latest version such as Version 2, Version 3, and so on.

Versioning Logic

When a new Qualification Criteria is created and published for the first time, it is assigned Version 1. Every time the Qualification Criteria is edited and then published again, the version number is incremented: Example: Version 2, Version 3, and so on.

Note 1: For the default Qualification Criteria, the version is always set to “1” because these are populated from the template. Note 2: Until the Qualification Criteria is published, the status displays Pending Publish. Once the Qualification Criteria is published in the staging or production environment, the status updates accordingly on the Qualification Criteria screen.

The Triggers indicate when a particular tag is to be triggered based on the data inputs. The triggers are associated with different actions and events while performing the tasks. Some of the examples for triggers include Product View, View cart, Add to cart, View price, View item, View Payment, and so on. Also, the Qualification Criteria provides the additional criteria to indicate more specific instances of when the tag must be triggered. While the Triggers are mandatory, Qualification Criteria is optional.

Related Topics

The Triggers section includes the following topics:

Introduction

This document outlines the step-by-step procedure for deleting a particular Data Element.

Procedure

To delete a Data Element in Ingest Labs, perform the following steps:

Step 1: Select the Data Element you want to delete.

Step 2: From the Actions drop-down menu on the top right corner, select Delete.

Step 3: Click Yes on the confirmatory message that appears.

Step result: The Data Element is deleted successfully.

Note 1: You cannot delete a Data Element if there are any dependencies in the tag. Only after deleting the dependent categories, you can delete the Data Element successfully.

Note 2: Even after deleting the dependencies, if you cannot delete the Data Element, then you must Publish the relevant categories first and then perform the delete operation.

Overview

Every Data Element includes a version number on the top right corner of the screen. Once the Data Element is published, the Version is set to 1. That is Version 1.

Version Number Location

After subsequent edits and only after publishing, the version number keeps on updating to the latest version such as Version 2, version 3, and so on.

Versioning Logic

• When a new Data Element is created and published for the first time, it is assigned Version 1.

• Every time the Data Element is edited and then published again, the version number is incremented:

  • Example: Version 2, Version 3, and so on.

Note 1: For the default Data Elements, the version is always set to “1” because these are populated from the template.

Note 2: Until the Data Element is published, the status displays Pending Publish. When the data element change is published in staging or production environment, the status is updated with the corresponding environment in the Data Elements screen.

Introduction

This document provides step-by-step instructions on how to restore a deleted Data Element using the Restore option.

Procedure

To restore a deleted data element, perform the following steps:

Step 1: Navigate to the Data Elements screen to view the deleted Data Element.

Step 2: Select the Data Element you want to delete.

Step 3: In the top right corner, click the Action dropdown, then select Restore.

Step 3: A restore confirmation dialog box appears. Click Yes to proceed.

Step Result: The Data Element is restored successfully.

The Transformers or the transformation functions are the main building blocks of data while implementing tags. The data layer value may return an object and needs to convert it into a variety of other formats to be used within tags or provider attributes.

The standard approach is to create multiple Data elements and format the value each time while creating other Tag Managers. This results in the same data being redefined in various occurrences. However, if the source data changes, then you must update all the instances where it is being read and transformed to different formats.

A transformation function can accept any number of data elements as inputs, format the data, and return it in a different format as required for a dynamic template parameter.

Related Topics

The Transformers section includes the following topics:

Tags are a collection of data elements, providers, qualification criteria, and privacy settings. Tags are used to build simplified data points and analyze and monitor the data in real-time to ease the marketing processes. You can use the code snippet or MediaPixel to configure the data, send data to providers, and simplify the marketing processes. The two types of Tag Management Solutions are Server-side Tagging solution and Browser/Client-side Tagging solution.

Server-side Tagging

In Server-side Tagging, the events are sent to Ingest Labs and based on the events and configuration of tags, the respective tags are triggered. Server-side tagging includes the marketing needs of the server-side ecosystem. You can collect the data in a first-party consented manner for better control over data collection and transfer the high-performance tag management and streaming to the customer. All integrations are performed using MagicPixel UI platform.

Client-side Tagging

In Client-side tagging, events are not sent to the server and all tasks are performed on the client directly. The tags are triggered on the browser or client website and not sent to the server. Ingest Labs collects the tag information and reports triggered through the SDK on the client website. However, the actual tags are triggered on the client.

Related Topics

The Tags section includes the following topics:

Introduction

You can change the Dashboard and revert to the Default dashboard.

Procedure

Step 1: From the Default Dashboard dropdown menu, select the Change Dashboard option.

Step 2: Click the Project's Default Dashboard option on the Dashboard screen.

Step Result: The default dashboard appears on the screen.

Step 3: While viewing the Default Dashboard, you can select and navigate to the specific Dashboard to display.

Overview

Every Transformer includes a version number on the top-right corner of the screen. Once the Transformer is published, the version is set to 1 — that is Version 1.

Version Number Location

After subsequent edits and only after publishing, the version number keeps updating to the latest version, such as Version 2, Version 3, and so on.

Versioning Logic

When a new Transformer is created and published for the first time, it is assigned Version 1. Every time the Transformer is edited and then published again, the version number is incremented: Example: Version 2, Version 3, and so on.

Note 1: For default Transformers, the version is always set to “1” because these are populated from the template. Note 2: Until the Transformer is published, the status displays Pending Publish. Once the Transformer is published in the staging or production environment, the status updates accordingly on the Transformer screen.

Information

Before publishing a tag in the Production environment, the tag must be published in the Staging environment.

Production

To publish a tag from the Staging to the Production environment, perform the following steps:

Step 1: Select Publish from the left navigation panel.

Step 2: Click the Production tab to view all the tags in the Production environment.

Step 3: Click Publish to Production.

Step Result: The list of Tags, Providers, Transformers, and Triggers appears on the screen.

Step 4: Select the list items that are to be published to production and click Review.

Step 5: In the Name field, enter the name, and in the Description field, enter the description.

Step 6: Click Publish to Production on the top-right of the screen.

Step 7: Click the refresh icon on the top right to change the status from Publish to Staging->Queued->Finished->Published.

Step Result: The relevant tags are published to Production. The tag will be successfully moved from the Staging environment to the Production environment.

Introduction

This document describes the Environment screen UI elements.

Procedure

Step 1: From the left navigation panel, click Environment.

Step 2: Overview of Environment Screen Options.

Introduction

This document provides step-by-step instructions for deleting a Qualification Criteria.

Procedure

Step 1: Select the Qualification Criteria that you want to delete.

Step 2: From the Actions drop-down menu on the top right corner, select Delete.

Step 3: Click Yes on the confirmatory message that appears.

Step Result: The Qualification Criteria is deleted successfully.

Note: You cannot delete a Qualification Criteria if there are any dependencies in the tag. Only after deleting the dependent categories, you can delete the Qualification Criteria successfully. Even after deleting the dependencies, if you cannot delete the Qualification Criteria, then you must Publish the relevant categories first and then perform the delete operation.

Data Elements are the core components you define while creating the tags. Data elements act as components that intelligently fetch information from across your digital property. You can create any number of custom Data elements for a particular Data type and define the elements in the tags as per client requirements. Some of the Data types include Server Header, Server Cookie, Magic Pixel Data Layer, URL Parameter, Custom JavaScript, Custom event, and so on.

Related Topics

The Data Elements section includes the following topics:

• Data Elements Screen

Introduction

This document explains step by step how to add Triggers to the browser side. All the information required for Client-side or Browser-side configuratin.

on is fetched from the webpage or browser.

Procedure

To add a new Trigger, perform the following steps:

Step 1: From the left navigation panel, select Triggers.

Step 2: On the top-right corner of the screen, click the Add Trigger dropdown, then select For Browser.

Step 3: Under the Info section, locate the Name field and enter the appropriate name.

Step 4: Under the Event section, click on Data Element. The Select Data Element panel opens on the right side of the screen. You can use the search bar to find a specific Data Element or browse through the list.

Step 5: Record Trigger

Under the Record Trigger section, select the Enable checkbox. Once enabled, the Namespace field appears. Enter the appropriate namespace in the Namespace field.

Step 6: Once all the required fields are filled, click Save to apply the changes.

Introduction

This section explains how to edit the status of a provider under the Data Governance module.

Procedure

To edit the status of the provider under Data Governance, perform the following steps:

Step 1: From the left navigation panel, click the Data Governance drop-down, and then click Provider.

Step 2: Click Edit to modify the provider’s details.

Step 3: From the Status column, open the Allowed drop-down menu and select Blocked to stop data tracking. You can also change the status back to Allowed if you want to enable data tracking again.

Step 4: Click Review to review the changes before you submit the changes.

Step 5: Enter the name in the Name field and a description in the Description field, then click Save. Click Submit to submit the changes.

Step 6: A confirmation message will appear indicating that the provider’s data has been updated successfully.

Step Result: The Provider status is updated in the Data Governance screen as well as in the section.

Alarms are the notifications triggered by specific events or conditions within the Tag Manager of Ingest Labs. Alarm notifications can be set to alert users when a tag expires, or is about to expire, or when there is a sudden anomaly in the tag behavior.

The two types of Alarms are Tag Anomaly Detection Alarm and the Tag Expiration Alarm.

Tag Anomaly Detection Alarm

The tags are typically triggered consistently over time. This regular pattern is monitored using the Bollinger band. However, there could be an anomaly or an abnormal tag behavior with a sudden spike or drop in the tag trigger. You can configure alarms to detect such anomalies in the tag behavior and receive timely notifications.

Tag Expiration Alarm

When configuring a tag within the Tag Manager, you can specify start and end dates for execution. Alarms can be set to notify configured contacts on tag expiry or just before tags expire. By default, if you do not select any criteria or filters while creating a new alarm, the alarm will be triggered for all configured tags within the project.

Additionally, using the Tag Expiry Look Back feature, you can set alarms in advance, specifying the number of days before tag expiration for reminder notifications and the exact time for alarm triggering.

Related Topics

The Alarms section includes the following topics:

The Providers are the key components to be defined before you create tags. Providers include Media providers for implementing the server-side and client-side tags. You can select from the provider templates created and listed by Ingest Labs or add a custom provider template.

Related Topics

The Providers section includes the following topics:

• Providers Screen

Introduction

A deleted transformer can be restored using the Restore option.

Production

To restore a deleted transformer, perform the following steps:

Step 1: Navigate to the Transformers screen to view the deleted transformer.

Step 2: Select the Transformer and click Restore in the Actions drop-down on the top right corner.

Step 3: Click Yes in the Restore confirmatory dialog box that appears.

Step Result: The Transformer is restored successfully.

Introduction

You can disable the details of a particular tag.

Procedure

To disable a tag, perform the following steps:

Step 1: Select the tag that you want to disable.

Step 2: From the Actions drop-down menu on the top right corner, select Disable.

Step Result: The tag is disabled successfully.

Once the Provider status is updated, you can view all the client-side changes. The Data Governance Timeline screen lists all the providers updated from Allowed to Blocked or Blocked to Allowed.

Note: Whenever a provider status is modified from Allowed to Blocked or Blocked to Allowed under Data Governance, the Provider section is also modified with the changes.

You must also ensure to navigate to the Publish section and publish the provider status of the respective provider.

Click the show changes to view the timeline changes:

Introduction

The Report screen provides users with a detailed view of data, allowing them to filter and analyze information based on specific time ranges.

Procedure

You can add a tag using any of the following options:

• Browser: For the conventional method of tagging using the browser.

• Server: For backward compatibility and support to create new tags on the server.

In Ingest Labs, you can create media tags for client-side and server-side seamlessly and quickly using the following steps. For browser-side tagging creation, the conventional method of tagging is applicable.

The following elements are mandatory to add a new tag:

Introduction

You can delete a particular Transformer.

Procedure

To delete a Transformer in Tag Manager, perform the following steps:

Introduction

This document explains step by step how to add Qualification Criteria to the browser side. All the information required for Client-side or Browser-side configuration is provided.

Procedure

Introduction

After creating any elements, you must first publish to the Staging Environment and then in the Production environment.

Procedure

To publish the tag to Staging, perform the following steps:

Data Governance ensures companies follow legal regulations when triggering tags in Tag Manager. Data Governance serves as a controller or approver for these guidelines, which may include government policies like CCPA and GDPR. For example, when a website detects a visitor from a state with privacy laws, it displays a consent banner. This banner informs the user that their information will be tracked after obtaining their consent for further data tracking purposes.

The banner providers are called Consent Managers, with One Trust being a prominent example. Ingest Labs utilizes the consent obtained from these banners to determine whether to trigger media tags. The Privacy Compliance Data element, pr_comp, returns True or False when Ingest Labs executes the provided JavaScript in the Custom JavaScript section. With Ingest Labs, you can seamlessly integrate with any Consent Manager available, as long as it can read consent from the website browser using JavaScript.

The default pr_comp value is set to true. This means that a user’s activities are tracked by default.

Even if a user denies data tracking consent, Ingest Labs has some providers in the ‘allowed’ state, that will still always be allowed. The other providers, however, in the ‘blocked’ state are blocked when a user denies consent.

A client can choose to block or allow providers at any time. Ingest Labs marks such changed providers as 'modified' until the client publishes them manually. After publishing, the provider is successfully modified.

Introduction

You can perform live debugging using the Debug ID on the console.

Procedure

Step 1: Navigate to the particular brand website.

Introduction

A deleted trigger can be restored using the Restore option.

Procedure

To restore the changes, perform the following steps:

Introduction

The Settings option provides you options to configure the settings for a particular project.

Procedure

Step 1: The Settings screen includes the following information:

Introduction

You can enable tag details for a specific tag.

Procedure

To enable a enable tag, perform the following steps:

Introduction

As all the debugging data of the triggered tags are populated in the live debugging page, you can apply filters to view only the events based on a particular field or type or parameter.

Procedure

The Qualification Criteria are similar to Triggers that are performed to trigger the tag for a specific condition. The Ingest Labs triggers the tag when the Qualification Criteria is met for either browser-side tags or server-side tags.

Note: The Qualification Criteria evaluates the conditions to trigger a tag. For a particular tag to trigger, the qualification criteria is optional. However, when the Qualification Criteria is provided along with the Triggers, then the conditions for Triggers and Qualification Criteria must return true. Only then the tag gets triggered.

Also, if the Qualification Criteria is not defined, the tag is triggered only when the triggers are invoked.

Related Topics

Introduction

Live Debugging is performed either in Staging environment or in the Production environment.

Procedure

To perform Live Debugging on Ingest Labs:

Introduction

The dashboard details of the newly created dashboard can be edited.

Procedure

To edit the Dashboard details, perform the following steps:

Overview

Every Trigger includes a version number displayed in the top-right corner of the screen. Once the Trigger is published, the version is set to 1 — that is Version 1.

Version Number Location

Introduction

Add a New Project is the first step in the entire Tag Management process soon after you launch the Ingest Labs application.

Procedure

To add a new Project, perform the following steps:

Step 1: On the dashboard, in the Easily access your products section, locate Tag Manager, and then click Launch.

Step 2: On the Project screen, in the top-right corner, click Add Project.

Step 3: On the New Project screen, in the Name field, enter an appropriate name.

Step 4: In the Description field, enter a relevant description.

• Note: The Name and Description fields are mandatory. If not provided, an error message This value is required. appears below the respective fields.

Step 5: Under Project Type, select an option based on your project:

• Website: Select this option if the project is website-based.

• Mobile App: Select this option if the project is a mobile application.

Step 6: If you select Website, the Demand-Side Platform (DSP) section appears.

Note: By default, Website is selected.

Step 6.1: Check the Enable DSP integration checkbox.

DSP Integration: DSP integration is the process of connecting a Demand-Side Platform (DSP) with other systems to deliver targeted ads efficiently by using customer data, campaign insights, and inventory sources.

Step 6.2: In the Select Provider drop-down, select the appropriate provider.

Note: DSP integration is enabled only if required by the client.

Step 7: If you select Mobile App, the Select Mobile App Platform section appears.

Step 7.1: In the Select Mobile App Platform drop-down, select the appropriate platform:

• Native – Select this option if the app is developed using native programming languages such as Swift (for iOS) or Kotlin/Java (for Android).

• React Native – Select this option if the app is built using React Native, a cross-platform framework that allows you to develop apps for both iOS and Android using JavaScript and React.

• Ionic – Select this option if the app is built using Ionic, a framework that enables the development of hybrid mobile applications using web technologies like HTML, CSS, and JavaScript.

Step 8: Click Create Project.

Result: This creates the project successfully and adds it to the project list.

Introduction

This document explains step by step how to add Qualification Criteria to the server side. All the information required for Client-side or Server-side configuration is provided.

Procedure

Step 1: From the left navigation panel, select Qualification Criteria.

Step 2: Click the Add Qualification Criteria dropdown and select For Server.

Step 3: Under Info, enter the Qualification Criteria Name in the Name field.

Step 4: Under Data Element, click Add Data Element.

The Select Data Element panel opens on the right side. Choose from the User Defined or Default tabs or use the search bar to find a Data Element.

Step 5: Under the Include these values section, click Add Value and enter the value you want to include. Then, click the plus symbol.

Step 5.1:

• Case Sensitive: This option indicates if the value entered is Case sensitive to further trigger the tag.

• Exact Match: This option indicates if the value matches exactly to trigger the tag.

Step 6: Under Exclude these values, type the value you want to remove, then click the plus icon to exclude it.

Step 6.1:

• Case Sensitive: This option indicates if the value entered is Case sensitive to further trigger the tag. • Exact Match: This option indicates if the value exactly matches to trigger the tag.

Step 7: Click Save on the top right to save the Qualification Criteria details.

Introduction

A Consent Provider collects, stores, and manages users’ permission for data collection and use.

Procedure

Step 1: Under the Data Governance drop-down, click Consent Providers.

Step 2: Click on Add Consent Provider.

Step 3: The Consent Provider panel opens from the right side. In the Name field, enter the appropriate name. In the Description field, provide a proper description.

Step 4: Click Consent Template. The Select Consent Template panel opens. Choose a template from the drop-down list or use the search bar to find and select the required template.

Step 5: The selected Consent Template is displayed under the Consent Template field. Click Save.

Step 6: The created Consent Provider is displayed on the screen with the following details:

• Name – The name of the Consent Provider.

• Template – The Consent Template associated with the provider.

• Status – Indicates the current state of the provider.

• Updated By – The user who last updated the provider.

The Publish option provides an overview of all the tags that are present on the Ingest Labs application. Any tag that is created in Ingest Labs includes the following stages:

• Pending Publish: A newly created tag appears with a "Pending Publish" status in orange color.

• Staging: Before any tag can be published to "Production" it has to be first published to "Staging". Once published to staging, it displays as staging in green.

• Production: In the Publish Project to Production screen, review the tags, providers, triggers, and transformers that are ready for production. You can now publish the tag to "Production". Once you publish the tag in production, it displays production in green.

The stages are displayed on the Tags UI screen:

Note: A disabled tag is displayed in grey background.

Related Topics

The Publish section includes the following topics:

Introduction

This section describes the Data Elements UI screen options.

Add Data Element

Introduction

This section outlines the steps to add a new filter to the Reports screen.

Procedure

Follow the steps below to add and apply a filter:

The Dashboard screen includes the following details:

Introduction

This section describes the Triggers screen UI elements.

Procedures

Introduction

This document explains step by step how to add Transformers to the server side. All the information required for client-side or server-side configuration is provided.

Procedure

Introduction

To view the Production Environment, select the Production option on the Environments screen.

Procedure

Under the

Introduction

This document explains step by step how to add Transformers to the browser side. All the information required for client-side or browser-side configuration is provided.

Procedure

Introduction

You can create a new Tag Anomaly Detection Alarm to monitor unusual tag activity.

Procedure

To add a new Tag Anomaly Detection Alarm, perform the following steps:

Introduction

The Funnel Monitoring Alarm is a new alarm added to Tag Manager that provides real-time alerts for specific notifications within your funnels.

Procedure

Introduction

This document describes the Publish screen UI elements.

The Publish Timeline screen is categorized into two environments:

• Staging

Introduction

The Alarms screen displays information related to alarms in the system. It helps users view, track, and manage alarms easily.

Procedure

Introduction

You can edit the details of a particular alarm.

Procedure

To edit an alarm in Ingest Labs, perform the following steps:

Introduction

You can delete a particular alarm.

Procedure

To delete an alarm in Ingest Labs, perform the following steps:

Introduction

To view the Staging Environment, select the Staging option on the Environments screen.

Procedure

Under the Name field, click Staging.

Info

The Info section includes the following information.

• Name: Displays Staging, indicating the environment type.

• Description: Displays Staging Environment, which gives more details about the selected environment.

SDK Settings

Click Edit.

Event Type

Denotes the specific event that will be used to trigger the tag.

Event Trigger

Specifies the condition that activates the tag. You can choose from the following options:

• On Page Interactive – Triggers the tag when the page becomes interactive (for example, when the DOM is fully parsed and ready for user interaction).

• On Page Loaded – Triggers the tag as soon as the page is loaded.

• Custom Page Event – Allows you to define a custom event that triggers the tag.

Secondary Trigger (JavaScript Variable)

Select this checkbox to enable a secondary trigger.

Once enabled, two additional fields appear:

• Variable Name – Specify the JavaScript variable that acts as the secondary trigger.

• Wait Time – Enter the in milliseconds that the system should wait before triggering the secondary action.

Cookie Domain

Determines how the cookie domain is set. Two options are available:

• Auto – The cookie domain is automatically detected at runtime.

• Manual – Allows you to manually specify the cookie domain.

Note: The cookie domain is automatically detected at runtime, so you don’t need to configure it manually.

Enable Error Logging

Provides options to capture and report SDK errors on the client side.

• Report Client-side SDK Errors – Select this checkbox to allow the Client SDK to report errors and exceptions to the Ingest Labs servers.

• Enable Logging for Client-side SDK – Select this checkbox to capture and log client-side SDK activities locally for troubleshooting.

Trigger Delay

With Trigger Delay, you can set how long, in milliseconds, the system should wait after the page loads before firing the tag.

Note: Allows the page to render its content before the Tag Manager is fired, ensuring that all necessary elements are available.

Content Security Policy

This allows the client to add an additional CSP field so we can use the same csp field to add scripts to the website - Else, it will fail. Select this check box to enable or disable this option. If Enabled, the following option is available.

• Meta tag attribute name for Nonce: The Attribute name in meta tag where the Nonce value is configured in the website.

SDK Setup

To set up Ingest Labs SDK, you must include the following script tag in index.html file of the website. Once the script is executed, the SDK is installed on the client website.

The following is the SDK URL that you must embed in the Staging environment of the client website. The first party domain is mp.ingestlabs.com and the Project ID in the sdk url is MPcl02kskp1eha030nh7hnn. In the IDL Setup, the idl.js file is Identity Link or First party identity script file. The following is the IDL setup url that you must embed in the Staging environment of the client website:

Approved Domains and Collector URLs

The Approved Domains has the list of domains on which the SDK will run. The SDK will execute only these listed domains. This is to avoid spamming and to ensure that the SDK of one site is not used on another site.

The Script sdk url changes when the domain is verified based on the data collector configuration. This decides which collector url to pick based on what domain. Collector url is the url to which Server Side Tags and report calls are sent.

The Approved Domains & Collector URLs display the following information:

• Domain – Enter your website domain in this field.

• Collector URL – This displays the URL where the collected data is sent.

Approved Data Collection Domains – This section lists the domains that are authorized to collect data.

Introduction

This option allows users to create a new Tag Expiration Alarm. It helps monitor tags and notifies users when a tag is about to expire, enabling timely action.

Procedure

To add a new alarm, perform the following steps:

Step 1: Select Alarms from the left navigation panel.

Step 2: Click Add Alarm on the top-right corner of the screen.

Step 3: Select Tag Expiration Alarm.

Step Result: The New Tag Expiration Alarm screen appears.

Step 4: Enter the following details in the New Tag Expiration Alarm screen.

Step 5: In the Name field, enter the alarm name. In the Description field, enter the alarm description.

Step 6: In the Metadata Filters, select a key.

Step 7: Under the Enter Value field, enter the corresponding value.

Step 8: The entered values will appear under Selected Values.

Step 9: To clear the selected values, click Clear.

Step 10: To delete an entry entirely, click Delete.

Note: You can add multiple filters by clicking Add.

Settings

Step 11: Enter the details mentioned in the Settings section.

a. Tag Expiry Lookback (in Days): Send tag expiration notification before the tag expires. You can choose five durations during which the alert should be sent. The number of days must be between 1-180.

b. Report Time: Select the time to trigger the tag expiration alarm. The timezone is set according to the user time zone.

Destination.

Step 12: Select Notification Group: The tag expiration alert is sent to the contacts configured in the selected notification group. In this step, you can select the check boxes or search for a particular group.

Step 13: Provide Email ID: Enter the e-mail IDs to send the tag anomaly notification. You can add users using the Add Users tab.

Note: You can select Notification Groups, Email IDs, or both, based on where you want to send the alerts.

Step 14: Click Save to save the settings.

Step 15: A message appears confirming that the alarm was added successfully.

Introduction

This section describes the Transformers UI screen elements.

Procedure

Transformers (25 of 25)

This option indicates the number of Transformers currently displayed out of the total available Transformers.

Adjust Transformers View Per Page

This option indicates the number of Transformers currently displayed out of the total available Transformers. You can adjust the number of Transformers displayed per page using the dropdown menu located at the top-right corner of the screen.

• 50 per page: Displays up to 50 Transformers on the current page.

• 100 per page: Displays up to 100 Transformers on the current page.

• 200 per page: Displays up to 200 Transformers on the current page.

Add Transformers

Click the Transformers dropdown. You will see two options: For Server and For Browser. Select the required option.

Filter Transformers

The Filter Transformers option is based on the following types:

• Filter By Name: Filters the Transformers based on the trigger name.

• Filter By Attribute Value: Filters the Transformers based on Attribute Value.

• Filter By Metadata Attribute: Filters the Transformers based on Metadata Attribute.

Click the Refresh.

A Fetching Data Elements… message appears while the system retrieves and displays the updated data.

The following are the additional fields that appear on the Transformers screen.

Procedure

Perform the following steps to create widgets in the Dashboard:

Before you begin

Before adding a widget, ensure that a new dashboard is created. Follow the steps in

Introduction

This document provides an overview of the Qualification Criteria UI screen elements.

Procedure

The Media Data Platform (MDP) Dashboard visually represents the customer data when you log in to the MDP. It displays the conversion data using customizable dimensions and metrics. Conversion refers to the conversion of a prospective customer into an actual customer. Ingest Labs creates a default dashboard for the new MDP users soon after the users are onboarded.

Related Topics: