Page History

...

Example: A event param for the issue name configured in Mapp has the ID 5. To use this parameter for the APP_BOOKMARK_ADDED action you have to configure the event like this:

{
  "mapp": {
    "eventsEnabledByDefault": true,
    "viewsEnabledByDefault": true,
    "purchasesEnabledByDefault": true,
    "attributesEnabledByDefault": true,
    "events": {
      "APP_BOOKMARK_ADDED": {
        "templates": {
          "name": "Bookmark added"
        },
        "parameters": {
          "event_param_5": "{{ISSUE_NAME}}"
        }
      }
    }
  }
}

...

Parameter with prefixes use numbered IDs in Mapp / Webtrekk. 

Example: A custom parameter for the issue name configured in Mapp has the ID 6. To use this parameter for the STOREFRONT_ISSUE_PURCHASED action you have to configure the event like this:

...

User attributes are sent as additional session parameters to Webtrekk / Mapp. As with custom parameters, session parameters are numbered IDs and can be configured using the id template.

Values will be converted to strings. Attributes will be cached locally (in-memory) and sent with each event / page view.

Example:

{
  "mapp": {
    "eventsEnabledByDefault": true,
    "viewsEnabledByDefault": true,
    "purchasesEnabledByDefault": true,
    "attributesEnabledByDefault": true,
    "attributes": {
      "HAS_ACTIVE_SUBSCRIPTION": {
        "templates": {
          "id": "1"
        }
      },
      "HAS_ACTIVE_SUBSCRIPTION_CODE": {
        "templates": {
          "id": "2"
        }
      }
    }
  }
}

...