User accounts & automated user-tagging

Note: Please contact Magine support, to support you in setting up this feature.

Goal

Users that register should be tagged, either by a parameter in the URL or from a selected option in the dropdown to segment these users based on predefined options. This can be e.g. favourite sports teams, local cinemas, or affiliates of any sort. This can be used for e-mail segmentation and data reports.

Key user benefits

• Partners can segment users on different attributes based on the tags

• Users can themselves select what “group” they belong to

• Users coming from a specific URL will automatically get a tag

Implementation

• A dropdown with options is configured for the registration flow: https://console.magine.com/configurations/default#users-signup

• Under "Web Registration Flow, click "Add" registration field.

• Select "Drop Down Menu"

• "Key" = The query string parameter in the URL to be used

  • https://play.maginepro.com/create-account?<KEY>=<VALUE>

• "Tag for affiliates" = The user gets an additional user tag (see use case 2) if the URL is used as the source link to get to the registration page.
  

• For each "Option" in the drop-down list, you want to create, and in order to separate the data for reporting, it is important that each "value" has a common prefix, for the different options.

  • Option 1 in the list: Value = cinema_madrid

  • Option 2 in the list: Value = cinema_barcelona

  • Using this method, reporting can filter on the "cinema_" prefix.
    

• If the “Key” for the dropdown matches a parameter in the URL, the value from the URL will be used and the user can not select an option

• If the “Key” for the dropdown does not match with a parameter in the URL, the user can select an option themselves.

• Users will get an additional tag if they come from a URL with the matching “Key”

DATA

• Magine will configure and provide one additional standard report in the Analytics dashboard to report the user segmentation.

• Since the information is stored in the user tags, this information is exported to Mailchimp and can be used to segment email marketing lists.

LImitations

• The user cannot modify this field in any way.

• The administrator can edit this field in the user's profile in the CRM, however, this will affect the data reported for that user.

• Passing query string parameters, will not store any data in the Magine Platform unless the user completes the user creation flow.

• Deletion of a user profile will result in losing tagging data associated with the user and their history.

Use Case 1 - user-selected input

• Once configured with the help of Magine support, the drop-down option will be available, with the options to select (note - this can be set to be a mandatory or optional field)

• The user will then select the relevant option from the drop-down, and continue to create their account.

• https://play.maginepro.com/create-account

After the user has successfully created an account, the user's profile will be updated with the tag

Use Case 2 - URL query parameter & forced selection

• Once configured with the help of Magine support, the relevant options will be available for tagging via the URL query parameters.

• In this use case, the user cannot select from the drop-down but is assigned the selection that is passed in the query string parameters.

• https://play.maginepro.com/create-account?affiliate=a3

• After the user has successfully created an account, the user's profile will be updated with the tag

• The user also gets an additional tag (configurable), that shows that this user came from a "forced" URL Query parameter flow (and not a user-selected flow, as in Use Case 1)

Web Query Strings

In combination with the above, the web application can use URL variables and pass these through to specific fields in the web application. https://en.wikipedia.org/wiki/Query_string

Web - Create User ( /create-account )

Example URLs

• Base URL: https://play.maginepro.com/create-account

• URL with all query strings: https://play.maginepro.com/create-account?name=first name&identity=user_email@email.com

Limitations & considerations

• If the create user page, has the email confirmation field setup (i.e. two email fields), only the first field will be populated. This is to ensure that the user still validates their email.

• When using this feature in combination with other web query string features (i.e. affiliate tracking), ensure that the above field names are only used for this purpose.

• Passing these query string parameters, will not store any data in the Magine Platform unless the user completes the user creation flow.