Pages

This section covers the most common problems that you might run into when working with modifications and other features, and shows you how to troubleshoot and solve those problems.

The following instructions rely on the Frosmo Debugger. While you can use the Preview Tool for previewing and testing modifications, the Debugger provides more advanced debugging features, which you need in some problem cases.

What seems to be the problem?

Modification content is not displayed on the page

This problem can be caused by a number of reasons. Try the following solutions:

  1. Open the page using private browsing.
  2. Remove yourself from the comparison group if you're in it.
  3. Check if the placement is valid for the page.
  4. Check if the modification is loaded on the page.
  5. Check if the placement uses the correct trigger.
  6. Check if you're in the correct segment or segments.
  7. Check if your visitor session matches any other audience targeting settings used by the modification.
  8. Check the modification schedule to determine when the modification is displayed.
  9. Check for errors in the modification content.

Opening the page using private browsing

Open the page in private browsing mode (also known as incognito mode). If the modification now displays normally, the issue is with your browser cache and only affects your visitor session. To fix the issue outside the private browsing mode, clear your browser cache and reload the page.

Removing yourself from the comparison group

If you're in the comparison group, remove yourself from it:

  1. In the Frosmo Debugger, select Info.
  2. In the Visitor information section, if the Comparison group field has a green check mark, click Disable.

    Disable the comparison group

You have removed yourself from the comparison group and now get the modifications rather than the original content.

Checking if the placement is valid for the page

A placement is valid for a page if the URL rules of the placement match that page. If the placement has no URL rules defined, the placement is valid for all pages. The target element of the placement need not exist on a page for the placement to be valid for the page.

To check if the placement is valid for the page:

  1. In the Frosmo Debugger, select Preview.
  2. Click inside the Placement field.
  3. Check the placement status (see the following table).

Table: Solutions depending on placement status (when modification content is not displayed on the page)

Status (click the images to enlarge)DescriptionSolution

Placement is marked with a green check mark.

Placement is valid

The placement is valid for the page.In the Control Panel, make sure the placement targets the correct element or elements on the page, and check if the placement has multiple modifications assigned to it.

Placement is marked with a red cross.

Placement is not valid

The placement is not valid for the page.In the Control Panel, update the URL rules for the placement to include the current page.

Checking if the modification is loaded on the page

To check if the modification is loaded on the page:

  1. In the Frosmo Debugger, select Debug.
  2. In the Modification field, select the modification. The Debugger displays the basic event tracking status for the modification.
  3. Check the modification status (see the following table).

Table: Solutions depending on modifications status (when modification content is not displayed on the page)

Status (click the images to enlarge)DescriptionSolution

Rendered and Display are green.

Modification is rendered and displayed

The modification is loaded.If the modification has multiple variations, check in the Modification section which variation you got. It could be that you got a different variation from the one that you expected.

Frosmo Debugger displays a notification about a placement mismatch.

Modification is not loaded

The modification is not loaded because its placement is not valid for the page.In the Control Panel, check that the modification uses the correct placement and that the content variations are active.

Checking if the placement uses the correct trigger

If the placement uses a trigger, make sure it's the correct trigger:

  1. In the Control Panel, select Modifications > Placements.
  2. In the placements list, find the placement, and click the placement name.
  3. In the Trigger field, check the selected trigger. If the trigger is not the correct one, change the trigger.

For more information about placement settings, see Creating placements.

Checking if you're in the correct segments

If the modification targets specific segments, make sure you're in the correct segment or segments:

  1. In the Frosmo Debugger, select Info.
  2. In the Visitor information section, check the Segments field to view the segments to which you currently belong. The segments defined for the modification in the Control Panel must match your segments.

    Current segments

  3. If you're not in a correct segment, perform whatever actions are needed to place you in that segment.

Checking the other audience targeting settings

If the modification uses other audience targeting settings, such as target groups or test mode, make sure your current visitor status matches them.

To check your current visitor status:

  1. In the Frosmo Debugger, select Info.
  2. Check the Visitor information section to view detailed information about your session. For more information about the different fields, see Frosmo Debugger.

Checking the modification schedule

Check the modification schedule to see if the modification should be currently displayed:

  1. In the Control Panel, select Modifications > Overview.
  2. In the modifications list, find the modification, and click the modification name.
  3. Select Display Options.
  4. Check the display time settings, including the advanced time settings. The time settings use the time zone defined for the company. If the modification is not scheduled for the current time, it's not displayed on the page.

    Cached modifications use the time zone of the visitor's browser rather than the time zone defined for the company. While advanced time settings are disabled for cached modifications, the start and end times still apply.

    You can check the current time and time zone for the company in the Control Panel footer.

    Current time and time zone for a company

Checking for errors in the modification content

Check the modification content for errors that might prevent the content from being displayed.

To check the content:

  1. On the page, check for Frosmo Core error messages:
    1. Open the Frosmo Debugger, and enable and open the event log.
    2. Look for console.error events, and check their data.
  2. On the page, check for failed Message API requests:
    1. Open the developer tools, and select the Network tab.
    2. Look for failed messageApi requests.

      Failed Message API request

    3. To check the details of a request, click the request and review its headers and response.
  3. In the Control Panel, review and update the modification content if necessary. For more information about editing a modification, see Managing modifications.

Modification is not getting clicks

The following assumes that the modification displays normally.

This problem can be caused by a number of reasons. Try the following solutions:

  1. Make sure the modification content uses clickable elements.
  2. Make sure the modification content is correctly nested in the page code.
  3. Check for errors in the modification content.

Making sure the modification content uses clickable elements

Make sure the modification content uses HTML elements for which Frosmo Core automatically tracks clicks:

  • <a>
  • <area>
  • <button>
  • <form> (on submit)
  • <input type="button">
  • <input type="image">
  • <input type="submit">
  • Any element with the class frosmo-click

For other elements, click tracking must be implemented manually.

Making sure the modification content is correctly nested in the page code

Make sure the modification content for which clicks should be tracked is rendered inside the placement <div> element.

Modification content rendered inside the placement div element

Checking for errors in the modification content

Check the modification content for errors that might prevent clicks from being tracked.

To check the content:

  1. On the page, check for Frosmo Core error messages:
    1. Open the Frosmo Debugger, and enable and open the event log.
    2. Look for console.error events, and check their data.
  2. On the page, check for failed Optimizer API requests:
    1. Open the developer tools, and select the Network tab.
    2. Look for failed optimizerApi?event=clickMessage requests.

      Failed Optimizer API request for a click

    3. To check the details of a request, click the request and review its headers and response.
  3. In the Control Panel, review and update the modification content if necessary. For more information about editing a modification, see Managing modifications.

Modification is not getting true displays

The following assumes that the modification displays normally.

This problem can be caused by a number of reasons. Try the following solutions:

  1. Make sure the modification content is correctly nested in the page code.
  2. Make sure the modification content has a proper size.
  3. Check for errors in the modification content.

Making sure the modification content is correctly nested in the page code

Make sure the modification content for which true displays should be tracked is rendered inside the placement <div> element.

Modification content rendered inside the placement div element

Making sure the modification content has a proper size

Make sure the modification content has a proper size, that is, that the placement <div> element for the modification has positive width and height values.

To check the size:

  1. On the page, open the developer tools, and select the Elements tab.
  2. In the <body> element, find and select the placement <div> element for the modification. You can find the element by searching for the modification ID or placement ID.

  3. At the bottom of the Styles panel, check the element size.

    Checking the element size

If either the width or the height is 0, or if both are 0, the element lacks a proper size, meaning the platform cannot track true displays for the element. Either the element has no content to display and therefore takes up zero space, or the content uses absolute or fixed position, which removes the content from the normal flow of the DOM and leaves the containing element without a proper size.

You can also quickly check the size of a placement <div> element by running the following code in the browser console (replace <modification_id> with the actual modification ID):

var el = document.querySelector('.frosmo_message_<modification_id>');
console.log(el.offsetWidth, el.offsetHeight);

The code prints the width and height of the element.

Checking the element size in the console

Checking for errors in the modification content

Check the modification content for errors that might prevent true displays from being tracked.

To check the content:

  1. On the page, check for Frosmo Core error messages:
    1. Open the Frosmo Debugger, and enable and open the event log.
    2. Look for console.error events, and check their data.
  2. On the page, check for failed Optimizer API requests:
    1. Open the developer tools, and select the Network tab.
    2. Look for failed optimizerApi?event=trueDisplay requests.

      Failed Optimizer API request for a true display

    3. To check the details of a request, click the request and review its headers and response.
  3. In the Control Panel, review and update the modification content if necessary. For more information about editing a modification, see Managing modifications.

Modification is not getting conversions

The following assumes that the modification displays normally.

Try the following solutions:

  1. Make sure you understand the conversion attribution model used by the Frosmo Platform.
  2. Make sure another modification further along in the interaction funnel is not getting the conversions. If another modification gets a higher-priority event after the current modification, that modification gets the conversion. To determine if another modification is the cause, test the modification flow on the site, or check the conversion statistics in the Control Panel.
  3. Make sure conversion tracking is correctly implemented for the site. Check with a developer, if necessary. For more information about conversions and how to track them, see Conversions.
  4. Make sure the modification gets clicks, true displays, and, if relevant, custom events normally.

Deactivated cached modification is still getting clicks, displays, and true displays

This is most likely a browser cache issue. The cached modification is still active in a visitor's browser and continues to get clicks, displays, and true displays normally for as long as it remains in the browser cache. This issue will eventually subside as the browser cache gets cleared or refreshed, resulting in the modification getting removed from the cache and therefore from the page.

Trigger is not firing

Make sure the trigger's evaluation point does not occur too early during page load. If the evaluation point occurs before the firing conditions can be met, the trigger does not fire.

For example, let's say your trigger has "Frosmo script loaded" as its evaluation point and is set to fire when a specific DOM element exists. If the Frosmo scripts are in the <head> element of the page, the DOM element may not be available when the trigger is evaluated, since the scripts are loaded and the trigger evaluated before the page content in the <body> element is rendered.

To debug the evaluation flow:

  1. Open the Frosmo Debugger, and enable and open the event log.
  2. Check the log for trigger and other relevant events, and note their order.
  3. In the Control Panel, update the evaluation point settings for the trigger, if necessary.

Enabling and disabling the event log in the Frosmo Debugger

You can set the Frosmo Debugger to display detailed debugging information in the Event Log tab.

Figure: Frosmo Debugger with the event log enabled

Enabling the event log in the Frosmo Debugger also enables debug logging in the browser console. For more information about using the console, see Console debugging with Frosmo Core.

Enabling the event log in the Frosmo Debugger

To enable the event log in the Frosmo Debugger:

  1. In the Frosmo Debugger, select Info.
  2. In the Visitor information section, click Enable for Console debugging. The event log is enabled.

    Enabling the event log in the Frosmo Debugger

  3. Reopen the Debugger, and select Event Log.
  4. Select Show all. This shows events of all severity levels in the log.

    Show all events in the event log

You can now view detailed debugging information in the Event Log tab.

Disabling the event log in the Frosmo Debugger

To disable the event log in the Frosmo Debugger:

  1. In the Frosmo Debugger, select Info.
  2. In the Visitor information section, click Disable for Console debugging. The event log is disabled.

    Disabling the event log in the Frosmo Debugger

You can no longer view any debugging information in the Event Log tab.

  • No labels