View Production Environment

Introduction

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

Procedure

Under the Name field, click Production.

Info

The Info section includes the following information.

• Name: Displays production, indicating the environment type.

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

SDK Settings

Click Edit.

The SDK Settings section includes the following information:

Event Type

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

Event Trigger

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

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

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

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

Secondary Trigger (JavaScript Variable)

Select this checkbox to enable a secondary trigger.

Once enabled, two additional fields appear:

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

• Wait Time – Define the time (in milliseconds) the system should wait before evaluating the secondary trigger.

Cookie Domain

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

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

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

Enable Error Logging

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

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

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

Trigger Delay

Defines the time to wait after the page_load event before the tag is triggered.

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

Content Security Policy

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

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

SDK Setup

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

The following is the SDK URL that you must embed in the 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:

Approved Domains and Collector URLs

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

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

The Approved Domains & Collector URLs display the following information:

• Data Collector Configuration

• Approved Data Collection domains

  Reach out to the Ingest Labs Support team to add domain level configuration.