Configure Browse Settings in Script Manager

Configure product and contact capture settings in Bronto so that you can collect browse data. Not all Bronto features powered by Script Manager have capture settings.

About this task

In order to capture browse and contact data you will need to identify and set product and contact selectors. You can use either a CSS selector or JSON object when configuring product and contact capture.

The steps below walk you through how to set up Script Manager and configure your selectors with Script Manager settings.

Procedure

  1. Go to Settings > Integrations > Script Manager.
  2. Add the Script Manager code to your site manually or with Google Tag Manager.
  3. In the Individual Features section, set Browse Recovery or Recommendations Web as active.
  4. Optional: Specify the Domain you want to capture browse data for.
  5. Configure your Commerce Platform settings.
  6. Select your Commerce Platform. If you are not using one of the listed integrations, select select Other/None.
    • If you select Magento 2, the Product ID Selector Type is set to CSS and the Email Address Selector(s) and Product ID Selector(s) fields are automatically populated. The Product ID Selector Visibility is set to All. Click Save Changes to finish.
    • If you select Salesforce Commerce Cloud Connector, the Product ID Selector Type is set to CSS and the Email Address Selector(s) and Product ID Selector(s) fields are automatically populated. The Product ID Selector Visibility is set to All. Click Save Changes to finish.
    • If you select Shopify, the Selector Type is set to JSON and the Email Address Selector(s) and the Product ID Selector fields are automatically populated. Click Save Changes to finish.
    • If you select NetSuite SuiteCommerce, the Product ID Selector Type is set to CSS and the Email Address Selector(s) and Product ID Selector(s) fields are automatically populated. The Product ID Selector Visibility is set to All. Click Save Changes to finish.
    • If you selected Other/None nothing is automatically populated and you should complete all of the following steps.
  7. Optional: If you want to capture email addresses only after a contact has clicked a button, turn on the Email Button Selector(s) toggle.
    1. If this toggle is turned on, enter the button selector(s).
      • When the button being targeted has a type identified, such as <button type="submit>, the value entered should be input[type=button]
      • When the button has an ID, such as id="popup-submits-button-123", the value entered should be #popup-submits-button-123
  8. Enter the CSS selector(s) used to capture emails on your site in the Email Address Selector(s) box.

    This allows Bronto to recognize the email address of a customer browsing on your site and, when possible, to associate that email with a Bronto contact. If you use different selectors to capture email addresses, you can enter multiple selectors using a comma separated list.

  9. Optional: Enter contact_eid in the Contact ID URL Parameter(s) box.

    This allows Bronto to capture data for a contact by associating the browse data with the contact's unique external ID. You should use Bronto's custom analytics feature to help set this association up. See Custom Web Analytics Connection for more information.

  10. Select the Product Selector Type:
    • CSS if you are using jQuery selectors to identify your products.
    • JSON if you are using JSON objects to identify your products.

    If you're not sure which your site uses, find a product ID on your site and view its source code. If the product ID is defined inside of a <script> tag and looks similar to ‘Product ID’ : ‘SKU123’, you should use a JSON selector. If the product ID is defined inside an HTML element, such as a <div> tag, and looks similar to <div class="product" sku="SKU123">, use a CSS selector.

  11. Enter your JSON or CSS selector in the Product ID Selector box. You can target multiple selectors using a comma separated list.
    Target the selector that can map to the Product ID field. The selector you identify for the Product ID Selector(s) must pull in product IDs that match the Product ID field data in your Bronto product catalog or Browse Recovery rules will not trigger properly. Because the Product ID is unique, Browse Recovery can pull all of the other product data from your Bronto product catalog.
    Note: If you use JSON, you must use JSON array format. For example, product["id"].
    Selector examples:
    • CSS code: <div class="product" name="My Product">SKU123</div> would translate to the selector div.product
    • CSS code: <span class="sku-value" itemprop="sku">SKU123</span> would translate to the selector span.sku-value
    • CSS code: <input id="productID">SKUI23</input> would translate to the selector #productId or input[id="productId"]
    • JSON code: dataLayer = [{ ‘ProductId’ : ‘SKU123’ }]; would translate to the selector dataLayer[0][‘ProductId’]
    • JSON code: dataLayer = { ‘ProductId’ : ‘SKU123’ }; would translate to the selector dataLayer[‘ProductId’]
  12. Optional: If you use CSS selectors and want to target an attribute, enter it in the Product ID Selector Attribute box.

    You can only target an attribute for CSS selectors and you only need to target an attribute when the code related to the Product ID (SKU) is stored at the attribute level. For example, your site code might have <div id=“product-sku” data-actual-sku=“blah-123”></div>. In this case, the Product ID Selector would be #product-sku and the Product ID Selector Attribute would be data-actual-sku.

  13. From the Product ID Selector Visibility list select
    • All if you want the view tracked any time the selector is present in the code for the page, even if the contact does not see it.
    • Visible On Page if you want the view tracked only when a contact views a page with the content associated with the selector on it.

    This setting mostly impacts whether you want a pop up or mouse over to count as a page view. If you want to count every interaction with a product, select All.

  14. Click Save Changes. Your Script Manager settings changes will take up to 15 minutes to take effect.