Data Enrichment and Inlining

FunnelConnect provides extensive data enrichment and inlining capabilities across most of its APIs. Any data collected and imported, including event and profile data can be returned and inlined. Additionally, our iPaaS solution provides a wide range of API based data integration capabilities, for example with data cloud, data service, and client internal data warehouse services.

Fetching data from external systems via API requires very low latencies. Configurable timeout and circuit breaker solutions ensure the FunnelConnect service operates end-to-end even if external systems are not as expected.

FunnelConnect can use any of the available identifiers from its ID profile as lookup ID with these systems.

Data Enrichment

All Data Pipelines can be enabled for data enrichment. This can be done based on specific consent / permissions.

Geo.IP

IP address and user-agent derived data enrichment.

IP2Location data sample as inlined into events data stream:

JSON

  "geo": {
      "cc": "ES",
      "loc": {
        "lon": -0.37756800651550293,
        "lat": 39.469482421875
      },
      "mobileBrand": "Orange",
      "mnc": "03/09",
      "reg": "Valenciana, Comunidad",
      "city": "Valencia",
      "latency": 1,
      "isp": "Orange Espagne SA",
      "domainName": "orange.es",
      "mcc": "214",
      "usageType": "MOB"
    }

See Geo.IP Address Derived Field Description for more information .

User-Agent

Udger data sample as inlined into events data stream:

JSON

    "ua": {
      "bType": "MB",
      "os": "Android",
      "latency": 1,
      "hdr": "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Mobile Safari/537.36",
      "bFamily": "Chrome Mobile",
      "dName": "SP",
      "bVer": "133.0.0.0"
    }

See User-Agent Derived Field Description for more information.

External Data Enrichment Services

External data sources (e.g. profile database) and data enrichment services (e.g. Weather API) can be included in real-time as long as latencies permit.

Data Inlining

User profile data inlining can be done via the following methods:

JSON response and attributes key-value-pairs, also stored in fcData local storage key, using Info Ident Track API.
Query string parameter key-value-pairs (for example to landling page, etc.), using Click Ident Track API and Proxy service.

Example JSON response:

JSON

{
  "umid": "86def240-beff-420d-ae87-ea76b8a84e1b",
  ...
  "attributes": {
    "browserFamily": "Chrome",
    "browserType": "BR",
    "browserVersion": "132.0.0.0",
    "cc": "DE",
    "city": "Frankfurt am Main",
    "deviceName": "PC",
    "domainName": "amazon.com",
    "isp": "A100 ROW GmbH",
    "latitude": "50.11088",
    "longitude": "8.681996",
    "mcc": "",
    "mnc": "",
    "mobileBrand": "",
    "osFamily": "Windows",
    "region": "Hessen",
    "nba1": "nba1",
    "nba2": "nba2",
    "usageType": "DCH",
    "attribute1": "value1",
    "attribute2": "value2"
  }
}