ifp_params
When the script is executed with the auto=1 option, the ifp_init methods are called automatically. In this scenario, it is not possible to directly pass a partner configuration object to these methods. To accommodate this, configurations can be set through a variable named ifp_params, which should be declared and initialised before calling the GAH script. This variable will be used to configure the partners:
<head>...
<script>
var ifp_params = {
bhv: {
pageIdCallback: function () {
return "ebanking/auth/login"
},
anonymous: {
by_name: ["userId"]
}
}
}
</script>
<script src="<%= signalCollectorUrl %>/api/v2/tenants/<%= tenantId %>/scripts?auto=1"></script>
...
Page ID
A Page ID is a distinct numeric identifier assigned to a customer's web page, essential for differentiating between multiple pages configured for Page Fingerprinting. Each Page ID must be unique within the specified Org_ID. For example, if a customer operates multiple websites, each web page across all sites associated with that Org_ID must have a distinct Page ID. This parameter links Profiling Tags to the Page Fingerprinting configuration.
Important Consideration
If only a single page utilises the Page Fingerprinting feature, specifying the page_id parameter within the Profiling Tags is not mandatory, although it is recommended. If the page_id parameter is omitted, the system defaults to a Page ID of 1.
Additional Recommendation
The inclusion of this parameter is strongly recommended for optimal usage. The value assigned to the Page ID itself is arbitrary.
| Parameter | Value | Description | Data Type |
|---|---|---|---|
| page_id | Optional | Specifies which page is being profiled, applicable when more than one page contains ThreatMetrix tags. The value must be a whole number entered as a string and cannot contain , . or spaces. | string |
Client applications can specify a page_id by invoking the following function:
ifp_initView({
tmx: {
page_id: 123
}
});
The
ifp_initViewfunction is invoked to initiate data collection for a specific view. It loads the TMX script, optionally including apage_idif provided, and ensures the script is only loaded once per use case.The
tmxobject manages the integration with ThreatMetrix within the application, controlling when and how TMX data collection scripts are loaded for each use case. It tracks whether profiling has already occurred and allows for re-profiling as needed.
