Tags in the MOCA Console refers to properties you can add to users, and are designed to act like counters. Once this attribute is given to the user, you can use it for segmentation purposes.


Tags are created in the MOCA Console or via API. Console example below:

Things that can be done with tags:

  • You can color code each tag for an easier visual search.
  • You can exclude certain tags from analytics. 
  • You can create hierarchical tags using the colon symbol.
  • Tags can be set and reset using experiences. Example: experience 1 sets tag to 1 when a user enters the range. Experience 2 sets tag 1 to zero when the user leaves the location.

Tags are a powerful tool, easily configured and recommended to maximize the efficiency of proximity campaigns. 

    • Related Articles

    • Export Tag data

      The Tag data can be downloaded in a simple manner using the Export function in Analytics Reports > Tags. To do so follow these steps: Log into your MOCA Console Account.  Navigate to your App. Go to Analytics. Now click on Tags. On the upper right ...
    • Analytics Reports

      Analytics reports allow you to get a variety of insights from your app per range of time. Data is presented in the form of graphs, heat maps, tabular data, pie charts, etc...  The UI is divided into: Activity - Shows user metrics per time period. ...
    • Tag Analytics

      MOCA Console's Tag Analytics provides you with an inclusion diagram that represents the taxonomy you have defined in your tags: here we have a campaign dividing users between physical and online purchases. This is made possible using the Tag feature ...
    • Segments

      Segments are a powerful tool to create audience segments based on their attributes. First of all you select the logic to apply to one or more attributes. You can choose between All (AND) and Any (OR), and nest various logical operators. You have a ...
    • Default Segmentation Variables

      The segmentation variables in this list are attached to the individual user. Some of the variables are captured directly from the handheld, others are information facilitated by the App in which the SDK is integrated.   Here is the default list: A/B ...