View Production Environment
Last updated
Last updated
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.
