Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Tag Manager forms the main product in Ingest Labs and comprises the following modules.
This documentation portal explains how to ingest, manage, orchestrate, and onboard Ingest Labs on to your website.
When you select a Project, the default Dashboard opens automatically. However, if you want to create a new Dashboard, follow these steps.
Step 1: From the Default Dashboard drop-down menu, click New Dashboard.
Step Result: The New Dashboard screen appears.
Step 2: Enter the Name and Description in the relevant fields.
Note: Ensure that the number of characters in the name field is five or more. Else the following message appears: Name must be longer than or equal to 5 characters.
Step 3: Click Save to save the changes.
Step Result: The new Dashboard is added successfully.
Note: You cannot edit the Default Dashboard as the project is configured with the default settings.
Please rate this document to help us improve the content
A newly created dashboard can be set as the default dashboard.
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.
Please rate this document to help us improve the content
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.
The Dashboard section includes the following topics:
Perform the following steps to create widgets in the Dashboard:
Before adding a widget, ensure that a new dashboard is created. Follow the steps in Create a New Dashboard to create a dashboard. Once the dashboard is created, the New Widget option becomes available.
Step 1: Click Add Widgets.
Step 2: The following visualization types are available:
Line Chart: Displays data trends over time by connecting individual data points with a line.
Tags Fired Counter: Counts and displays the number of times specific tags have been triggered.
Pie Chart: Represents data proportions as slices of a circular chart, showing relative sizes.
Select the appropriate chart type.
Step 3: Under the Select Aggregation Attribute section, click the Select Attribute dropdown. The following options will be displayed:
Browser
Device Type
Language
Tag Fire Status
Step 4: Click Add Filter and select the various criteria to filter information.
Note: This step is optional and can be skipped if no filtering is needed.
Step 5: Click the Operator dropdown.
The following options will be available:
Is one of: Select this operator to filter data where the field matches any of the values in the specified list.
Is not one of: Select this operator to filter data where the field does not match any of the values in the specified list.
Step 6: When you select the Operator , a tab opens below. Click the arrow in the tab to select the filter for a specific field type.
Step 7: Click Add Filter to add the filter conditions.
Step 8: Enter the Widget Name and Description under the Widget Info section and click Save.
Step Result: The new widget is added successfully.
The Dashboard screen displays the required filtered information for a default period of 24 hours. You can also specify a time range to display the information for a specific period and click Refresh.
Note: You can perform the same steps as explained in this procedure for the Tags Fired Counter and Pie Chart.
Browser
Select this option to display information regarding the Browser types such as Chrome, Safari, Edge, IE, Firefox, Opera, and Other.
Device Type
Select this option to display the device type such as Desktop Web, Mobile Web, Tablet, and Other.
Language
Select this option to set the preferred language. The available languages are English, Spanish, and Other.
Tag Fire Status
Select this option to set to one of the Tag trigger Statuses.
• Success (200)
• Success (202)
• Provider Side Failure (400)
• Provider Side Failure (404)
• Provider Side Failure (500)
• Tag Validation Failure (900)
• Tag Validation Failure (1000)
• Error (1001)
• Privacy Blocked (1002)
• Skipped (1003)
• Success with Warnings (1004)
• Scheduled for retry (1005)
• Maximum retry attempts reached (1006)
• Delayed (1007)
Tag
Specifies the tag that needs to be filtered.
Page Name
Specifies the Page Name. Select either contains or is from the Operator drop-down menu.
Provider
Specifies the Provider that needs to be filtered.
Device Type
Select this option to display the device type such as Desktop Web, Mobile Web, Tablet, and Other.
Browser
Select this option to display information regarding the Browser types such as Chrome, Safari, Edge, IE, Firefox, Opera, and Other.
Language
Select this option to set the preferred language.
Domain
Select the appropriate domain name. Select either contains or is from the Operator drop-down menu.
Status
Select this option to set to one of the Tag trigger Statuses. • Success (200) • Success (202) • Provider Side Failure (400) • Provider Side Failure (404) • Provider Side Failure (500) • Tag Validation Failure (900) • Tag Validation Failure (1000) • Error (1001) • Privacy Blocked (1002) • Skipped (1003) • Success with Warnings (1004) • Scheduled for retry (1005) • Maximum retry attempts reached (1006) • Delayed (1007)
Please rate this document to help us improve the content
Add a New Project is the first step in the entire Tag Management process soon after you launch the Ingest Labs application.
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.
This section explains the different tabs available on the Ingest Labs UI screen.
Click the User Icon to edit the profile or log out of the application.
The Products section includes the list of products available for a particular Ingest Labs project.
A Notification Group allows you to add multiple email addresses to receive alerts for alarms and product updates. Notifications are set at the client level, ensuring that only the relevant people receive alerts at the right time.
The Info section displays the information related to the product.
The Users section displays the number of users accessing the Ingest Labs product and the roles allocated for a particular user.
To add a new user, perform the following steps:
Click Users.
Click Add User on the top-right corner of the screen.
Enter the e-mail in the E-mail field.
Enter the Full Name in the Full Name field.
Enter the Last name in the Last Name field.
Note: Provide email ID, first name and last name to add a user. If any field is left blank, the screen displays a warning.
Step Result: Once you add a user, the user receives an e-mail notification to activate the account.
Note: If the user cannot activate and reset the password, the admin may select the Re-invite User option to trigger the e-mail notification again.
You can delete a user using the delete icon to the right of the user.
To delete a user, perform the following steps:
Navigate to Users section.
Select the user and click the three dots to the right of the user.
Click Delete.
Click Yes on the confirmatory message.
You will receive a success message after the user is deleted.
Delete the user cache using the clear cache option to the right of the user. User roles are cached for a short duration on the backend server to facilitate Role-Based Access Control (RBAC). When a user's role changes, delete the user's roles and permissions from the cache using the Clear Cache feature. This ensures that the updated roles and permissions take effect immediately.
To clear the cache of a particular user, perform the following steps:
Navigate to Users section.
Select the user and click the three dots to the right of the user.
Click Clear Cache.
The Roles section displays the multiple roles assigned to the particular user.
Following are the steps to assign the roles to the user:
Using Users Section
Navigate to the Users section on the top.
Select the respective user and click Edit.
Select the roles for the user from the drop-down list.
Click Save.
Note: You will receive an e-mail notification for any edits or modifications.
Using the Roles Section
Navigate to the Roles section on the top.
Select the role to edit.
Under the List of Users associated with this role, enter the user's e-mail ID.
You can delete the roles using the Delete icon at the right-hand corner of the screen.
To delete the roles in the User section, perform the following steps:
Navigate to Users section.
Select the user and click Edit on the top right corner of the screen.
You must clear the roles of a particular user and click Save.
The Usage option includes the real-time metrics and the data collected based on the number of days. By default, the data for the last seven days appears. However, you can modify the number of days to view the metrics for a particular category.
To view the usage details, select Product -> Project -> Category.
Note: The Projects option is available only in Tag Manager. By default, All Projects is selected under Products tab.
If there is no data available, then the following message appears: “Metrics data is currently unavailable.”
The following are the default user options:
Tag Manager
In Tag Manager, SDK enables the client website to trigger API calls to Ingest Labs. In the Usage option, the Tag Manager includes metrics that are collected in real-time during the server-side API calls.
All Projects
Select a specific project to collect the metrics using the All Projects drop-down.
All Categories
Includes the following categories to collect the metrics: • Collector API Calls • Server-Side Tag Count • Server-Side Tag API Calls • Collector Bot Traffic
You can view the following details with the usage in each category:
Collector API Calls
Denotes the number of Collector API calls from the website to Ingest Labs servers.
Server-Side Tag Count
Denotes the number of Server-side tags triggered from Ingest Labs servers.
Server-Side Tag API Calls
Denotes the number of Server-side API calls from the website to Ingest Labs servers.
Collector Bot Traffic
Denotes the number of API calls that Ingest Labs servers detect as bot traffic.
The same categories are listed under the All Categories drop-down for a detailed view of the metrics. For example, to view the Collector API calls from the previous week, click Collector API Calls from the All Categories drop-down and select Last One Week. To view the graphical representation for the last month, select Last One Month and click Refresh.
The Notifications option displays the notifications triggered for a particular user. You can add any number of e-mail IDs for a Notification Group. The Notifications are triggered at the client level for alarms and other products.
Note: While creating alarms, you can set a notification group e-mail for each alarm. The two types of alarms that are triggered under Tag Manager are: • Tag Anomaly Detection Alarm • Tag Expiration Alarm
To add a new notification group, perform the following steps:
Click Add Notification Group on the top-right corner of the screen.
In the Info screen, add the Name in the Name field.
Enter the Description.
Enter the e-mail ID in the Add New User field under the Destinations section.
Click Save.
Step Result: The new notification is added.
The Integrations section describes the third-party integrations using the Authorization token. You can set the token expiry to 1 hour, 12 hours, and 72 hours accordingly.
You can change the Dashboard and revert to the Default dashboard.
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.
After signing in, the landing page appears, displaying the Vendor Name at the top and the Username along with the Email ID of the signed-in customer at the bottom left.
Please rate this document to help us improve the content
You can delete the newly created dashboard using this option.
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.
Please rate this document to help us improve the content
The dashboard details of the newly created dashboard can be edited.
To edit the Dashboard details, perform the following steps:
Step 1: Select Edit Dashboard from the newly created dashboard drop-down menu.
Step 2: Edit the details in the Update Dashboard.
Step 3: Click Save.
Step Result: The dashboard details are updated.
Please rate this document to help us improve the content
A dashboard can be shared with multiple users, and existing users can also be removed from a shared dashboard as needed.
Perform the following steps to share the Dashboard with other users:
Step 1: Select the Share Dashboard option from the newly created dashboard option.
Step 2: Enter the e-mail ID in the Add New User field and click Add User.
Note: A notification is triggered to the users about the dashboard details.
Perform the following steps to stop sharing a Dashboard with a user:
Step 1: Select the Share Dashboard option from the dashboard screen.
Step 2: Click the Delete icon against the user's e-mail ID to delete the user from the shared dashboard.
Step Result: The user details are successfully saved.
Please rate this document to help us improve the content
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.
The Reports 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.
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.
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.
The Tags section includes the following topics:
The Dashboard screen includes the following details:
Total Tag Fires
The total number of tags triggered during a particular duration.
Successful Tag Fires
The number of tags that the Media Provider successfully receives.
Provider Side Tag Failures
The tags that failed validation at the Media Provider.
Tag Validation Failures
The tags that failed mandatory attributes validation.
Privacy Blocked Tags
Tags that are blocked due to privacy consent from the users.
Tag Errors
Indicates the unknown tag errors.
Success with Validation Failures
The number of tags that are successfully triggered but have missing values.
Tag Distribution - Browsers
The number of successful tags across different browsers.
Tag Distribution - Devices
The number of tags across different devices.
Tag Contribution - Browsers
The browser composition of tags across the website.
Tag Contribution - Devices
The device composition of tags across the website.
By default, the Dashboard is set to an hourly session and displays the Default Dashboard. To apply the selected time range and update the dashboard data, click the Refresh button.
Custom Time Range
In the Custom Range section, you can select from the following predefined options in the dropdown menu:
Today so far – Displays data from the start of the current day up to the present time.
Last 3 hours – Shows data for the most recent 3-hour window.
Last 6 hours – Displays data collected over the past 6 hours.
Last 24 hours – Provides data for the past 24-hour period.
Last 7 days – Retrieves data from the past 7 days, including the current day.
Last 1 month – Displays data for the previous month from the current date.
Additionally, you can manually define a start date and end date to filter the dashboard data based on your requirements.
Note: Ingest Labs retains the Dashboard data for a maximum period of 24 months. After 24 months, the data is deleted. To view the Dashboard for a specific custom range, select the time range from the ~ 24 hours ago option and click Refresh.
Click the Refresh button to update the dashboard with the latest data.
Click the dropdown to switch the Dashboard display between the Staging and Production environments.
The Report screen provides users with a detailed view of data, allowing them to filter and analyze information based on specific time ranges.
Accessing the Reports
Navigate to the left navigation panel.
Click on Reports to open the Report screen.
Understanding Report Columns
Tag Column: Displays the Tag name.
Tag Fires Column: Shows the number of times the tag is triggered.
Default Time Range
Reports are generated for a 24-hour period by default.
Filtering Reports by Time Range
To view reports for a specific time range:
Click the dropdown under Custom Range.
Choose one of the available time ranges:
Today so far
Last 3 hours
Last 6 hours
Last 24 hours
Last 7 days
Last month
The report will be displayed based on the selected time range.
Manually Selecting a Time Range
You can manually select a start date and end date to filter the report data according to your requirements.
Refreshing the Report
Each time you modify the time range selection, click the Refresh button to update the report accordingly.
Selecting the Environment
Click the Environment dropdown and choose one of the following:
Production: Redirects to the Production environment.
Staging: Redirects to the Staging environment.
Adjusting Items Displayed per Page
Click the dropdown to select the number of items displayed per page.
The available options are:
20 items per page
50 items per page
100 items per page
Note: Ingest Labs retains the metadata information for a period of 6 months at any given point. For customers who have Enterprise contracts with longer data retention needs, Ingest Labs retains and archives the data as agreed in contracts.
This section describes the Tags screen UI elements.
Filter the tags based on the following types:
Filter By Name: Filters tags based on their names.
Filter By Attribute Value: Filters tags based on their attribute values.
Filter By Metadata Attribute: Filters tags based on their metadata attributes.
All Provider Types: Displays a list of all available provider types.
Image Tags: Displays a list of image-based tags.
JS Tags: Displays a list of JavaScript-based tags.
The Tag Status defines whether a tag is currently active (Enabled) or inactive (Disabled).
Enabled
The tag is active and available for use.
Select Enable from the drop-down menu.
The list of enabled tags is displayed.
Disabled: The tag is inactive and hidden from active use. Instead of deleting a tag when it is not needed, you can disable it and re-enable it later if required.
Select Disable from the drop-down men.
The list of disabled tags is displayed.
The Filter By Providers option filters the tags based on the providers.
Click Filter by Providers.
The Choose Providers panel opens on the right.
Select a provider from the list or use the search bar to find one.
Click Done.
Step Result: All the tags associated with the Provider Name appear on the screen.
The Filter by Qualification Criteria option allows you to filter tags based on a predefined qualification criteria list.
Click on Filter by Qualification Criteria.
The Choose Qualification Criteria dialog box appears on the right side of the screen.
Select the applicable qualification criteria from the list.
Alternatively, enter the name of the criteria in the Filter by Name field to search for a specific criterion.
Click Done to apply the filter.
Step Result: Click a tag. Under Qualification Criteria, the selected qualification criteria are displayed.
The Filter by Data Elements option allows you to filter tags based on predefined Data Elements.
Click on Filter by Data Elements.
The Choose Data Elements dialog box appears.
Select one of the following options:
Default Data Elements
User-Defined Data Elements
(Optional) Enter the name of the Data Element in the Filter by Name field to search for a specific element.
Click Done to apply the filter.
Step Result: All the tags associated with the Data Elements appear on the screen.
The Reset Filters option resets the applied filter settings.
The following are the additional fields that appear on the Tags screen.
Name
Denotes the Tag Name.
Support
Denotes whether the tag is a server-side or a browser-side setting.
Status
Denotes the tag status: • Production: Displays the tags in the production stage. • Staging: Displays the tags in the Staging process. • Pending Publish: Displays the tags yet to be published. • Published: Displays the published tags. • Deleted: Displays the deleted tags.
Provider
Denotes the Provider name and the format. • IMG: Denotes the Provider in the Image format. • JS: Denotes the Provider in the Java Script format.
Validity Period
Denotes the validity period of the tag configured while creating the tag.
Updated By
Specifies the user who updated the tag.
...
The Ellipsis on the last column denotes whether to delete the tag or clone the tag. To delete a tag there must not be any dependencies. Note: You cannot delete a tag if there are any dependencies in the tag for Data Elements, Providers, Triggers, or Qualification Criteria. Only after deleting the dependent categories, you can delete the tag successfully. Even after deleting the dependencies, if you cannot delete the tag, then you must Publish the relevant categories first and then perform the delete operation. The Clone option allows you to clone the tags based on the selection of the already available providers. You can view the same settings for a particular provider and edit the required details and additional information for the new tag.
Perform the following steps to add a new filter and display the reports.
Step 1: From the Reports screen, click Add Filter.
Step 2: Select a field type from the Select a Field drop-down menu based on your requirement.
Step 3: Select an operator from the Operator drop-down menu based on your requirement.
Is one of - This operator allows you to filter reports that match any of the selected values.
Is not one of - This operator excludes the selected values from the results.
Step 4: Select all the applicable field types from the drop-down.
The selected fields are displayed here.
Step 5: Click Add Filter.
To clear the filter, click the small cancel icon in the Add filter category.
Step Result: The Reports for the respective field types appear.
Note: By default, the columns for Tags, Provider, Page Name, and Tag Fires under Reports are mandatory.
Step 6: To modify the settings, click the Settings icon on the top right corner of the screen and select the required columns.
Step 7: Click Submit.
Step Result: The Reports with the selected columns appear on the screen.
Please rate this document to help us improve the content
Tag
Specifies the tag that needs to be filtered.
Page Name
Specifies the Page Name. Select either contains or is from the Operator drop-down menu.
Provider
Specifies the Provider that needs to be filtered.
Device Type
Select this option to display the device type such as Desktop Web, Mobile Web, Tablet, and Other.
Browser
Select this option to display information regarding the Browser types such as Chrome, Safari, Edge, IE, Firefox, Opera, and Other.
Language
Select this option to set the preferred language.
Domain
Select the appropriate domain name. Select either contains or is from the Operator drop-down menu.
Status
Select this option to set to one of the Tag Fire Statuses. • Success (200) • Success (202) • Provider Side Failure (400) • Provider Side Failure (404) • Provider Side Failure (500) • Tag Validation Failure (900) • Tag Validation Failure (1000) • Error (1001) • Privacy Blocked (1002) • Skipped (1003) • Success with Warnings (1004) • Scheduled for retry (1005) • Maximum retry attempts reached (1006) • Delayed (1007)
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.
You can edit the Tag details of a particular tag.
To edit the tag, perform the following steps:
Step 1: Select the tag that you want to edit.
Step 2: From the Actions drop-down menu on the top right corner, select Edit.
Step 3: Edit the tag details and click Save on the top-right to save the changes.
Note: You cannot edit the Provider Attributes values for any tag. You can add new attributes in provider level, and edit the Triggers, Qualification Criteria, Tag Info and Tag Attributes.
Step 1: Click Metadata and click edit
Step 2: Add the Key and the value.
Step 3: Click Add to add more keys and values.
Step 4: Click Save to save the Metadata.
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.
To add a new Tag for browser/client-side, perform the following steps:
Select Tags from the left navigation panel.
Click the Add Tag dropdown in the top right, then select For Browser from the list.
The Select Provider panel opens on the right side. You can choose a provider from the list or use the search bar to find and select a provider.
After selecting a provider, the Tags screen opens.
Select Trigger
In Triggers, click Choose Trigger.
The Choose Triggers panel opens with two tabs:
User-Defined: Displays custom triggers created by users.
Default: Contains predefined system triggers.
Select a trigger from the list or use the search bar to find and select a trigger.
Click Done.
The selected trigger appears on the Triggers screen.
Note: You can remove the selected trigger by clicking the Clear button.
Note: If mandatory details are not filled in, the following warning message gets triggered:
Qualification Criteria (Optional)
The Qualification Criteria are the conditions/triggers that inform Ingest Labs when to trigger a particular tag. You can add multiple Qualification Criteria, and these criteria are layered.
Click Qualification Criteria (Optional).
The Qualification Criteria panel opens on the right side.
Select a qualification criterion from the list or use the search bar to find and select one.
Click Done.
The selected qualification criteria appear on the Qualification Criteria (Optional) screen.
Note: To remove the selected criteria, click the Clear button.
You can set the tag name and validity period. The default validity period is one year for any new tag and can be set to any desired date. To understand tag validity or expiry, see the section Set the Validity period and Tag Expiry.
Name: The Tag name.
Validity Period: Denotes the Tag Validity period including Start Date and End Date.
While creating a tag in Tag Manager, you can set the validity period of a particular tag and define its expiry. The default validity period is one year for any new tag and can be set to any desired date. When the expiry date is close, you will receive a reminder e-mail notification about the tag expiry. If no action is taken, the tag stops triggering post the set validity period.
See ExpirationAlarm for more information.
The Provider is a mandatory setting while adding a new tag. You can add any number of Provider attributes using the Key-Value pair and configure the settings using the Settings option. For a particular Provider attribute, you must set the value either from the Data Elements or Transformers. The user can view the provider attributes added from Provider side configuration.
If you do not set the mandatory values, the following message appears:
After selecting either from the Data Element or Transformer, the value appears in the Value column.
To add Attributes, select Add Attributes and set the following values.
Name: Set the Attribute name. For example: visitor_id, user_id, and so on.
Value: Set the value either for the Data Element or Transformer.
JSON: Enter the Attribute name and value, and configure the Settings.
Mandatory - Denotes the value to be mandatory.
Ignore If Empty - Ignore the field if empty.
Hash (SHA256) - denotes the value in the HASH format.
Static: Denotes the static Value that is known.
Enter the Attribute Settings.
Tool-tip! Select the Mandatory check box to display the Fatal check box.
Set the Data Type Conversion using the following options.
No Conversion
Indicates that there is no conversion required for the data type.
Convert to Boolean
Converts the input data to Boolean.
Convert to Number
Converts the input data to Number.
Convert to Array
Converts the input data to Array.
Convert to Object Spread
Converts the JSON attributes under a parent level attribute to the root level attributes.
Select one of the following Transformer types and click Confirm.
URL encode
Converts the URL in the encrypted format.
HASH (SHA256)
The value is converted to HASH (SHA256) format.
Ignore if empty
May be ignored if the value is empty.
Select the Ignore Redaction checkbox to display the data elements. Redaction is a setting for each data element, which allows the server-side processing to apply the redaction strategy - like anonymize for email.
Step Result: The Provider Attribute is created.
To delete the Provider Attribute, select the Delete icon at the right-hand corner of the screen.
Denote the Script.
The Script denotes the code script if available for the tag. Select the No Script check box if the script is unavailable.
The Tag Attributes are detected from the placeholders in the Script.
The syntax for a placeholder is {{YOURPLACEHOLDERHERE}}
Click Save to save the settings.
Step Result: The new tag is created.
Note: To clone an existing tag, perform the following steps:
Click the three dots to the right of the tag and select clone.
Select a provider.
Denote the Script.
The Script denotes the code script if available for the tag. Select the No Script check box if the script is unavailable.
Click Save.
Step Result: The cloned tag is created.
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:
To enable a disabled tag, perform the following steps:
Step 1: Select the tag that you want to enable from the list of tags.
Step 2: From the Actions drop-down menu on the top right corner, select Enable.
Step Result: The tag is enabled successfully.
A deleted tag can be restored with all its settings using the Restore option.
To restore a deleted tag, perform the following steps:
Step 1: Select the tag.
Step 2: Click the Actions button drop-down and select Restore.
Step 3: Click Yes in the Restore confirmatory dialog box that appears.
Step Result: The tag is restored successfully.
The Provider acts as a template to define the attributes on a high-level, before configuring the tag. You can select any of the available provider templates, set the attributes, save the provider template, and configure the tag. Note: If the default provider templates are unavailable, you can create a custom-defined template using the Providers option on the left navigation panel.
The Data elements refer to the data points that are sent to the Provider to populate the values while configuring the tag.
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 under tags.
The Qualification criteria refer to the rules and conditions required to trigger a tag for a particular scenario. You must set the rules when the tags are to be triggered for different scenarios and send the data to the data endpoints.
This section describes the Data Elements UI screen options.
You can filter the Data Elements based on the following types:
Filter By Name: Filters the tag based on the Tag name.
Filter By Attribute Value: Filters the tag based on the Attribute Value.
Filter By Metadata Attribute: Filters the tag based on the Metadata Attribute.
The following are the additional fields that appear on the Data Elements screen.
Name
Denotes the Data Element Name.
Support
Denotes whether the tag is a server-side or a browser-side setting. • C: Denotes that the Data Element is client-side. • S: Denotes that the Data Element is server-side.
Status
Denotes the status of the Data Element: • Production: The Data Element is in the production stage. • Staging: The Data Element is in the Staging process. • Pending Publish: The Data Element is yet to be Published. • Published: The Data Element is in the Published stage. • Deleted: The Data Element is deleted.
Type
Denotes the type of the Data Element. For example, URL Parameter, Custom Java script, and so on.
Created By
Denotes the user who created the Data Element.
Updated By
Denotes the user who updated the Data Element.
Updated On
Denotes when the Data Element is last updated.
This option indicates the number of DATA elements currently displayed out of the total available DATA elements.
You can adjust the number of DATA elements displayed per page using the dropdown menu located at the top-right corner of the screen.
50 per page: Displays up to 50 DATA elements on the current page.
100 per page: Displays up to 100 DATA elements on the current page.
200 per page: Displays up to 200 DATA elements on the current page.
The Refresh button allows you to reload the DATA elements screen. If you create new DATA elements or update their properties and the changes are not immediately visible on the main UI screen, clicking the Refresh button will reload the page to display the most up-to-date information.
Default DATA Elements Checkbox
Select the Default Data Elements check box at the top to list the readily available default data elements. The specific default template will be used for the particular data elements.
Clearing the checkbox shows all available DATA elements.
For Server-side configuration, all the information is fetched from the server.
Perform the following steps to create the Data elements on browser:
Step 1: Click Add Data Element (For Server) on the top right corner of the screen.
Step 2: Enter the following details in the New Data Element screen that appears. Update the Info section on the top-left corner of the screen.
Step 3: Enter the following fields:
Name
The Default Data Element Name.
Variable Name
Denotes the variable name. Note: The Variable name is same as the Data Element name.
Description
Enter the description of the Data Element.
Choose Data Element Type
Denotes the following data element type: • Server Cookie: • Server Header: • JSON path:
The following screen appears if you select Server Cookie:
Step 4: Enter the Cookie name.
Step 5: Select the Default Value from the drop-down. If the value for a particular data element is unavailable, the default value is used.
Undefined: If the data element is not supposed to be used then select Undefined.
Empty String: Denotes that the data element is a string value.
Null: Denotes the Null data type for the data element.
Custom Value: Denotes the static value for the Data Element.
The following screen appears if you select Server Header:
Select the Default Value from the drop-down. If the value for a particular tag is unavailable, the default value is used.
Undefined: If the data element is not supposed to be used then select Undefined.
Empty String: Denotes that the data element is a string value.
Null: Denotes the Null data type for the data element.
Custom Value: Denotes the static value for the Data Element.
The following screen appears if you select Json Path:
Add the Query Json path.
Select the Default Value from the drop-down. If the value for a particular tag is unavailable, the default value is used.
Undefined: If the data element is not supposed to be used then select Undefined.
Empty String: Denotes that the data element is a string value.
Null: Denotes the Null data type for the data element.
Custom Value: Denotes the static value for the Data Element.
Select the following checkboxes, if required:
Clean: Clears and trims any white spaces on the trailing and leading strings after collecting the data value. Lower-case: Denotes that the string needs to be in lower-case.
Step 6: Select redaction for the data element. It is applicable only for serverside tagging. Basically, when you set up a data element as sensitive, and set up a strategy, the backend server will scramble it while using the data element in a tag or provider.
This data classification setting allows the serverside processing to apply a redaction strategy - like anonymize for email ID, IP address, phone number and so on.
Step 7: Click Save to save the changes.
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.
The Data Elements 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.
The Providers section includes the following topics:
You can delete a particular Data Element.
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: 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.
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.
To add a new server-side tag, perform the following steps:
Step 1: Select Tags from the left navigation panel.
Step 2: Click the Add Tag dropdown select For server.
Step 3: The Select Provider panel opens on the right side. Select a provider from the list or use the search bar to find and select a provider.
Step Result: The New tag screen appears.
Step: 4: Select Trigger.
The Choose Triggers panel opens on the right side. Choose a trigger from the list or use the search bar to find and select a trigger, then click Done.
Step Result: The tag is triggered for the respective trigger data.
Qualification Criteria of a tag are conditions/triggers that inform Ingest Labs when to trigger a particular tag. You can add multiple Qualification Criteria and these criteria are layered.
Click Choose Qualification Criteria.
Note: This step is optional.
Click Choose Qualification Criteria. The Choose Qualification Criteria panel opens on the right side. Select an option from the dropdown or use the search bar to find and select a criterion, then click Done.
This is the step where you set a name and validity period for the tag. The default validity period is one year for any new tag that is created and can be set to any desired date. To understand tag validity or expiry, see the section Set the Validity period and Tag Expiry.
Name: The Tag name.
Validity Period: Denotes the validity period of the tag including Start Date and End Date.
Note: If you don't enter the tag name, an error message appears: This value is required.
While creating a tag on Ingest Labs, you can set the validity period of a particular tag and define tag expiry. The default validity period is one year for any new tag that is created and can be set to any desired date. When the expiry date is closer, you will receive reminder e-mail notification about the expiry of the tag. If no action is taken, the tag stops triggering post the set validity period. You can find all expired tags in the “Paused State” in the Publish section and you can remove the expired tags to reduce the size of your SDK.
The Query parameters include the set of dynamic values that are included along with the Base URL while executing the query. These parameters appear in the Attributes section as well along with the values.
The Provider is a mandatory setting while adding a new tag. You can add any number of Provider attributes using the Key-Value pair and configure the settings using the Settings option. The user can view the providers attributes added from Provider side configuration.
For a particular Provider attribute, you must set the value either from the Data Elements or Transformers.
After selecting either from the Data Element or Transformer, the value appears in the Value column.
Add Attributes
To add Attributes, select Add Attributes and set the following values.
Name: Set the Attribute name. For example: visitor_id, user_id, and so on.
Value: Set the value either for the Data Element or Transformer.
JSON: Enter the Attribute name and value, and configure the Settings.
Mandatory - Denotes the value to be mandatory.
Ignore If Empty - Ignore the field if empty.
Hash (SHA256) - denotes the value in the HASH format.
Static: Denotes the static Value that is known.
Attribute Settings:
Enter the Attribute Settings.
Tool-tip! Select the Mandatory check box to display the Fatal check box.
Set the Data Type Conversion using the following options.
No Conversion
Indicates that there is no conversion required for the data type.
Convert to Boolean
Converts the input data to Boolean.
Convert to Number
Converts the input data to Number.
Convert to Array
Converts the input data to Array.
Convert to Object Spread
Converts the JSON attributes under a parent level attribute to the root level attributes.
Select one the following Transformer types and click Confirm.
URL encode
Converts the URL into the encrypted format.
HASH (SHA256)
The value is converted to HASH (SHA256) format.
Ignore if empty
May be ignored if the value is empty.
Select the Ignore Redaction checkbox to display the data elements. Redaction is a setting for each data element, which allows the server-side processing to apply the redaction strategy - like anonymize for email.
Step Result: The Provider Attribute is created.
To delete the Provider Attribute, select the Delete icon at the right-hand corner of the screen.
To add Tag Attributes, click Add Attribute.
Name: Set the Attribute name. For example: visitor_id, user_id, and so on.
Value: Set the value either for the Data Element or Transformer.
JSON: Enter the Attribute name and value, and configure the Settings.
Mandatory - Denotes the value to be mandatory.
Ignore If Empty - Ignore the field if empty.
Hash (SHA256) - denotes the value in the HASH format.
Static: Denotes the static Value that is known.
Attribute Settings:
Enter the Attribute Settings.
Tool-tip! Select the Mandatory check box to display the Fatal check box.
Set the Data Type Conversion using the following options.
No Conversion
Indicates that there is no conversion required for the data type.
Convert to Boolean
Converts the input data to Boolean.
Convert to Number
Converts the input data to Number.
Convert to Array
Converts the input data to Array.
Convert to Object Spread
Converts the JSON attributes under a parent level attribute to the root level attributes.
Select one of the following Transformer types and click Confirm.
URL encode
Converts the URL into the encrypted format.
HASH (SHA256)
The value is converted to HASH (SHA256) format.
Ignore if empty
May be ignored if the value is empty.
Step Result: The Tag Attribute is created.
Enable Retry Configuration.
Enable Delay Configuration.
Click Save to save the settings.
Step Result: The new tag is created.
To edit the Data Element in Ingest Labs, 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.
For Client-side or Browser-side configuration, all the information is fetched from the webpage or browser. Perform the following steps to create a Data elements for the browser:
Step 1: Click Add Data Element (For Browser) on the top right corner of the screen.
Step 2: Enter the following details in the New Data Element screen that appears. Update the Info section on the top-left corner of the screen.
Name
Denotes the default Data Element Name.
Variable Name
Denotes the variable name. Note: The Variable name is the same as the Data Element name.
Description
Enter the description of the Data Element.
Is a Language Data Element?
The language that must be essentially used in the particular website. There can be only one Language Data Element for a particular Data Element.
Is a Privacy Compliance Data Element?
Denotes if the user or customer has provided consent for data collection. There can be only one Privacy Compliance Data Element for a particular Data Element.
Choose Data Element Type
Denotes the data element type. • URL Parameter: Denotes the parameters that are fetched from the URL. • Launch Data Element: This is a reference to the Adobe Launch data element if the client's website has Adobe launch configured and the Adobe launch SDK downloaded on their website. • Custom JavaScript: Includes the Custom Java Script code that the user provides as input. The code must be included in the Custom Java Script section while adding the Data Elements. • Magic Pixel Data Layer: Includes the Data Layer that the Ingest Labs generates. You can specify the path in the Element Name that is a JSON object and provide values.
Step 3: You can select either the default or custom (user-defined) template.
You must ensure to create the Data Elements in Ingest Labs and then proceed further with the tag updates. The following table depicts the different Data Element types for both Browser-side and Server-side tag elements.
JSON Path
Yes
-
URL Parameter
Yes
Yes
Magic Pixel Data Layer Element
Yes
Yes
Custom Java Script
Yes
Yes
Server Header
Yes
-
Server Cookie
Yes
-
Magic Pixel Internal
Yes
Yes
Magic Pixel Event Timestamp
Yes
Yes
Magic Pixel Event Name
Yes
Yes
Magic Pixel Event ID
Yes
Yes
Magic Pixel Identity
Yes
Yes
URL Parameter
Step 4: Enter the following fields in the URL section of the screen.
Parameter Name
This is a mandatory field. Enter the parameter name.
Default value
Represents the Default Value of the parameter. • Empty String: Denotes that the data element is a string value. • Undefined: If the data element is not supposed to be used then select Undefined. • Null: Denotes the Null data type for the data element. • Custom Value: Denotes the static value for the Data Element.
Case-sensitive
Select the Case-sensitive check box to make the default parameter case-sensitive. Else, clear the check box.
Launch Data Element
Step 5: Enter the following fields in the Launch Data section of the screen.
Element Name
This is a mandatory field. Enter the data element name.
Default value
Represents the Default Value of the data element. • Empty String: Denotes that the data element is a string value. • Undefined: If the data element is not supposed to be used then select Undefined. • Null: Denotes the Null data type for the data element. • Custom Value: Denotes the static value for the Data Element.
Magic Pixel Data Layer
Step 6: Enter the following fields in the Magic Pixel Data Layer section of the screen.
Element Name
This is a mandatory field. Enter the element name of the Magic Pixel data layer.
Default value
Represents the Default Value of the element. • Empty String: Denotes that the data element is a string value. • Undefined: If the data element is not supposed to be used then select Undefined. • Null: Denotes the Null data type for the data element. • Custom Value: Denotes the static value for the Data Element.
Transformation Function
Step 7: Enter the following fields in the Transformation Function section.
Default Functions
• Clean: Clears and trims any white spaces on the trailing and leading strings after collecting the data value. • Lowercase: Denotes that the string needs to be in the lower-case.
Custom Function
Use Custom Function: For performing other transformations, you can write the code, retrieve or convert the value into a new value, and return the new value in the code using Custom function.
Step 8: Select redaction for the data element. Basically, when you set up a data element as sensitive, and set up a strategy, the backend server will scramble it while using the data element in a tag or provider.
This data classification setting allows the serverside processing to apply a redaction strategy - like anonymize for email ID, IP address, phone number and so on.
Step 9: Click Save to save the changes.
This section describes the Providers screen UI elements.
You can filter the Providers based on the following types:
Filter By Name: Filters the providers based on the Provider name.
Filter By Attribute Value: Filters the Providers based on Attribute Value.
Filter By Metadata Attribute: Filters the Providers based on Metadata Attribute.
You can adjust the number of providers displayed per page using the dropdown menu located at the top-right corner of the screen.
50 per page: Displays up to 50 providers on the current page.
100 per page: Displays up to 100 providers on the current page.
200 per page: Displays up to 200 providers on the current page.
The following are the additional fields that appear on the Providers screen.
Name
Denotes the Provider Name.
Support
Denotes whether the Provider is a server-side or a browser-side setting.
Status
Denotes the status of the Provider. • Production: The Provider is in Production status. • Staging: The Provider is in Staging status. • Pending Publish: The Provider is yet to be Published.
Type
Denotes the type of the Provider. For example, IMG, JS, and so on.
Created By
Denotes the user who created the Provider.
Updated By
Denotes the user who updated the Provider.
Updated On
Denotes when the Provider is last updated.
Add Tag
You can create the tag using this option from the Providers.
The All-Provider Types drop-down menu displays the following provider types:
All Provider Types
Image Tags: Providers that use image-based tracking.
JS Tags: Providers that use JavaScript for tracking.
The Filter By Data Elements option filters the Data Elements based on the Data Element selected.
The Reset Filters option resets the applied filters.
Refresh Button The Refresh button allows you to reload the Providers screen. If you create new providers or update their properties and the changes are not immediately visible on the main UI screen, clicking the Refresh button will reload the page to display the most up-to-date information.
Deleted data elements can be restored using the Restore option.
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 and click Restore under the Actions drop-down on the top right corner.
Step 3: Click Yes in the Restore confirmatory dialog box that appears.
Step Result: The Data Element is restored successfully.
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.
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.
Note: For the default Data Elements, the version is always set to “1” because these are populated from the template.
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.
All the information required for Client-side or Browser-side configuration is fetched from the webpage or browser.
To add a new Provider in Tag Manager, perform the following steps:
Step 1: From the left navigation panel, select Providers.
Step 2: Select Add Provider -> For Browser on the top-right corner of the screen.
Step 3: The Provider Template panel opens on the right side and choose a template from the list or use the Search bar to find a specific one.
To add a custom image provider, select Custom Image Provider from the Provider Template box.
You can also select other JS provider templates. Let us take an example of the Facebook JS provider template.
Step 4: Enter the Provider Details such as Provider Name and Description in the New Provider screen.
Step 5: The Script section includes both the Template script and Provider script.
You can enter the JavaScript in the Provider Script section and click Save to save the changes.
Step 6: The Attributes section lists the Attributes for Data Elements and Transformers. This is an Optional section.
Step 7: Select Choose Data Element for Data Element attributes.
Step 8: Select either User-Defined Data Element or Default Data Element.
Step Result: The selected Data Element is visible in the Value section.
Step 9: Select Choose Transformer to Transformer Attributes.
Step Result: The selected Transformer is visible in the Value section.
Step 10: Click cancel on the top right of the page to cancel the settings and view the the list of providers.
Click Save on the top right to save the new Provider (Browser).
Note: The page displays the following success message.
This section describes the Triggers screen UI elements.
Using the Filter Triggers option, you can filter the triggers based on the following types:
Filter By Name: Filters the trigger based on the trigger name. • Filter By Attribute Value: Filters the trigger based on Attribute Value.
• Filter By Metadata Attribute: Filters the trigger based on Metadata Attribute.
This option indicates the number of Triggers currently displayed out of the total available Triggers. You can adjust the number of Triggers displayed per page using the dropdown menu located at the top-right corner of the screen.
50 per page: Displays up to 50 Triggers on the current page.
100 per page: Displays up to 100 Triggers on the current page.
200 per page: Displays up to 200 Triggers on the current page.
The Filter By Data Elements option allows to filter the triggers based on the Data Elements.
You can select either the User-defined Data Element or Default Data Element in the Choose Data Elements screen.
The Reset Filters option resets the filter criteria applied.
Select the Default Triggers check box if you are selecting the default triggers for a particular tag.
The following are the additional fields that appear on the Triggers screen.
You can delete a particular Provider using this option.
To delete a Provider in Ingest Labs, perform the following steps:
Step 1: Select the Provider 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 Provider is deleted successfully.
Note: You cannot delete a provider that includes provider dependencies with the other attributes. Only after deleting the dependent categories, you can delete the Provider successfully.
Even after deleting the dependencies, if you cannot delete the Provider, then you must Publish the relevant categories first and then perform the delete operation.
Name
Denotes the trigger Name.
Support
Denotes whether the trigger is a server-side or a browser-side setting.
Status
Denotes the status of the Trigger. • Production: The Trigger is in Production status. • Staging: The Trigger is in Staging status. • Pending Publish: The Trigger is yet to be published.
Created By
Denotes the user who created the Trigger.
Updated By
Denotes the user who updated the Trigger.
Updated On
Denotes when the Trigger is last updated.
Add Tag
You can create a tag using this option from the Trigger.
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. 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.
Note: For the default Providers, the version is always set to “1” because these are populated from the template. Until the Provider is published, the status displays as Pending Publish. If the Provider is published in staging, the status is updated as Staging. If the Provider is published in production, the status is updated as Production.
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.
The Triggers section includes the following topics:
You can edit the Provider details of an existing Provider.
To edit the Provider in Ingest Labs, perform the following steps:
Step 1: Select the Provider that you want to edit.
Step 2: From the Actions drop-down menu on the top right corner, select Edit.
Step 3: Edit the Provider details and click Save on the top-right to save the changes.
For Client-side or Browser-side configuration, all the information is fetched from the webpage or browser.
To add a new Trigger, perform the following steps:
Step 1: From the left navigation panel, select Triggers.
Step 2: Select Add Trigger -> For Browser on the top-right corner of the screen.
Step 3: Enter the Trigger Name in the Name field in the Info section.
Step 4: Click Data Element to open the Select Data Element panel on the right side of the screen. This panel contains two tabs: User-defined and Default. You can either browse through the list or use the search bar to find a specific Data Element.
Step 5: Record Trigger
When you check the Enable checkbox, the Namespace field appears. Enter the appropriate namespace in this field.
Step 6: Click Save to save the trigger details.
For Server-side configuration, all the information is fetched from the server.
To add a new server-side trigger, perform the following steps:
Step 1: From the left navigation panel, select Triggers.
Step 2: Select Add Trigger -> For Server on the top-right corner of the screen.
Step 3: Enter the Trigger Name in the Name field in the Info section.
Step 4: Click Data Element to open the Select Data Element panel on the right side of the screen. This panel contains two tabs: User-defined and Default. You can either browse through the list or use the search bar to find a specific Data Element.
Step 5: Record Trigger
When you check the Enable checkbox, the Namespace field appears. Enter the appropriate namespace in this field.
Step 6: Click Save to save the trigger details.
For Server-side configuration, all the information is fetched from the server.
To add a new Provider on Ingest Labs, perform the following steps:
Step 1: Select Add Provider -> For Server on the top-right corner of the screen.
Step 2: The Provider Template panel opens on the right side. Select a template from the list or use the Search bar to find a specific one.
Step 3: Let's take an example of the Facebook Conversion API provider template.
Step 4: Ingest Labs configures the Provider Name and Base URL.
Step 5: The values such as the API version and the Pixel Id are specific to every provider. You need the API version, Pixel ID, and Access token before you add a Facebook Conversion API template.
Step 6: To add a Facebook Conversion API Template, perform the following steps:
a. Navigate to the following URL to generate a Pixel Id, and an Access Token for the API version. Generate Pixel Id and Access Token
b. Follow the steps mentioned on the webpage.
Add Attributes The Attributes section consists of the following two sub-sections:
User Data
Custom Data
Step 7: Under the Attributes section, click Add Attribute at the bottom to add a new attribute. The Name, Value, and Settings information is visible.
Note: You can set the attribute to Mandatory, Ignore If Empty, Fatal, Hash (SHA256).
Mandatory: This value is mandatory.
Fatal: This value is mandatory.
Ignore If Empty: This may be ignored if the value is not set.
HASH (SHA256): The value is converted to HASH format.
You can add additional attributes from FacebookCAPIParameters
You can see a list of parameters here:
Step 8: To add a new parameter from the Customer Information Parameters, for example, the subscription Id, perform the following steps:
a. In the JSON section, click Add Attribute.
b. Add the exact field name under User Data and configure it with a data element that returns a subscription Id.
Step 9: To modify the settings, click the Settings icon on the bottom-right corner of the screen.
Step 10: Enter the Attribute Settings and click Confirm to save the changes.
The following are the Data Type Conversions for the attributes.
No Conversion
Indicates that there is no conversion required for the data type.
Convert to Boolean
Converts the input data to Boolean.
Convert to Number
Converts the input data to a number.
Convert to Array
Converts the input data to Array.
Convert to Object Spread
Converts the JSON attributes under a parent level attribute to the root level attributes.
Step 11: To delete the attribute, click the Delete icon.
Step 12: Enter the fields in the HTTP Headers section. This section is optional.
Step 13: Enter the fields in the Connectors section and click Save to save the changes.
Note: Similarly, while adding any other provider template, for example, TikTok Event API Provider, click TikTok Event API Provider to create a Pixel Id and Access Token and proceed as given above.
Every Trigger includes a version number on the top right corner of the screen. Once the Trigger is published, the Version is set to 1. That is Version 1. 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.
Note: For the default Triggers, the version is always set to “1” because these are populated from the template.
Note: Until the Trigger is published, the status displays as Pending Publish. Once the Trigger is Published, the status is updated as Production.
You can edit the Trigger details of a particular Trigger that is already created.
To edit the Trigger in Tag Manager, perform the following steps:
Step 1: Select the Trigger that you want to edit.
Step 2: From the Actions drop-down menu on the top right corner, select Edit.
Step 3: You can edit the details in the Info section and Data Elements section.
Step 4: Click Save on the top right to save the changes.
This section describes the Qualification Criteria UI screen elements.
This option indicates the number of Qualification Criteria currently displayed out of the total available Qualification Criteria. You can adjust the number of Qualification Criteria displayed per page using the dropdown menu located at the top-right corner of the screen.
50 per page: Displays up to 50 Qualification Criteria on the current page.
100 per page: Displays up to 100 Qualification Criteria on the current page.
200 per page: Displays up to 200 Qualification Criteria on the current page.
The Filter Qualification Criteria is based on the following types:
Filter By Name: Filters the Qualification Criteria based on the trigger name.
Filter By Attribute Value: Filters the Qualification Criteria based on Attribute Value.
Filter By Metadata Attribute: Filters the Qualification Criteria based on Metadata Attribute.
The Filter By Data Elements option filters the Qualification Criteria based on the Data Elements.
You can select either the User-defined Data Element or Default Data Element in the Choose Data Elements screen.
The Reset Filters option resets the filter criteria applied.
The following are the additional fields that appear on the Qualification Criteria screen.
Name
Denotes the Qualification Criteria Name.
Support
Denotes whether the Qualification Criteria is a server-side or a browser-side setting.
Status
Denotes the status of the Qualification Criteria. • Production: The Qualification Criteria is in Production status. • Staging: The Qualification Criteria is in Staging status. • Pending Publish: The Qualification Criteria is yet to be Published.
Created By
Denotes the user who created the Qualification Criteria.
Updated By
Denotes the user who updated the Qualification Criteria.
Updated On
Denotes when the Qualification Criteria is last updated.
Add Tag
You can create the tag using this option from the Qualification Criteria.
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.
The Qualification Criteria section includes the following topics:
You can delete a particular Trigger.
To delete a Trigger in Ingest Labs, perform the following steps:
Step 1: Select the Trigger that you want to delete.
Step 2: From the Actions drop-down menu on the top right corner, select Delete.
Note: You cannot delete the default triggers as the option for delete option is unavailable for default triggers.
Step 3: Click Yes on the confirmatory message that appears.
Step Result: The Trigger is deleted successfully.
To monitor and capture events in your triggers, you can enable the recording feature. This will ensure that every event occurring within the triggers is saved and marked as recorded for future reference.
You can enable the recording feature for triggers by following these steps.
Navigate to Tag Manager > Triggers.
Note: You can create Record Triggers for both Server and Browser.
Step 1: Click Add Trigger.
Note: You can create Record Triggers for both Server and Browser.
Step 2: Click for Browser.
Step 3: Under the Info section, click the Name field and enter an appropriate name for your Record Trigger.
Step 4: Under Data Element, click Add Data Element. The Select Data Element panel will open on the right side. You can either search for a particular data element by typing its name in the search bar or select it from the available list.
Step 5: Under the Include these values section, click Add value to include list to give the appropriate value you want to include, and then click the plus symbol.
Step 6: After clicking the plus symbol, two checkboxes will appear:
· Case Sensitive and
· Exact Match
Click both checkboxes to apply these settings.
Note: Under Exclude these values, you can give values to exclude.
Step 7: Under the Record Trigger section, you will find the Enable checkbox. Check the box, and then the Namespace section will appear. Provide the appropriate namespace value.
Step 8: Click Save.
Step 9: Red color indicates that the trigger is actively being recorded.
Note: The same steps apply for server-side triggers.
A deleted trigger can be restored using the Restore option.
To restore the changes, perform the following steps:
Step 1: Navigate to the Triggers screen to view the deleted trigger.
Step 2: Select the Trigger and click Restore under the Actions drop-down on the top-right corner.
Step 3: Click Yes in the Restore Trigger confirmatory dialog box that appears.
Step Result: The Trigger is restored successfully.
You can edit the details of an existing Qualification Criteria using this option.
To edit a Qualification Criteria in Tag Manager, perform the following steps:
Step 1: Select the Qualification Criteria that you want to edit.
Step 2: From the Actions drop-down menu on the top right corner, select Edit.
Step 3: Click Save to save the changes.
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. 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.
Note: Until the Qualification Criteria is published, the status displays as Pending Publish. Once the Qualification Criteria change is published in staging or production environment, the status is updated with the corresponding environment in the Qualification Criteria screen.
For Server-side configuration, all the information is fetched from the server.
To add a new Qualification Criteria in Tag Manager, perform the following steps:
Step 1: From the left navigation panel, select Qualification Criteria.
Step 2: Select Add Qualification Criteria -> For Server on the top-right corner of the screen.
Step 3: Enter the name of the Qualification Criteria in the Name field in the Info section.
Step 4: Select the Data Element from the Data Element section.
Step 5: For each Data Element, the following Criteria is to be met.
Include these values
The list of values entered are included in the Qualification Criteria. You can select the following check boxes: • 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.
Exclude these values
The list of values entered are excluded from the Qualification Criteria. You can select the following check boxes: • 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 6: Click Save on the top right to save the Qualification Criteria details.
You can delete a particular Qualification Criteria.
To delete a Qualification Criteria in Tag Manager, perform the following steps:
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.
Deleted qualification criteria can be restored using the Restore option.
To restore deleted qualification criteria, perform the following steps:
Step 1: Navigate to the Qualification Criteria screen to view the deleted Qualification Criteria.
Step 2: Select the Qualification Criteria you want to restore.
Step 3: Click Restore in the Actions drop-down on the top right corner.
Step 4: Click Yes in the Restore confirmatory dialog box that appears.
Step Result: The Qualification Criteria is restored successfully.
For Client-side or Browser-side configuration, all the information is fetched from the webpage or browser.
To add a new Qualification Criteria in Tag Manager, perform the following steps:
Step 1: From the left navigation panel, select Qualification Criteria.
Step 2: Select Add Qualification Criteria -> For Browser on the top-right corner of the screen.
Step 3: Enter the Qualification Criteria Name in the Name field under Info section.
Step 4: Select the Data Element from the Data Element section.
Step 5: For each Data Element, the following criteria is to be met.
Include these values
The list of values entered are included in the Qualification Criteria. You can select the following check boxes: • 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.
Exclude these values
The list of values entered are excluded from the Qualification Criteria. You can select the following check boxes: • 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 6: Click Save on the top right to save the Qualification Criteria details.
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.
The Transformers section includes the following topics:
This section describes the Transformers UI screen elements.
Filter the Transformers based on the following types:
Filter By Name: Filters the Transformers based on the trigger name.
Filter By MetadataAttribute: Filters the Transformers based on Metadata Attribute.
The following are the additional fields that appear on the Transformers screen.
Name
Denotes the Transformer Name.
Type
Denotes whether the Transformer is a server-side or a browser-side setting.
Status
Denotes the status of the Transformer. • Production: The Transformer is under production. • Staging: The Transformer is in Staging. • Pending Publish: The Transformer is yet to be published.
Created By
Denotes the user who created the Transformer.
Updated By
Denotes the user who updated the Transformer.
Updated On
Denotes when the Transformer is last updated.
For Client-side or Browser-side configuration, all the information is fetched from the webpage or browser.
To add a new Transformer in Tag Manager, perform the following steps:
In the left navigation panel, select Transformers.
Select Add Transformer -> For Browser on the top-right corner of the screen.
Enter the Function Name in the Function Name field in the Info section.
Enter the Description in the Description field.
Click Add Arguments in the Function Arguments section.
Enter the Argument name and select the Data Element in the Value section. Here is an example:
Select the check boxes for Mandatory and URL Encode, if necessary.
To delete the Argument, click the Delete icon on the right-hand corner of the screen.
To access the Argument, enter the code in the Code section. You can also Test the function using the Test Function tab on the right-hand corner of the screen.
Click Save to save the Transformers details.
For Server-side configuration, all the information is fetched from the server.
To add a new Transformer in Tag Manager, perform the following steps:
In the left navigation panel, select Transformers.
Select Add Transformer -> For Server on the top-right corner of the screen.
Enter the Function Name in the Function Name field in the Info section.
Note: The Function name must always start with an alphabet, and can only contain letters, numbers and underscores.
Enter the Description in the Description field.
Click Add Arguments in the Function Arguments section.
Enter the Argument name and select the Data Element in the Value section.
Select the check boxes for Mandatory and URL Encode, if necessary.
To delete the Argument, click the Delete icon on the right-hand corner of the screen.
To access the Argument, enter the code in the Code section. You can also test the function using the Test Function tab on the right-hand corner of the screen.
Click Save to save the Transformer details.
You can edit the details of an existing transformer using this option.
To edit the Transformer in Ingest Labs, perform the following steps:
Select the Transformer that you want to edit.
From the Actions drop-down menu on the top right corner, select Edit.
You can edit the details in the Info, Function Arguments, and Code sections.
Click Save on the top right to save the changes.
You can delete a particular Transformer.
To delete a Transformer in Tag Manager, perform the following steps:
Select the Transformer that you want to delete.
Select Delete from the Actions drop-down menu on the top right corner.
Click Yes on the confirmatory message that appears.
Step Result: The Transformer is deleted successfully.
Note: The following error occurs if there are any dependencies for the transformers in tags.
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.
The Publish section includes the following topics:
A deleted transformer can be restored using the Restore option.
To restore a deleted transformer, perform the following steps:
Navigate to the Transformers screen to view the deleted transfomer.
Select the Transformer and click Restore in the Actions drop-down on the top right corner.
Click Yes in the Restore confirmatory dialog box that appears.
Step Result: The Transformer is restored successfully.
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. 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.
Note: Until the Transformer is published, the status displays as Pending Publish. If the Transformer is published in staging, the status is updated as Staging. If the Transformer is published in production, the status is updated as Production.
The Publish option appears at the bottom of the left navigation panel.
The Publish Timeline screen is categorized into two environments: Staging and Production.
The Staging section displays all the tags that are currently in the staging environment and you can publish any tag into the production environment.
The Production section displays all the tags that are published from staging and are currently in production.
Pending to Publish change is visible on the dashboard in about 4-5 mins for client-side tags after the CDN cache for client SDK is cleared. For server-side tags, it is almost immediate.
After creating a new tag in Ingest Labs, you must first publish the tag to the Staging Environment and then in the Production environment.
To publish the tag to Staging, perform the following steps:
Step 1: Select Publish from the left navigation panel.
Step 2: Click the staging tab to view all the tags in the Staging environment.
Step 3: Click Publish to Staging.
Step Result: The Publish Project to Staging screen appears where all the tags that are ready to be published to staging are listed.
Step 4: Select the tags that you have created and click Review on the top-right corner of the screen.
Step 5: Enter the Publishing Name in the Name field and provide description under the Info section.
Step 6: Review the tags that are selected and click Publish to Staging.
Step 7: Click the refresh icon on the top right to change the status from Publish to Staging->Queued->Finished->Published.
Step Result: The Published tag appears with the Published status.
In Ingest Labs, before publishing a tag in the Production environment, the tag must be published in the Staging environment.
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 Publish Project to Production screen, review the tags, providers, triggers, and transformers that are ready for production.
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.
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.
Note: The Data element pr_comp returns True if the user accepts data tracking.
The Data Governance section includes the following topics:
You can perform live debugging using the Debug ID on the console.
Navigate to the particular brand website.
Right-click on the webpage and click Console option.
Open the developer console and enter the following command: _mp.printDebugId()
Step Result: The Debug ID appears on the screen.
Live Debugging is performed either in Staging environment or in the Production environment.
To perform Live Debugging on Ingest Labs:
Step 1: Select Live Debugging on the left navigation panel.
Step 2: Select either Staging or Production under the Live Debugging section.
Step 3: Click Start Debugging on the top right corner of the screen.
Step 4: Enter the Debug ID in the Debug ID field or click Start to start the debugging session. You need to enter a Debug ID to see events exclusively from your session on the website.
The following screen appears:
You can see all the tags configured in the tag session for the View Item list.
Note: The Debug ID is unique and is meant to streamline traffic tracking. Without a debug ID, you will be bombarded with general traffic data. Using a debug ID will help to streamline data and view the traffic for a particular session. A debug ID is not mandatory for Staging. A Debug ID is required for Production due to the huge network traffic.
To retrieve the Debug ID, follow the procedure "Retrieve the DebugID Using Console".
Step Result: The live debugging details appear on the screen.
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.
To filter the events during Live Debugging, perform the following steps:
On the Live Debugging page, click Add Filter.
Select any of the following fields:
Tag
Page Name
Provider
Device Type
Browser
Language
Domain
Status
Select the Operator options and select any operator to populate the list of available fields.
To stop Live Debugging session, click Stop Debugging on the top right corner of the screen.
To navigate to the Data Governance screen, select Data Governance from the left navigation panel.
The Data Governance screen lists all the providers configured in a particular project.
Each provider displays the status as Allowed or Blocked in the right corner. When you create a new project, all providers are initially set to Allowed by default.
Ingest Labs blocks or allows the triggering of tags based on the following conditions:
User consent
Provider settings
The following table lists the two scenarios while triggering the tags.
User provides data tracking consent
True
Allowed
Yes
User provides data tracking consent
True
Blocked
Yes
User denies data tracking consent
False
Allowed
Yes
User denies data tracking consent
False
Blocked
No
The Providers in the Allowed state are allowed despite the value of pr_comp.
The Providers in the Blocked state are allowed only when the pr_comp = True.
Ingest Labs includes two environment types to clearly segregate the stages of implementation:
Staging
Production
The Environments section includes the following topics:
To access the Environments section, select Environments on the left navigation panel.
Name
Denotes the Environment name.
Status
Denotes the Environment status.
Author
Denotes the user who created the environment.
Last Updated on
Denotes when the Environment is last updated.
To edit the status of the provider under Data Governance, perform the following steps:
Navigate to Data Governance -> Provider from the left navigation panel.
Select the Allowed drop-down menu from the Status column and click Blocked to block data tracking. You can also switch the provider status from Blocked to Allowed.
Click Review to review the changes before you submit the changes.
Enter the Name and Description in the provided fields.
Click Submit to submit the changes.
Step Result: The Provider status is updated in the Data Governance screen as well as in the section.
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.
Click the show changes to view the timeline changes:
You must also ensure to navigate to the Publish section and publish the provider status of the respective provider.
The Live Debugging feature in Ingest Labs displays all the tags that are trigerred in real-time on a particular page. You can perform live debugging for both the server-side tags and browser-side tags. The event data is populated in the live debugging section.
Step 1: Click on the start debugging button. Without entering the debug ID, you can view all the events firing in real-time traffic on the website.
Step 2: Click on “View request” of any SS tag to view API call request/response body.
You can view the following tag details:
Step 3: Click "data elements" to view the data element details.
Step 4: Click "request body" to view the following page:
Step 5: Click "response body" to view the following page:
For all the tags that are triggered, you can view the following key information:
Event Time
The event time-stamp.
Page Name
The page from which the tag is triggered.
Provider
Displays the Provider details.
Tag
Displays the Tag details.
Platform
Displays the Platform from which the page is accessed.
Status
Displays the tag status, whether the tag is successfully triggered or not.
You can perform the Live Debugging in two ways, either through the console or through a Live Debugging session on Ingest Labs.
The Live Debugging section includes the following topics:
Cookie consent is the process of asking website visitors for permission to store and use their data through cookies.
Navigate to Tag Manager > Data Governance > Cookie Consent Providers.
Follow these instructions to successfully set up a new provider:
Step 1: Click Add Cookie Provider.
Step 2: Enter Provider Details.
Name: Input an appropriate and descriptive name for the Cookie Consent Provider.
Description: Provide a clear and relevant description that outlines the purpose of the provider.
Step 3: Select Consent Template.
Choose between the two available consent templates:
One Trust Consent Provider: This is a third-party solution for managing cookie consent. It's an external service that integrates into your system to handle user consent preferences automatically.
Custom Template: This allows you to design and configure your own cookie consent setup according to your specific requirements.
Step 3.1: One Trust Consent Provider:
Follow these steps to set up a Cookie Consent Provider with the One Trust Consent Provider template:
When you choose the One Trust Consent Provider template, you won’t need to write JavaScript code, as it's a third-party solution that automatically manages cookie consent for you.
Name: Click the Name field and enter a unique and descriptive name for the provider.
Description: Click the Description field and provide a brief explanation of what the provider does.
After filling in the necessary details, click Save to finalize the setup.
Step 3.2: Follow these steps to set up a Cookie Consent Provider with the Custom Template:
Name: Click the Name field and provide a unique name for the provider.
Description: Click the Description field and enter a brief explanation of the provider's purpose.
JavaScript: In the JavaScript field, paste the relevant custom JavaScript code that handles the cookie consent functionality.
After filling in the necessary details, click Save to finalize the setup.
Assigning Classification Codes
Cookie classifications help you organize and manage cookies based on their purpose and functionality.
Assigning appropriate classifications ensures compliance with regulations and provides clarity for users about how their data is being used.
Common Cookie Consent Classification Codes:
· Strictly Necessary Cookies: Cookies that are essential for the website to function: C0001
· Preference Cookies: Cookies that remember user preferences or choices: C0002
· Performance Cookies: Cookies that collect information about website usage: C0003
· Targeting/Advertising Cookies: Cookies used to deliver personalized ads, track browsing behaviour, and build user profiles for targeted advertising: C0004
· Functional Cookies: Cookies that provide additional functionality, such as remembering login credentials or enabling live chat: C0006
·Session Cookies: Temporary cookies used for maintaining a session across pages: C0007
· Persistent Cookies: Cookies that stay on the user's device after the session ends, typically used for remembering login details or user preferences between sessions: C0008
· First-party Cookies: Cookies set by the website the user is currently visiting: C0009
· Third-party Cookies: Cookies set by external sites, usually for advertising, tracking: C0010
Ste 1: On the left-hand menu under Data Governance, click Cookie Classifications to access the classification settings.
Step 2: Click the Add Cookie Classification button located at the top right.
Step 3: Classification Code: Add an appropriate code to identify the classification.
Step 4: Classification Name: Add a descriptive name for the classification.
Step 5: Description: Provide a brief explanation outlining the purpose of the classification.
Step 6: Under Cookie Providers, click Add Provider to add the appropriate provider.
Step 7: In the Consent Code, give the appropriate consent code. Click Provider and select the appropriate cookie provider.
List of consent codes are:
· Consent Given: The user has consented to the use of strictly necessary cookie: C0001-allow
· Consent Denied: The user has denied consent for strictly necessary cookies: C0001-deny
· Full Consent: The user has granted consent for all cookie categories: C0000-all-allow
· Partial Consent: The user has given consent for some cookie categories (e.g., accepting necessary and performance cookies, but rejecting advertising cookies) C0000-partial-allow
· No Consent Given: The user has not given consent for any cookies, meaning no cookies (except strictly necessary) should be set: C0000-no-consent
Step 8: Once all details are entered, click Save
A confirmation message will appear: Cookie Classification was created successfully.
Step 9: The status will be marked as Pending Publish. To finalize, you must publish the classification.
Publish the Cookie Classification
Step 1: On the left-hand menu click Publish.
Step 2: Click Publish to Staging.
Step 3: Scroll down to the Classification Codes section and check the appropriate cookie classification. Once selected, the related Cookie Provider will appear automatically.
Ste 4: Scroll up and click Review.
Step 5: In the Name section, provide an appropriate name. In the Description section, enter a relevant description, and then click Publish to Staging.
Step 6: A popup message will appear, confirming the publication with the message: Published item successfully. This confirms that the item has been published.
Step 1: In the left-hand menu, go to the Providers section.
Step2: Click the particular Cookie Classification, then click the Action button dropdown and select Edit.
Step 3: Scroll down to the Classification Codes (Optional) section and click Add Classification Codes.
Step 4: The Classification Codes panel will open on the right side. You can either search for a code in the search bar or create a new one by clicking Create Consent Classification.
Step 5: Click Save
A popup message will appear: Provider was updated successfully, confirming the update.
Restoring a Deleted Cookie Consent Provider
Note 1: Both Cookie Consent Providers and Cookie Classifications have a restore option, allowing you to recover deleted items if needed.
Note 2: The restore option for both Cookie Consent Providers and Cookie Classifications is available only if they have been published.
Note 3: To delete a Cookie Classification, it must not have any dependencies. If dependencies exist, they must be removed before the classification can be deleted.
Click Restore.
A confirmation pop-up message will appear, confirming that the Cookie Classification has been restored successfully.
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.
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.
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.
The Alarms section includes the following topics:
To view the Production Environment, select the Production option on the Environments screen.
The Info section includes the following information.
Name
Description
Sandbox Demo Site
The SDK Settings section includes the following information:
Event Trigger
Includes the browser event which triggers the Tag manager. Select the relevant option from the following drop-down menus: • Event Type: Denotes the event type. • Event Trigger: Denotes the event trigger. Ingest Labs uses page_load eedl event as the trigger. Since this trigger is not used in most of the setups, it is a non_existing_event as of now. • Default Cookie Domain: The Cookie domain will automatically be detected at runtime. Includes the Auto and Manual options. When in auto, look up the domain name in the url, and set local cookies accordingly. The user needs to hardcode cookie domains for a very few sites. For default cookie domain set as auto, if the domain is ingestlabs.com, then the Ingest Labs cookies will be set at .ingestlabs.com
Secondary Trigger (JavaScript Variable)
Select this check box to define a secondary trigger.
Enable error logging
These settings allow the client sdk to report errors and exceptions to the Ingest Labs servers. Select the check boxes to enable the following errors for debugging purposes: • Report Client-side SDK errors • Enable Logging for client-side SDK
Trigger Delay
Once the user gets the page_load event, the user can configure the delay before the tag is triggerred. This is to give the page a chance to render content before tag manager is fired.
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.
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 Production environment of the client website. 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 Production environment of the client website:
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:
Data Collector Configuration
Approved Data Collection domains
Reach out to the Ingest Labs Support team to add domain level configuration.
To view the Staging Environment, select the Staging option on the Environments screen.
The Info section includes the following information.
Name
Description
Sandbox Demo Site
The SDK Settings section includes the following information:
Event Trigger
Includes the browser event which triggers the Tag manager. Select the relevant option from the drop-down menus: • Event Type: Denotes the event type. • Event Trigger: Denotes the event trigger. Ingest Labs uses page_load eedl event as the trigger. Since this trigger is not used in most of the setups, it is a non_existing_event as of now. • Default Cookie Domain: The Cookie domain will automatically be detected at runtime. Includes the option either Auto or Manual. When in auto, look up the domain name in the url, and set local cookies accordingly. The user needs to hardcode cookie domains for a very few sites. For default cookie domain set as auto, if the domain is ingestlabs.com, then the Ingest Labs cookies will be set at .ingestlabs.com.
Secondary Trigger (JavaScript Variable)
Select this check box if a secondary trigger is to be defined.
Enable error logging
These settings allow the client sdk to report errors and exceptions to the Ingest Labs servers. Select the check boxes to enable the following errors for debugging purposes: • Report Client-side SDK errors • Enable Logging for client-side SDK
Trigger Delay
Once the user gets the page_load event, the user can configure the delay before the tag is triggerred. This is to give the page a chance to render content before tag manager is fired.
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.
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:
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:
Data Collector Configuration
Approved Data Collection domains
Reach out to the Ingest Labs Support team to add domain level configuration.
The Settings option provides you options to configure the settings for a particular project.
Step 1: To view the Settings screen, select Settings from the left navigation panel.
The Settings screen includes the following information:
Name
Name of the project.
Description
Description of the project.
Project Type
Denotes the project type.
Demand-Side Platform (DSP)
By default, this option is disabled. To enable the DSP in this project, reach out to the Support team.
Step 2: Click edit on the top right corner to edit the project name and the description.
Step 3: Click Save to save the changes. Click cancel to revert to the original settings.
Step 1: To delete the project, select Delete option from the Actions drop-down menu on the top right corner.
Step 2: Click OK in the confirmatory dialog box that appears.
Step Result: The project is deleted.
The following UI elements appear on the Alarms screen.
Name
Denotes the Alarm Name.
Status
Denotes the Alarm status .
Created By
Denotes the user who created the alarm.
Updated By
Denotes the user who updated the alarm.
Updated On
Denotes the time and the date of the last update of the alarm.
You can configure one or both of these alarms:
Tag Anomaly Detection Alarm: To notify contacts when tag anomalies occur.
Tag Expiration Alarm: To notify contacts when a tag expires.
In Ingest Labs, you can create an alarm for tag expiration and anomaly detection. The configured contacts will receive an alert when an abnormal tag trigger is detected or when a tag expires. You can also set an advance notification for tag expiry using the Tag Expiry Look Back feature.
To add a new Tag Anomaly Detection 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 the Tag Anomaly Detection Alarm.
Step 4: Enter the following details in the New Anomaly Detection screen.
Name
The Alarm Name.
Description
Enter the description of the Alarm. The description must be more than five characters.
Environment
Select the Staging or the Production environment.
Step 5: Enter the details mentioned in the Settings section.
Threshold Sensitivity:
High sensitivity: The anomaly detection trigger will fire and send alert if it detects an anomaly at least ONCE in the previous hour.
Medium sensitivity: The anomaly detection trigger will fire and send alert if it detects an anomaly once in the past 2 consecutive hours.
Low sensitivity: The anomaly detection trigger will fire and send alert if it detects an anomaly once in the past 3 consecutive hours.
The Tag behavior is determined using the Bollinger Band.
Preferred Timings:
Select the exact tag monitoring period from the Preferred Timings drop-down. This is an optional setting. For example, If there is a sudden spike in traffic in the evenings, you could set the preferred timing from 5 p.m. to 10 p.m. The tag firing activities will be monitored every evening between 5 p.m. to 10 p.m.
Note: The tags are monitored continuously with a set preferred timing.
Step 6: Enter the details in the Filter Conditions section.
You can make the alarm more specific by creating monitors on specific tags, providers, or other attributes. To filter the alarms, perform the following steps:
On the alarm page, click Add Filter.
Tag
Specifies the tag to be monitored for anomaly detection.
Page Name
Specifies the Page Name to be monitored for anomaly detection. Select either contains or is from the Operator drop-down menu.
Provider
Specifies the Provider that needs to be monitored for anomaly detection.
Device Type
Select this option to display devices such as Desktop, Web, Mobile Web, Tablet, and Other.
OS
Select this option to display information regarding the OS such as iOS and Android.
Language
Select this option to set the preferred language.
Domain
Select the appropriate domain name. Select either contains or is from the Operator drop-down menu.
Status
Select this option to set to one of the Tag trigger Statuses. • Success (200) • Success (202) • Provider Side Failure (400) • Provider Side Failure (404) • Provider Side Failure (500) • Tag Validation Failure (900) • Tag Validation Failure (1000) • Error (1001) • Privacy Blocked (1002) • Skipped (1003) • Success with Warnings (1004) • Scheduled for retry (1005) • Maximum retry attempts reached (1006) • Delayed (1007)
Select the Operator options and select any operator to populate the list of available fields.
Step 7: Select Destinations section.
Select Notification Group: The tag anomaly alert will be 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.
Provide Email ID: Enter the email IDs of the users to send the notification for tag anomaly. You can add users using the Add Users tab.
Step 8: Click Save to save the settings.
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.
Name
The Alarm Name.
Description
Enter the description of the Alarm. The description must be more than five characters.
Metadata filters
Select filters to make the alarms more specific and monitor specific tag groups.
Step 5: 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 timezone.
Step 6: Select Destination.
Step 7: 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 8: Provide Email ID: Enter the e-mail IDs to send the tag anomaly notification. You can add users using the Add Users tab.
Step 9: Click Save to save the settings.
You can delete a particular alarm.
To delete an alarm in Ingest Labs, perform the following steps:
Select the alarm that you want to delete.
From the Actions drop-down menu on the top right corner, select Delete.
Click Yes on the confirmatory message that appears.
Step Result: The alarm is deleted successfully.
Introduction
The Funnel Monitoring Alarm is a new alarm added to Tag Manager that provides real-time alerts for specific notifications within your funnels.
Follow these steps to set up and configure the alarm:
Navigate to Tag Manager > Alarms.
Step 1: Click the Add Alarm dropdown and select Add Funnel Monitoring Alarm.
Step 2: Under the Info section, the Name and Description fields are available. In the Name field, enter a descriptive name for your Funnel Monitoring Alarm, and in the Description field, provide additional details to clarify the purpose or scope of the alarm.
Step 3: Under Funnel Monitoring Type, in the Select Funnel Monitoring Type dropdown, two options are available:
· Conversion and
· Occurrence
Step 3.1: Click Conversion.
Conversion: This option tracks the percentage of users who progress from adding products to their cart to completing a purchase. For example, if a user visits the website, adds products to the cart but does not complete the purchase, the website owner can use this alarm to monitor the conversion rate. The alarm provides a clear percentage, helping the owner understand how many users are converting from Add to Cart to Purchase.
Step 3.1.1: In the Event Name section, provide a clear and descriptive name for the event you want to monitor. Click Add Event.
Step 3.1.2: Under the Check Type dropdown, the following options are available:
· LESS_THAN
· GREATER_THAN
· LESS_THAN_EQUAL_TO, and
· GREATER_THAN_EQUAL_TO.
For example, if you specify 60% in the Value section and select LESS_THAN from the dropdown, a notification will be sent if the monitored percentage falls below 60%. Similarly:
· GREATER_THAN will send a notification if the percentage exceeds 60%.
· LESS_THAN_EQUAL_TO will trigger a notification if the percentage is 60% or lower.
· GREATER_THAN_EQUAL_TO will send a notification if the percentage is 60% or higher.
Step 3.2: Click Occurrence.
Step 3.2.1: In the Event Name section, provide a clear and descriptive name for the event you want to monitor.
Step 3.2.2: Under the Select Threshold Type dropdown, the following options are available:
LESS_THAN
GREATER_THAN
LESS_THAN_EQUAL_TO
GREATER_THAN_EQUAL_TO
In the Value section, specify the numeric threshold you want to monitor. For example, if you select LESS_THAN and enter a value of 50, the alarm will trigger when the monitored percentage falls below 50%. Similarly:
· Selecting GREATER_THAN will trigger the alarm when the value exceeds the specified threshold.
· LESS_THAN_EQUAL_TO will activate the alarm when the value is equal to or less than the threshold.
· GREATER_THAN_EQUAL_TO will trigger the alarm when the value is equal to or greater than the threshold.
Step 4: Time Window.
Choose how sensitive you want your alarm to be by configuring the time window settings.
Under the Unit dropdown, the following options are available:
HOUR
DAY
WEEK
MONTH
In the Value field, specify a numeric value that corresponds to your selected unit. For example:
· If you enter 2 in the Value field and select HOUR from the dropdown, the alarm will monitor events within a 2-hour time window.
· Similarly, choosing DAY with a value of 1 will set the alarm to monitor events within a 1-day period.
Step 5: Destinations.
Under the Notification Groups dropdown, you can select the groups that should receive the notification. By choosing a specific group, all members of that group will be alerted when the alarm is triggered.
Under Email IDs, if you want to send the notification to a specific email address in addition to the selected groups, you can enter the email address here. This allows you to add a new user or ensure that a particular individual receives the notification directly.
Media Data Platform Overview
Ingest Labs' Media Data Platform (MDP) is designed to provide deep insights into visitor behavior on websites. The MDP ensures precise tracking and analysis of visitor journeys, enabling a better understanding of user interactions. Key features include First-Party ID generation, comprehensive visitor journey tracking, and advanced cookie management, all aimed at improving data analysis, visitor insights, and website performance.
First-Party ID Generation: Generates a unique First-Party ID for each client, enabling precise tracking and tailored data analysis.
First-Party Cookie Identifier: Creates a first-party cookie identifier for each visitor to track interactions and activities.
Comprehensive Visitor Journey Tracking: Captures detailed journey information for each visitor, including pages viewed, products considered, and interaction sequences.
Identifier Generation and Management: Verifies the presence of existing Visitor IDs and generates new First-Party IDs if necessary, integrating with the Magic Pixel SDK to manage MPIDs.
Data Interpretation and Analysis: Identifies product categories viewed by visitors and generates comprehensive statistics, offering valuable insights into customer behavior.
Cookie Management and Domain Handling: Manages first-party cookies by handling sub-domains to ensure they are treated as first-party.
The Ingest Labs MDP offers enhanced visitor insights, personalized user experiences, and improved conversion rates by addressing potential drop-off points. The platform ensures accurate data tracking and collection, leading to reliable insights, and optimizes cookie management complying with privacy standards, and improving data integrity. These features collectively enhance visitor engagement and overall website performance.
Enhanced Visitor Insights: Gain a comprehensive understanding of how visitors navigate and interact with the website. This insight is crucial for optimizing user experience and increasing engagement.
Personalized User Experience: By understanding individual visitor journeys, you can tailor content and recommendations to match interests and preferences, leading to a more personalized and satisfying user experience.
Improved Conversion Rates: Detailed visitor behavior tracking allows for identifying and addressing potential drop-off points in the customer journey, enhancing overall conversion rates.
Enhanced Data Accuracy: The platform ensures accurate tracking and data collection by generating and managing unique identifiers, leading to more reliable insights.
Improved User Insights: Detailed analysis of product categories viewed and comprehensive statistics generation help understand customer preferences and behavior.
Optimized Cookie Management: Proper handling of first-party and third-party cookies ensures compliance with privacy standards and improves data integrity.
You can edit the details of a particular alarm.
To edit an alarm in Ingest Labs, perform the following steps:
Step 1: Select the alarm that you want to edit.
Step 2: From the Actions drop-down menu on the top-right corner, select Edit.
Step 3: Edit the alarm details and click Save on the top right to save the changes.
You can delete a particular alarm.
To delete an alarm in Ingest Labs, perform the following steps:
Step 1: Select the alarm 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 alarm is deleted successfully.
Media Data Platform Dashboard
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.
Perform the following steps to create a new dashboard:
Click Dashboard from the left navigation panel.
From the Default Dashboard drop-down menu, click New Dashboard.
Step Result: The New Dashboard screen appears.
Enter the Name and Description in the relevant fields.
Note: Ensure that the number of characters in the name field is five or more. Else the following message appears: Name must be longer than or equal to 5 characters.
Click Save to save the changes.
Step Result: The new Dashboard is added successfully.
Note: You cannot edit the Default Dashboard as the project is configured with the default settings.
The Dashboard screen is customisable and can include the following details:
By default, the Dashboard is set to display the data for the last 7 days. To view the data for a different time duration, you must set the time range from the Last 7 days tab on the top of the page and click Refresh.
To view the data for a custom duration, select the start date from the 7 days ago tab and the ‘end date’ from the Now tab at the top of the screen and click Refresh.
Total Conversions
Total number of conversions (for example, purchases)
Total Sales
Total sales value
Total Sales - KartMax
The total sales or conversion value in Kartmax
Average Order Value (AOV)
The average value of the conversions or the orders
Returning Users
Registered and unregistered users who repeatedly access the website
First visits by Users
First visits by registered and unregistered users
Sales through Campaigns
Total sales through various ad campaigns on Google, Meta, Instagram, Wishlink, Bing, Criteo, YouTube, and others.
Sales through Direct Visits
Total sales registered through direct visits (without referral campaigns)
Top 10 Product conversion
List of products purchased, number of people purchasing the products, total value of the purchase