Results for “ams_web_tracking”

46 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_WEB_TRACKING is a transactional table owned by the AMS (Marketing) schema in Oracle E-Business Suite. Its documented purpose is to store tracking data for web advertisements and offer-type schedules, making it a repository for recording how prospects and customers interact with marketing content delivered through web channels and structured offer schedules. Because the table captures activity and response events against a defined marketing schedule, it functions as an operational detail store within the Oracle Marketing (AMS) module rather than as a setup or reference table.

From a Data Vault modeling perspective, the supplied metadata classifies this object heuristically as standalone. No parent or child hub or link dependencies were mined from the foreign-key structure, so it is best viewed as an independent record set within the AMS web tracking domain. In practice, the web tracking identifier and its associated schedule, placement, and content references make it a natural satellite candidate keyed on WEB_TRACKING_ID, though the classification remains a modeling suggestion rather than a documented constraint.

Key Information Stored

The table contains 29 documented columns. The most significant include:

Common Use Cases and Queries

The primary reporting scenarios involve measuring web advertisement effectiveness, offer response rates, and click-through attribution by schedule, placement, or content item. A typical query joins the tracking rows to content items and security groups:

SELECT wt.WEB_TRACKING_ID, wt.SCHEDULE_ID, wt.PARTY_ID, wt.OFFER_SRC_CODE, ci.CONTENT_ITEM_NAME
FROM AMS.AMS_WEB_TRACKING wt, IBC.IBC_CONTENT_ITEMS ci, FND.FND_SECURITY_GROUPS sg
WHERE wt.CONTENT_ITEM_ID = ci.CONTENT_ITEM_ID
AND wt.SECURITY_GROUP_ID = sg.SECURITY_GROUP_ID;

Additional use cases include aggregating responses by OFFER_SRC_CODE for campaign attribution, extracting tracking records for a specific PARTY_ID to drive personalization, and auditing records by LAST_UPDATE_DATE for change tracking. Descriptive flexfield columns support client-specific extensions. Because the table is standalone with respect to hub/link dependencies, queries typically join outward to content, security, and recommendation objects rather than being consumed as a shared hub.

Related Objects

The documented foreign-key relationships define the primary dependencies:

  • IBC_CONTENT_ITEMS — referenced by AMS_WEB_TRACKING.CONTENT_ITEM_ID; provides the content item displayed.
  • FND_SECURITY_GROUPS — referenced by AMS_WEB_TRACKING.SECURITY_GROUP_ID; governs access control.
  • AMS_WEB_RECOMMS — references AMS_WEB_TRACKING via WEB_TRACKING_ID; stores web recommendations tied to a tracking record, making it the principal child object.

The primary key AWTR_PK on WEB_TRACKING_ID, enforced by the unique index AMS_WEB_TRACKING_U1, anchors these relationships and supports efficient lookups. Together with SCHEDULE_ID and PLACEMENT_ID, these references allow the AMS module to correlate web advertisement activity with offer schedules and downstream recommendation logic, which is the core analytic value of the table.