After successfully instantiating a VWO class, getVariationName API activates a FullStack A/B test for the specified user for a particular running campaign.
The API method:
- Validates the parameters passed.
- Checks whether the user is whitelisted.
- Checks if User Storage Service is provided to know whether the user is returning. If yes, show the previously assigned variation always.
- Checks if the campaign is part of Mutually Exclusive Group and evaluates all the grouped campaigns to decide whether the user is eligible for the campaign.
- Checks whether the user is eligible for a campaign based on pre-segmentation conditions.
- Checks whether the user qualifies to become a part of the campaign based on traffic allocation.
- Assigns a deterministic variation to the qualified user.
- Does not send an impression event to the VWO server.
It takes the same parameters and returns the same value as Activate API. The only difference is that this API method does not send a tracking impression to the VWO server. This API method is used to get the variation assigned to the userId.
The behavior of the two API methods, that is, activate and getVariationName is identical otherwise.
Use Get Variation Name API if Activate API has been already triggered to prevent a user from being tracked again. Also, this API is also helpful in retrieving the variation assignment to a particular User Id, respecting all other factors like segmentation, whitelisting, etc. without sending any impression call to the VWO servers.
The campaign needs to be identified based on the unique test-key provided at the time of campaign creation.
The User ID which uniquely identifies each user.
Pass params for pre-segmentation and whitelisting
customVariables(Object): Custom variables to be matched against Campaign's pre-segmentation.
variationTargetingVariables(Object): Custom variation targeting variables to be matched against Campaign's forced variation/whitelisting conditions.
The name of the variation in which the user is bucketed, or is null if the user does not qualify for a campaign.
When a user qualifies for the campaign, variation name is returned.
When a user is not qualified for a campaign, null is returned.
import vwo settings_file = vwo.get_settings_file(account_id, sdk_key) vwo_client_instance = vwo.launch(settings_file) # campaign_key: you provide at the time of campaign creation # user_id: how you identify a particular user # custom_variables: pre-segmentation variables # variation_targeting_variables: forced variation variables variation_name = vwo_client_instance.get_variation_name(campaign_key, user_id, custom_variables = custom_variables, variation_targeting_variables = variation_targeting_variables) if (variation_name == "Control"): # CODE: write code for Control elif (variation_name == "Variation-1"): # CODE: write code for Variation-1 else: # CODE: User is not qualified for the campaign. Would be due to configuring campaign's percent-traffic less than 100% while creating or updating a FullStack campaign.
If User Storage Service is provided, campaign activation is mandatory before tracking any goal, getting a variation of a campaign, and getting the value of the feature's variable.
vwo_client_instance.activate(campaign_key, user_id) vwo_client_instance.track(campaign_key, user_id, goal_identifier)
# Calling track API before activate API # This will not track goal as campaign has not been activated yet. vwo_client_instance.track(campaign_key, user_id, goal_identifier) # After calling track API vwo_client_instance.activate(campaign_key, user_id)
Updated about 1 year ago