How Google integration works

To integrate with Google Analytics and Google Tag Manager, you need to enter the tracking ID in the system settings of DreamApply. DreamApply integrates with Google products through:

  • Google Analytics: Measurement ID for a data stream, for example: G-XXXXXXXXXX
  • Google Tag Manager: Container ID, for example: GTM-XXXXXXX

DreamApply automatically injects the required tracking script into the DreamApply portal. DreamApply uses gtag.js — a single global tag that sends data to several Google services:

  • Google Analytics
  • Google Tag Manager
  • Google Ads

The gtag.js script collects user interaction data, such as page views, button clicks and file downloads, and sends it to the connected Google products. It also captures user details, such as geographical location, device type and browser details. As a result, you can monitor and analyze this data in existing Google environments.

Data layer

To gain deeper insights into user behavior, you can utilize the data layer provided by Google.

The data layer is a special JavaScript object that allows third-party systems to pass information to Google tags. DreamApply uses it to store and transfer data about application events that are otherwise difficult to get from URL changes, for example, when an applicant registers or submits an application.

DreamApply pushes the following event data to the data layer:

Event data
JSON
{
   "event":"Applicant registered",
   "applicant_ID":123
}
Event data
JSON
{
   "event":"Application was created",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
},
{
   "event":"Application was created by cloning",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
},
{
   "event":"Application was edited",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
},
{
   "event":"Application was submitted",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
},
{
   "event":"Application was reopened",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
},
{
   "event":"Application was withdrawn",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
},
{
   "event":"Application was re-submitted",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123
}
Event data
JSON
{
   "event":"Course was added to application",
   "academic_year":2025,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123,
   "course_ID":123,
   "institution_ID":123
},
{
   "event":"Course was removed from application",
   "academic_year":2023,
   "academic_term_ID":123,
   "applicant_ID":123,
   "application_ID":123,
   "course_ID":123,
   "institution_ID":123
}

DreamApply utilizes Google consent tools to ensure that user tracking preferences are applied correctly.

Google analytics tracking is activated only after users grant explicit consent for analytics and metrics cookies in the DreamApply portal. If users do not grant consent, DreamApply does not collect tracking data.

You can choose from one of the following cookie consent modes:

  • Implied consent: DreamApply assumes that users grant consent when they set their citizenship. All cookies are enabled automatically, and Google analytics tracking is activated.
  • Polite bar and Assertive dialog: DreamApply displays a consent window where users can choose which types of cookies to accept. If users do not explicitly grant consent, Google analytics tracking remains disabled.

If you select the Polite bar or Assertive dialog mode, DreamApply additionally displays the Google Consent mode section. You can use this section to granularly configure consent settings for Google Analytics, Google Ads and Google Tag Manager.

Integration disclaimer

This disclaimer should be read in conjunction with meaning of DreamApply Terms of Service (specifically section 6.3., 11.2. and 12) DreamApply Data Processing Agreement and DreamApply Service Level Agreement (specifically section 5.3.).

Risks associated with the use of external code (e.g., Google Tag Manager)

Adding an external tag manager (such as Google Tag Manager, or other similarly operating analytics platforms) will necessarily cause foreign code to run within the DreamApply system. This includes both code written by the respective platform (e.g., Google) and code written by the authors of the tags that you manage with the help of the tag manager.

This foreign code will run within the browser session context of your users, as if it were part of the DreamApply frontend, and will have access to anything that the authenticated user is able to access. This applies both to code written by the clients themselves and to cases where malicious code may be injected into the portal by a third party (for example, in case of a security compromise, a malicious actor may potentially add their code through these integrations).

If created with malicious intent, or due to a security vulnerability, the tags may expose personal data or other data held in DreamApply to third parties. As such, the use of such external code invalidates several key security assumptions, and DreamApply may no longer be able to safeguard the security of your data.

Critical implications and limitation of liability

  1. Data Access and Privacy: These integrations grant foreign code full access to client data. They may compromise data privacy and security.
  2. Functionality Disruption: External scripts may disrupt or break the portal’s functionality, leading to unexpected errors or downtime.
  3. Legal Liability: The client assumes sole responsibility for all legal and regulatory consequences arising from the use of external code and the sharing of data with third parties.
  4. System Warranty Invalidated: The use of any external code (such as Google Tag Manager, or similar platforms) invalidates the DreamApply system warranty. DreamApply cannot be held responsible for the effects of external scripts or tags, including any data loss, security breaches, or portal malfunction caused by them.
  5. No Direct Link or Shared Responsibility: For the avoidance of doubt, there is no direct link or shared responsibility between our company and Google or any other similar service provider.

Please be mindful of the tags that you add and make sure that the authors of those tags can be trusted.