Configure at.js

Information to help you set several settings on the at.js Settings page.

Note: You can override settings in the at.js library, rather than configuring the settings in the Target Standard/Premium UI or by using REST APIs. For more information, see targetGlobalSettings().

To open the Settings page:

  1. Click Setup > Implementation.

  2. Select at.js > Edit at.js Settings.

The section contains the following information:

Content Delivery Settings

Please consult with Client Care before changing these settings. These settings are required for most implementations.

Setting Description
Autocreate global mbox

Select whether to embed the global mbox call in the at.js file to automatically fire on each page load.

Changing this setting affects both at.js and mbox.js.

Global mbox name

Select a name for the global mbox. By default, this name is target-global-mbox.

Special characters, including ampersands (&), can be used in mbox names with at.js.

Changing this setting affects both at.js and mbox.js.

Advanced Settings

Setting Description
Client Code

The client code is a client-specific sequence of characters often required when using the Target APIs.

This setting cannot be changed.

IMS Organization ID

This ID ties your implementation to your Adobe Marketing Cloud account.

This setting cannot be changed.

Profile Lifetime

This setting determines how long visitor profiles are stored. By default, profiles are stored for two weeks.

To change the Profile Lifetime setting, contact Client Care.

X-Domain

Determines whether the browser sets cookies in your own domain (1st party cookies), Target's domain, or both.

Changing this setting affects both at.js and mbox.js.

Timeout

If Target does not respond with content within the defined period, the server call times out and default content is displayed. Additional calls continue to be attempted during the visitor's session. The default is 15 seconds.

Changing this setting affects both at.js and mbox.js.

The at.js library uses the timeout setting in XMLHttpRequest. The timeout starts when the request is fired and stops when Target gets a response from the server. For more information, see XMLHttpRequest.timeout on the Mozilla Developer Network.

If the specified timeout occurs before receiving the response, default content is shown and the visitor might be counted as a participant in an activity because all data collection happens on the Target edge. If the request reaches the Target edge, the visitor is counted.

Consider the following when configuring the timeout setting:

  • If the value is too low, users might see default content most of the time, although the visitor could be counted as a participant in the activity.

  • If the value is too high, visitors might see blank regions on your web page or blank pages if you use body hiding for extended periods of time.

To get a better understanding of mbox response times, look at the Network tab in your browser's Developer Tools. You can also use third-party web performance monitoring tools, such as Catchpoint.

Note: The visitorApiTimeout setting ensures that Target doesn't wait for the Visitor API response for too long. This setting and the Timeout setting for at.js described here do not affect each other.
Legacy Browser Support
Note: The Legacy Browser Support option is available in at.js version 0.9.3 and earlier. This option was removed in at.js version 0.9.4. For a list of browsers supported by at.js, see Supported Browsers.

Legacy browsers are older browsers that do not fully support CORS (Cross Origin Resource Sharing). These browsers include: Internet Explorer browsers earlier than version 11 and Safari versions 6 and below. If Legacy Browser Support is disabled, Target does not deliver content or count visitors in reports on these browsers. If this option is enabled, it is recommended to do quality assurance across older browsers to ensure a good customer experience.

Code Settings

Please consult with Client Care before changing these settings. These settings are required for most implementations.

Setting Description
Library Header

Add any custom JavaScript to include at the top of the library.

Library Footer

Add any custom JavaScript to include at the bottom of the library.