| DENG-3866 |
To improve marketing attribution and user journey insights, we’ve expanded tracking to capture both First Touch and Last Non Direct Touch interactions across Console, DirectSQL, and Data Export platforms.
First Touch records the user’s initial interaction with the financial institution’s website, while Last Non Direct Touch captures the final marketing-attributable interaction before application submission. Additionally, this release introduces Click IDs (Google, Facebook, and Microsoft) across all marketing touch points, including First Touch, Last Non Direct Touch, Application Start, and Application Submit.
New and Updated Fields:
- Entrance URL (First Touch): Records the URL of the applicant’s first interaction with the FI website. This field replaces “Entrance URL”.
- Entrance URL (Last Non Direct Touch): Captures the URL at the applicant’s final non-direct interaction with the FI website.
- Referring URL (First Touch): Stores the URL that referred the applicant to the FI website on their initial interaction. This field replaces “Referring URL.”
- Referring URL (Last Non Direct Touch): Tracks the referring URL of the applicant’s last non-direct interaction before submission, if applicable.
- Referring Domain (First Touch): Captures the domain of the first touch referring URL. Replaces “Referring Domain.”
- Referring Domain (Last Non Direct Touch): Captures the domain of the last non-direct referring URL.
- UTM Parameters (Last Non Direct Touch):
-
- UTM Source
- UTM Medium
- UTM Campaign
- UTM Content
- UTM Term
- Marketing Channel
- Click IDs for All Marketing Touch Points: Each of the following ad click identifiers now has entries for First Touch, Last Non Direct Touch, Application Start, and Application Submit
-
- Google Click ID (gclid)
- Facebook Click ID (fbclid)
- Microsoft Click ID (msclkid)
- Query Params (First Touch): Captures all query parameters from the First Touch Entrance URL. This field replaces “Query Parameters” in Application Reports.
- Query Params (Last Non Direct Touch): Captures all query parameters from the Last Non Direct Touch Entrance URL.
- Field Locations and Preceding Columns in Affected Reports:
- Simplified Acquisition Report:
- The following URL fields appear in the following order immediately after Browser Type:
- Entrance URL (First Touch)
- Referring URL (First Touch)
- Referring Domain (First Touch)
- Entrance URL (Last Non Direct Touch)
- Referring URL (Last Non Direct Touch)
- Referring Domain (Last Non Direct Touch)
- The following Last Non Direct Touch UTM Parameters appear in the following order immediately after Marketing Channel (First Touch):
- UTM Source (Last Non Direct Touch)
- UTM Medium (Last Non Direct Touch)
- UTM Campaign (Last Non Direct Touch)
- UTM Content (Last Non Direct Touch)
- UTM Term (Last Non Direct Touch)
- Marketing Channel (Last Non Direct Touch)
- Query Parameters (Last Non Direct Touch) – Positioned after Query Parameters (First Touch)
- The following advertising Click IDs appear in the following order immediately after Query Parameters (App Submit):
- Google Click ID (First Touch)
- Facebook Click ID (First Touch)
- Microsoft Click ID (First Touch)
- Google Click ID (Last Non Direct Touch)
- Facebook Click ID (Last Non Direct Touch)
- Microsoft Click ID (Last Non Direct Touch)
- Google Click ID (App Start)
- Facebook Click ID (App Start)
- Microsoft Click ID (App Start)
- Google Click ID (App Submit)
- Facebook Click ID (App Submit)
- Microsoft Click ID (App Submit)
-
-
- Raw (Legacy) Acquisition Report:
- The following URL fields appear in the following order immediately following Library:
- entrance_url__first_touch
- referring_url__first_touch
- referring_domain__first_touch
- entrance_url__last_non_direct_touch
- Referring_url__last_non_direct_touch
- referring_domain__last_non_direct_touch
- The following Last Non Direct Touch UTM Parameters appear in the following order immediately after Marketing Channel (First Touch):
- UTM Source (Last Non Direct Touch)
- UTM Medium (Last Non Direct Touch)
- UTM Campaign (Last Non Direct Touch)
- UTM Content (Last Non Direct Touch)
- UTM Term (Last Non Direct Touch)
- Marketing Channel (Last Non Direct Touch)
- Query Params (Last Non Direct Touch) - Added after Query Params (First Touch)
-
-
- Simplified Consumer Applications Report:
- Marketing Channel (Last Non Direct Touch) - Positioned immediately after Marketing Channel (First Touch)
- The following URL fields appear in the following order immediately following IP Address:
- Entrance URL (First Touch)
- Referring Domain (First Touch)
- Query Params (First Touch)
- Entrance URL (Last Non Direct Touch)
- Referring Domain (Last Non Direct Touch)
- Query Params (Last Non Direct Touch)
-
-
- Simplified Business Applications Report:
- The following URL fields appear in the following order immediately following IP Address:
- Entrance URL (First Touch)
- Entrance URL (Last Non Direct Touch)
- Marketing Channel (Last Non Direct Touch) - Positioned immediately after Marketing Channel (First Touch)
-
-
-
-
-
- Raw (Legacy) Applications Reports:
- Marketing Channel (Last Non Direct Touch) — positioned immediately after Marketing Channel (First Touch)
These changes will be in UAT starting 11/14/24 and Production 12/5/2024
|
| DENG-4021 |
Added new fields to the Simplified and Raw Reports in Console, DirectSQL, and Data Export to support the upcoming enhancement of opening multiple accounts in a single application.
-
- Reference ID: Unique identifier for each individual account opened as part of a bulk application
- Located in the following reports: Agreements, Attestations, Business Applications, Consumer Applications, Funding, KYC/Decisioning, Product Services
- Is Bulk Application: indicates if an application opened more than one new account.
- Located in the following reports: Agreements, Attestations, Business Applications, Consumer Applications, Email, KYC/Decisioning.
Note: For application reports, there will be one row for each Account created or modified. For example, a bulk application that opens 3 accounts will have 3 rows in these reports, one for each account.
These fields are currently in UAT reports and will be deployed to Production on December 5th.
|
