How To: Configure Rapid

The Rapid configuration can be accomplished by logging into rapid.yottaa.com. Configuration takes place either in the optimizations or settings tab. For information on the analytics please see the knowledge base article: FAQ - Performance Dashboard - Getting Started

Optimizations

Select - Rapid allows the ability to create a template of the optimizations that are setup. This is helpful for an organization with multiple sites. The select options will create a copy of the current sites optimization configuration available to apply later on.

Screen_Shot_2018-04-26_at_5.22.55_PM.png        

Associate Template – Once you’ve created a copy of an optimization configuration you can use the Associate option to apply this to a site you wish to have that same setup.

 Screen_Shot_2018-04-26_at_5.22.55_PM.png

Optimization History – There is a historical view of all optimization configurations that have gone through the portal. You have all published version with the dates that they were implemented, as well as the current Live version, and the draft version waiting to be published.

Screen_Shot_2018-04-26_at_5.22.55_PM.png

 

Screen_Shot_2018-04-23_at_10.23.37_AM.png                       

Add Optimization – Optimizations applied through the Rapid portal are able to sequence third parties that are dom loaded. Creating a sequencing rule is very straightforward.

Screen_Shot_2018-04-26_at_5.22.55_PM.png

  1. Third Party - Select the third party from the drop down. If the third party you are looking for doesn’t appear you can select the User Defined option. Screen_Shot_2018-04-23_at_11.16.11_AM.png  
  2. Optimization - Select the timing you wish this third party to load.  Screen_Shot_2018-04-23_at_11.18.36_AM.png  

Do Not Defer Loading – Will not sequence the third party

Defer Loading – Fire on onload or specify seconds after onload

Remove Third Party – Will remove the third party and third party will not load

Load on Event – You need to specify whether you want to load the third party based on another third party.

Afterloaded – Meaning only fire after another condition

beforeLoading – Fire selected third party before loading another specified third party.

  1. Criteria - Select the audience of this optimization.   Screen_Shot_2018-04-23_at_11.20.49_AM.png  

All page views – All requests will receive the optimizations

Only if – Select some conditions for which requests will receive the optimizations.

Screen_Shot_2018-04-23_at_11.22.56_AM.png

            Request URL – Specify which requested page

            Client IP – Specify a user, or group of users by IP

Request Header – By any request header name, and value

User Agent - Specify which browser experience gets the optimization

 

Publish Optimization

 After creating your optimization click save in the window.

Screen_Shot_2018-04-26_at_10.34.00_AM.png

Once saved you'll receive a popup letting you know that the optimization has been saved is in the queue for publishing.

Screen_Shot_2018-04-26_at_10.36.08_AM.png

Clicking the list option in the upper right hand corner you'll be able to view the options. You can either publish right away or preview. Previewing will open a new browser tab that triggers the optimization in a controlled session only visible to you.

Screen_Shot_2018-04-26_at_10.38.08_AM.png

 

Settings

The configurations in this are determine the metric values used in the analytics and violations measurements throughout the portal. Currently only status is available to end users. If adjustments are needed on any other setting configuration please contact the Client Services team for assistance.

Status - The status of Rapid CTRL is maintained by the Yottaa Client Services team. Any website on Rapid should utilize either Live or Bypass. There are currently other statuses available for internal use only. Please consult with you account representative if you have further questions on the status of your site.

Traffic - By default Yottaa will leave 1% of traffic unoptimized for comparison against the site with the current configuration deployed. This can be adjusted here, and may range depending on the amount of requests your site receives.

Violation Threshold - Yottaa used the amount of time a third party takes either before or after the onload event to identify violations. Those times for either Delay Page Load, default 750 ms before onload, or Performance risk, 1500 ms, can be adjusted here if you'd like to change the criteria used to identify violations. Size violations use KBs as a condition as the name suggests, which can be updated here as well.

Inventory Sampling Rate - You can change the percentage of sessions that return third party catalog information back to our portal. This data feeds into the third party inventory.

A/B Test - Allowing an A/B test will split traffic giving a two sets of data, either optimized or unoptimized, based on the percentage you specify as unoptimized.

Page Categories - Using the URL path to pages on a website we can divide the data collected and present third party or page load information based on whether the page is the home page, category page, product detail page, etc... These are applied in a top down manner, so your home page category should always be at the bottom of this rule list.

Screen_Shot_2018-04-23_at_3_33_01_PM.png

Have more questions? Submit a request

Comments

Powered by Zendesk