What is involved in Galileo initiation?

General technical requirements for each of three potential scenarios.

There are three potential scenarios that may require light configuration. The following are provided for general informational purposes, Arcalea will provide additional detailed instructions for each of the included scenarios.

Scenario 1: The Collector 
In this scenario, the data collector is turned on and Galileo initiates the collection of Client data for storage and data for evaluation. Technical requirements include the installation of a tracking tag in Google Tag Manager (GTM):

1. Client has access to GTM admin account (with publishing permissions) to implement 

Scenario 2: Galileo Full Deployment

The full deployment occurs where the data collector is turned on and CRM is integrated to integrate lead and revenue statuses. Installation of a tracking tag in Google Tag Manager (GTM) and CRM service account with login is required. In addition, Google Analytics 4 (GA4) "read" access is requested to benchmark data collection. Technical requirements include:

1. GTM admin account (with publishing permissions)
2. CRM API / service account
3. CRM UI login to examine records directly during the calibration period
4. GA4 to benchmark against for data collection

Scenario 3: Privacy-enabled (PII hashed) Deployment 

The privacy-enabled deployment occurs where a Galileo full deployment is implemented, however, all PII information is hashed (obscured) to the Galileo database. Client receives a hash registry for optional internal use. Technical requirements include:

1. GTM admin account with publishing permissions
2. CRM API / service account
3. CRM UI login to examine records directly during the calibration period
4. GA4 to benchmark against for data collection
5. PII hash registry provided to Client for optional use

Non-Technical Requirements

1. Established lead-to-revenue processes, or ability to establish processes for lead management
   1. Lead statuses process must identify the revenue step -> which status(es) are revenue-related in the CRM
2. Tagging of links - should use standard URL parameters including utm_source, utm_medium, utm_campaign, and any others for the Client’s specific infrastructure and platforms

Arcalea's account team works directly with customer teams throughout the onboarding and initiation process.

1. Hands-on training and quality assurance are performed during the first 4 weeks of the process.
2. Training consists of live demo/training sessions led by our staff to configure at-a-glance views for each team.
3. Tutorials from our video training library and our FAQ are always accessible to customer teams at any time.

Arcalea will provide detailed instructions for each of the above scenarios.