To configure weighting, start by creating one or more weighting schemes, and configure an Auto Importer for each scheme. The company uploads weight files, which set the segment level weights for a given time period. After the weighting files are imported, you can apply the weighting scheme to calculations and R-fields you want weighted.

You can define as many weighting schemes as your program needs, and your schemes can be applied to the same survey data. For example, an investment firm running several 401k plans might want to view scores weighted by the number of participants in each 401k plan and by the amount of money managed in each plan. If you need to apply the same weighting distribution measure across several survey programs, create one weighting scheme that incorporates the survey program field as one of the weighting scheme segments. This eliminates the need to have different calculations per survey program, which is especially important for users with cross-program roles.

1. Create a weighting scheme:
   1. Open the Reporting > Report Helpers > Weighting screen.
   2. Click New.
   3. Enter a Weighting Scheme Identifier, which identifies the scheme in Auto Importer and in relevant weighting A-field identifiers.

      After you create a weighting scheme with a specific identifier, you cannot reuse that identifier, even if you delete the original weighting scheme. The weighting A-fields, which are attached to historical surveys, continue to use that identifier.

   4. Enter a Weighting Scheme Name, which is visible when applying the scheme to calculations and R-fields.
   5. Enter a Priority, which determines the order of the scheme in the list of schemes.
   6. Select a Weighting Timeperiod, which determines the span of time to be considered when weighting.
   7. Optionally, enter a Survey Condition to restrict which surveys are weighted.
   8. Click Save.

      After saving, other parameters are available to configure.

   9. If you want to set weights (at least in part) on the basis of organizational hierarchy, select a Unit field to use for matching surveys to this weighting scheme.

      When weighting by unit, note that weights stay intact for survey records even if the unit is deactivated. Just as with unweighted calculations, responses tied to inactive units continue to be included in aggregate calculations.

   10. Select a Reporting Date, which is the time field used to determine whether a survey is in the time period you selected for the Weighting Timeperiod property.

       Ensure that the field you select matches the reporting Date Field you select on the Reporting > Report Helpers > Time > Time Fields screen. If these do not match, you might see discrepancies in weights over the weighting time period. A common cause of a mismatch is when a K-field is used to handle multiple timezones.

   11. If you do not want the weighting scheme to be applied when calculation is done on a single unit, turn on the Do not weight for single-unit calculations property.

       For example, unit-level Ranker reports will not show weighted data when this property is turned on.

   12. In the Add/Remove tab of the Segment Fields property, select one or more fields to use for segmentation, and then click Add.

       If you select more than one field, Medallia Experience Cloud uses values from the intersection of the fields you select. If a field is part of a weighting scheme it is always used to match weights to surveys. (Wild cards are not supported.) In this case, Null is considered a value for matching. You can select fields of the following types:

       • Unit
       • Unit Group
       • Enumerated (A-fields, E-fields,Q-fields, and K-fields)
       • Auto-Indexed (A-fields, E-fields, Q-fields, and K-fields)
   13. Click Save.
   14. When you are ready to use your scheme, turn on the Confirm property and then click ActivateWeightingScheme.
2. Configure an Auto Import specification for the weighting scheme:
   1. Open the Integrations > Data Import > Importers > Auto Importer Processors screen.
   2. Click New.
   3. Optionally, enter a Category for this specification, such as Weight.
   4. In the Definition property, enter XML that defines the specification. Note the following requirements and suggestions for the definition:

      • The Auto Importer (and incoming file from the company) must map:

        • The date to which the segment weight applies. Any date in the period is acceptable. For example, a monthly weighting scheme considers 2016-10-01 and 2016-10-15 to be the same.
        • The segment weight to be distributed to surveys in the segment, in the period.
        • The segment field(s) used to define the segments and match them to individual surveys.
      • You must specify a weighting scheme identifier using the weight-processor-options element.
      • Typically, append new weights rather than completely replace existing weights, so set the recordUpdateMode attribute to CREATE_AND_UPDATE.

      • Consider using the following sample XML as a starting point:

        <import-spec inputType="EXCEL" name="IMPORT: Segment Weights" description="An Importer for Weighting Scheme A">
        	<input-column heading="Date" />
        	<input-column heading="Segment Weight" />
        	<!--	Weighting segments can be based on the Hierarchy 
        			and/or enumerated fields (including auto-indexed)-->
        	<!--<input-column heading="Unit" />-->	
        	<!--<input-column heading="Unit Group" />-->
        	<input-column heading="Segment A" />
        	<!--<input-column heading="Segment B" />-->
        	<!--<input-column heading="Segment C" />-->
        	<output-column-group pluginName="Weight" recordUpdateMode="CREATE_AND_UPDATE">
        		<output-column>
        			<input-column heading="Date" />
        			<target-field fieldId="date" fieldName="Date" requiredness="REQUIRED_USED_FOR_DUPLICATE_CHECK" type="DATE">
        				<date-field-parse-options format="yyyy-MM-dd" />
        			</target-field>
        		</output-column>
        		<output-column>
        			<input-column heading="Segment Weight" />
        			<target-field fieldId="weight" fieldName="Weight" requiredness="REQUIRED" type="FRACTIONAL" />
        		</output-column>
        		<output-column>
        			<input-column heading="Segment A" />
        			<target-field fieldId="e_company_segment_a_txt" fieldName="Weight Group Name" requiredness="REQUIRED_USED_FOR_DUPLICATE_CHECK" type="ENUMERATED_AUTOINDEX" />
        		</output-column>
        		<!--	The weighting scheme identifier this AI will map weights to -->
        		<weight-processor-options identifier="weighting_scheme_id" />
        	</output-column-group>
        </import-spec>

   5. Click Save.

      For detailed information about configuring Auto Importer specifications, see Auto Importer Processors and Auto Importer UI.

      Warning: You can import weights for any time period, whether past, present, or future. However, if you import weights for a historical time period, be aware that those weights will not be applied until you run a backfill.
3. Apply the weighting scheme to one or more calculations:
   1. Open the Reporting > Report Helpers > Calculations screen.
   2. Select a calculation that should be weighted.
   3. Select a WeightingScheme.

      You can apply weighting to the standard calculation types: Average, Top Box, NPS, and % Yes on a Yes/No field.

      
   4. If your calculation has multiple options chosen in the MemberAlternativeSets property, you can apply a different WeightingScheme to each option.
   5. Click Save.

      For more information about configuring calculations, see Calculations.

4. Apply the weighting scheme to one or more R-fields:
   1. Open the Reporting > Report Helpers > Fields > R-Fields screen.
   2. Select the R-field that should be weighted.
   3. Select a WeightingScheme, and then click Save.
5. Test your weighting configuration, as described in Testing weighting schemes.