With the Simility Tag, you can collect user data for detecting fraudulent activities. This article shows you how to add and configure the Tag in your Tealium iQ profile.
Table of Contents Placeholder
First, go to Tealium's Tag Marketplace and add the Simility Tag to your profile (how to add a Tag?).
After adding the Tag, configure the below settings:
Customer ID (Required): Enter the unique identifier that you (or your company) received from Simility during signup.
Simility Lite: This is enabled by default. If you disable this feature, you have to provide additional user information to Simility.
Load Rules determine when and where to load an instance of this Tag on your site.
Recommended Load Rule: Load on all pages.
Mapping is the process of sending data from a Data Layer Variable to the corresponding destination variable of the vendor Tag. For instructions on how to map a Variable to a Tag destination, see Data Mappings.
The destination variables for the Simility Tag are built into its Data Mapping tab. Available categories are:
(Required) Customer/Account ID provided to you by Simility during signup
Boolean value (true/false) to determine whether or not Simility Lite is enabled.
Mapping to a Standard destination overrides its corresponding Tag Setting.
Allows you to send transaction data, e.g. user, orders, transactions, applications, profile, etc. Data is sent through the transaction_info object in the payload.
Entity type of the payload; required if using the transaction_info object
Unique id of the transaction; required if using the transaction_info object
First name of the user
Last name of the user
Username of the user
Email id of the user
Is First Order
Boolean value (true/false) to determine whether it's the user's first order
Number Of Retries
Number of attempts to place the order
Custom data related to the user's transaction. Replace "custom" with your custom parameter name. E.g. field.order_categories
Custom Nested Field
Send transaction data in a nested form. E.g. field.order_details.is_first_order
Notice how the transaction info mappings are wrapped in the transaction_info object whereas all non-transaction mappings are outside the object.